|
|
|
|
|
by C4stor
731 days ago
|
|
It's a good idea, but from the docs it looks like the high level abstractions are wrong. If my data pipeline is "take this table, filter it, output it", I really don't want to use a "csv file input" or a "excel file output". I want to say "anything here in the pipeline that I will define that behaves like a table, apply it this transformation", so that I can swap my storage later without touching the pipeline. Same things for output. Personally I want to say "this goes to a file" at the pipeline level, and the details of the serialization should be changeable instantly. That being said, can't complain about a free tool, kudos on making it available ! |
|