You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2020/12/03 17:13:00 UTC
[jira] [Resolved] (SPARK-33623) Add canDeleteWhere to
SupportsDelete
[ https://issues.apache.org/jira/browse/SPARK-33623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dongjoon Hyun resolved SPARK-33623.
-----------------------------------
Fix Version/s: 3.1.0
Resolution: Fixed
Issue resolved by pull request 30562
[https://github.com/apache/spark/pull/30562]
> Add canDeleteWhere to SupportsDelete
> ------------------------------------
>
> Key: SPARK-33623
> URL: https://issues.apache.org/jira/browse/SPARK-33623
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.1.0
> Reporter: Anton Okolnychyi
> Assignee: Anton Okolnychyi
> Priority: Major
> Fix For: 3.1.0
>
>
> The only way to support delete statements right now is to implement \{{SupportsDelete}}. According to its Javadoc, that interface is meant for cases when we can delete data without much effort (e.g. like deleting a complete partition in a Hive table). It is clear we need a more sophisticated API for row-level deletes. That's why it would be beneficial to add a method to \{{SupportsDelete}} so that Spark can check if a source can easily delete data with just having filters or it will need a full rewrite later on. This way, we have more control in the future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org