[jira] [Commented] (KUDU-1563) Add support for INSERT/UPDATE/DELETE IGNORE

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KUDU-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17222160#comment-17222160 ] 

ASF subversion and git services commented on KUDU-1563:
-------------------------------------------------------

Commit fe65185d9bc23489dc693d5214fb0d2172325737 in kudu's branch refs/heads/master from Grant Henke
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=fe65185 ]

KUDU-1563. Add UPDATE_IGNORE and DELETE_IGNORE operations

This patch adds an UPDATE_IGNORE operation which behaves like
a normal UPDATE except a key not found error will not be raised by the
primary key having not been previously inserted.

This patch also adds a DELETE_IGNORE operation which behaves like
a normal DELETE except a key not found error will not be raised by the
primary key having not been previously inserted.

Follow on patches will add more client support.

Note: This patch is a follow on to https://gerrit.cloudera.org/#/c/4491/.

Change-Id: I11dfd06e8d4d22cf1097fe1ff01a1b97cafaf899
Reviewed-on: http://gerrit.cloudera.org:8080/16661
Tested-by: Kudu Jenkins
Reviewed-by: Alexey Serbin <as...@cloudera.com>
Reviewed-by: Andrew Wong <aw...@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)