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

["tustvold (via GitHub)" <gi...@apache.org>]

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

   > The downsides are that such an ExecutionPlan is kind of strange
   
   In addition to the points r.e. sort order, etc... from a scheduling / partitioning standpoint the result is not especially 
   
   > Add specific runner / executor for Inserts / Update / Deletes
   
   I'm likely missing something but does this even need to be a separate abstraction, is this not an implementation detail of `TableProvider::insert_into`? This would also allow it to make table-specific decisions w.r.t preserving partitioning, transaction handling, etc... Basically https://github.com/apache/arrow-datafusion/pull/6049 but returning `Result<()>`


-- 
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