CTTY opened a new issue, #16959:
URL: https://github.com/apache/datafusion/issues/16959

   ### Is your feature request related to a problem or challenge?
   
   Hi DataFusion community,
   
   I'm currently working on Iceberg-DataFusion write support. 
`TableProvider::insert_into` provides a handy interface for `INSERT INTO` DML 
support, but I found that there is no `delete` or `update` interface in 
`TableProvider`.
   
   Ideally, all Iceberg-DataFusion DML support should go through the same 
layer. In this case, if we want to support `DELETE` and `UPDATE` with 
DataFusion, we may have to implement a custom planner specifically for those 
operations, which feels a bit cumbersome to me.
   
   If `TableProvider::delete_from` and `TableProvider::update` existed, we 
could use `TableProvider` as the unified integration point between DataFusion 
and Iceberg.
   
   
   
   
   ### Describe the solution you'd like
   
   Support delete or update DML.
   
   Would love to learn if there is anything blocking us from doing this.
   
   ### Describe alternatives you've considered
   
   _No response_
   
   ### Additional context
   
   Related issue: https://github.com/apache/datafusion/issues/12406
   
   I'm aware of these 
[comments](https://github.com/apache/datafusion/blob/aab44fdaaec28fd13b544ccff239c8b8fe6cee2f/datafusion/core/src/physical_planner.rs#L1289-L1297)
 claiming that DataFusion is a read-only query engine, but I'm assuming they 
are outdated since we already support insert_into 


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

Reply via email to