[
https://issues.apache.org/jira/browse/KUDU-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16720459#comment-16720459
]
Brock Noland commented on KUDU-1563:
------------------------------------
Thanks [~r1pp3rj4ck] for picking this up. While I'd like to contribute it, I am
more concerned with getting access to the feature. Is this something you have
bandwidth to work on now?
bq. I agree that operation level is more intuitive and more flexible, though I
don't really see a use case for that added flexibility. Can you articulate one?
I don't have a use case. Only a that feels slightly odd changing a session
level parameter to define how a operation behaves. I am fine with the suggested
approach it'll just take more work to implement.
> 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: Attila Bukor
> 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)
