[ https://issues.apache.org/jira/browse/KUDU-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821303#comment-16821303 ]
Grant Henke commented on KUDU-1563: ----------------------------------- This would be a useful optimization for full restore (via Spark) optimizations. Right now we use UPSERT in case a spark task needs to be retried, but in the case of a failed Spark task that means we UPSERT all the rows that previously succeeded again. > Add support for INSERT IGNORE > ----------------------------- > > Key: KUDU-1563 > URL: https://issues.apache.org/jira/browse/KUDU-1563 > Project: Kudu > Issue Type: New Feature > Reporter: Dan Burkert > Assignee: Brock Noland > Priority: Major > Labels: backup, newbie > > 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 (v7.6.3#76005)