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

Brock Noland edited comment on KUDU-1563 at 11/8/16 4:07 PM:
-------------------------------------------------------------

[~danburkert] [~wdberkeley] - what are your thoughts? From a high level, this 
is similar to the first approach 
[here|https://issues.apache.org/jira/browse/KUDU-1563?focusedCommentId=15504136&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15504136]

[~mjacobs] - 

1. The patch is nearing completion: https://gerrit.cloudera.org/#/c/4491/
2. I don't believe this is an error: "an UPDATE/DELETE and ignore cases where 
maybe there's no row found for the PK." It's just "no rows affected" right?


was (Author: brocknoland):
[~danburkert] [~wdberkeley] - what are your thoughts? From a high level, this 
is similar to this approach 
[here|https://issues.apache.org/jira/browse/KUDU-1563?focusedCommentId=15504136&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15504136]

[~mjacobs] - 

1. The patch is nearing completion: https://gerrit.cloudera.org/#/c/4491/
2. I don't believe this is an error: "an UPDATE/DELETE and ignore cases where 
maybe there's no row found for the PK." It's just "no rows affected" right?

> 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
>              Labels: 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
(v6.3.4#6332)

Reply via email to