[
https://issues.apache.org/jira/browse/KUDU-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17228650#comment-17228650
]
ASF subversion and git services commented on KUDU-1563:
-------------------------------------------------------
Commit 7fbe341e51a9e4245d8b3017cecf11e393c3a22b in kudu's branch
refs/heads/master from Grant Henke
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=7fbe341 ]
KUDU-1563 Support ignore operations in kudu-spark
This patch adds support for the INSERT_IGNORE, UPDATE_IGNORE,
and DELETE_IGNORE operations into the Kudu Spark integration.
It leverages `AsyncKuduClient.supportsIgnoreOperations()` to
handle INSERT_IGNORE operations in a compatible way.
Change-Id: If4b4dc0ec996a88afead0f9da0024457e568b0f4
Reviewed-on: http://gerrit.cloudera.org:8080/16681
Reviewed-by: Attila Bukor <abu...@apache.org>
Tested-by: Kudu Jenkins
Reviewed-by: Alexey Serbin <aser...@cloudera.com>
> Add support for INSERT/UPDATE/DELETE IGNORE
> -------------------------------------------
>
> Key: KUDU-1563
> URL: https://issues.apache.org/jira/browse/KUDU-1563
> Project: Kudu
> Issue Type: New Feature
> Reporter: Dan Burkert
> Assignee: Grant Henke
> Priority: Major
> Labels: backup, impala, roadmap-candidate
>
> The Java client currently has an [option to ignore duplicate row key errors|
> https://kudu.apache.org/apidocs/org/kududb/client/AsyncKuduSession.html#setIgnoreAllDuplicateRows-boolean-],
> which is implemented by filtering the errors on the client side. If we are
> going to continue to support this feature (and the consensus seems to be that
> we probably should), we should promote it to a first class operation type
> that is handled on the server side. This would have a modest perf.
> improvement since less errors are returned, and it would allow INSERT IGNORE
> ops to be mixed in the same batch as other INSERT, DELETE, UPSERT, etc. ops.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
