[ https://issues.apache.org/jira/browse/KUDU-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16723538#comment-16723538 ]
Mike Percy commented on KUDU-1563: ---------------------------------- I know I'm late to this party. I think it's worth modeling what SQL does and INSERT IGNORE in that context operates at a batch or operation level, not a session level. So it seems more of an impedance match to keep this type of error handling configuration at the operation or batch level from a client API perspective to avoid requiring SQL clients to constantly be setting session options if they are caching sessions. > 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: 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)