[
https://issues.apache.org/jira/browse/KUDU-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17228651#comment-17228651
]
ASF subversion and git services commented on KUDU-1563:
-------------------------------------------------------
Commit 5faf79726605e3a5d8b33bd18ce94c8c09241d3f in kudu's branch
refs/heads/master from Grant Henke
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=5faf797 ]
KUDU-1563 Use DELETE_IGNORE in KuduRestore job
This patch changes the KuduRestore job to use DELETE_IGNORE
operations instead of DELETE when the cluster supports ignore
operations.
`session.setIgnoreAllNotFoundRows(true)` is retained to support
falling back to DELETE operations for backward compatibility.
Change-Id: Ib6f6d5a31be77630e79ff1566e796eb5183a5d22
Reviewed-on: http://gerrit.cloudera.org:8080/16683
Reviewed-by: Attila Bukor <abu...@apache.org>
Reviewed-by: Alexey Serbin <aser...@cloudera.com>
Tested-by: Grant Henke <granthe...@apache.org>
> 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)
