You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by "thinkharderdev (via GitHub)" <gi...@apache.org> on 2023/04/25 17:50:37 UTC

[GitHub] [arrow-datafusion] thinkharderdev commented on issue #5076: Re-implement `DataFrame.write_*` to use `LogicalPlan::Write`

thinkharderdev commented on issue #5076:
URL: https://github.com/apache/arrow-datafusion/issues/5076#issuecomment-1522183544

   > The downsides are that such an ExecutionPlan is kind of strange (it makes no output, so therefore most of the methods like "output ordering" are basically useless)
   
   I think it's useful to have write operations be able to produce outputs. In many use cases you actually want metadata about what was written (file locations, total bytes, etc). This seems like a natural way to, for example, update a catalog with the new table. 


-- 
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-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org