alamb commented on issue #17297: URL: https://github.com/apache/datafusion/issues/17297#issuecomment-3228359549
In terms of designing an API, I think it would help me to understand what behavior you want in Ballista when a user runs `DataFrame::cache` (aka how wll you use this API)? For example do you want it to write to fies distributed across the nodes? It seems to me at the moment `DataFrame::cache` is basically a shorthand for ```sql "CREATE TABLE <temp> AS SELECT * FROM <dataframe> ``` The current implementation has a hard coded MemTable and the orchestration (creation of the MemTable / batches) is in the DataFrame::cache function itself. If you want to move the logic to LogicalPlans you'll probably also have to add an equivalent physical node that handles the orchestration -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
