[
https://issues.apache.org/jira/browse/KUDU-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039490#comment-17039490
]
ASF subversion and git services commented on KUDU-1563:
-------------------------------------------------------
Commit 14234a62c6dec587d5a8cb6a0ff3e3b3a9154409 in kudu's branch
refs/heads/master from Brock Noland
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=14234a6 ]
[java] KUDU-1563. Add support for INSERT_IGNORE
Implements java support for the `INSERT_IGNORE' operation.
I manually tested this against an old server version without
INSERT_IGNORE operation support and it returns the correct
error with a message that says: “Unknown operation type: 10”.
Change-Id: Ib0cc4a533dfb01a883d347c9795c165aa8efa3fd
Reviewed-on: http://gerrit.cloudera.org:8080/4523
Tested-by: Kudu Jenkins
Reviewed-by: Adar Dembo <[email protected]>
> 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, 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)
