Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #609 from tengguozheng/patch-2
Update README.md
- Loading branch information
Update README.md
ca4a80d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the timely correction. Will this project later include a data ETL processing module? This could include, but not be limited to, a drag-and-drop canvas interface allowing users to customize data flows.
ca4a80d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Accelerated & streamlined ETL is very much a focus, eg, part of what gfql needs to wrangle, and what .featurize() does for data prep for ML operators
It's an interesting question what to do for easier interfaces:
we have been improving docs in prep for making an LLM text2code converter that does pygraphistry, gfql, etc better. OpenAI has already been crawling out examples, so appears to be working somewhat.
... and via louie.ai, a conversational & point-and-click editor. It includes marble diagrams for flows, so it is somewhere between jupyter and nifi
Bringing ETL deeper in-tool for the UI is interesting. We are redoing the filter pipeline to sinplify in-viz pipelines, and hopefully then making the pipelines dynamic. At that point, in-viz ETL/connectors makes a lot of sense! Louie.ai will be doing the same from the outside in a more notebook flow.
Hope that helps , lmk if thoughts!