[
https://issues.apache.org/jira/browse/KUDU-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17223965#comment-17223965
]
ASF subversion and git services commented on KUDU-1563:
-------------------------------------------------------
Commit 24943aa5e51d25c532f20887fd21b246c973021c in kudu's branch
refs/heads/master from Grant Henke
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=24943aa ]
KUDU-1563: Fix DELETE_IGNORE operations with extra columns set
In commit 17fb5a1 the Java client was enhanced to support extra
columns set on DELETE operations. This patch ensures the same
functionality works with DELETE_IGNORE operations.
Change-Id: I179c2085c5061c71dc010929056247340f062b8c
Reviewed-on: http://gerrit.cloudera.org:8080/16682
Tested-by: Grant Henke <granthe...@apache.org>
Reviewed-by: Andrew Wong <aw...@cloudera.com>
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)
