You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/04/30 05:02:00 UTC

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

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

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

Commit 0ddcaaabc97c85a4715ae79ff5604feb9b342779 in kudu's branch refs/heads/master from Riza Suminto
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=0ddcaaabc ]

[client] KUDU-3351: Add ResourceMetricsPB into WriteResponsePB

KUDU-1563 adds support for INSERT_IGNORE, UPDATE_IGNORE, and
DELETE_IGNORE. However, it was lacking the per-session metrics about how
many rows get ignored vs modified. This patch implements the per-session
metrics by introducing a new ResourceMetricsPB field into the
WriteResponsePB that's populated in every response sent back to the
client.

Change-Id: I9adefd64b0058c66274a00e1b12334653fcab2b3
Reviewed-on: http://gerrit.cloudera.org:8080/18451
Tested-by: Kudu Jenkins
Reviewed-by: Alexey Serbin <al...@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
>             Fix For: 1.14.0
>
>
> 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.20.7#820007)