[
https://issues.apache.org/jira/browse/KUDU-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039497#comment-17039497
]
Grant Henke commented on KUDU-1563:
-----------------------------------
The INSERT_IGNORE op (duplicate PK only) and client support patches were
committed. I am leaving this open to track remaining work I expect to complete:
* Add DELETE_INGORE (missing PK only)
* Add UPDATE_IGNORE (missing PK only)
* Add feature handling for backwards compatibility (this allows me to replace
workaround implementations safely)
* Update workaround implementations to use new ops when the server supports it
(Backup, Spark, NiFi)
* Document the new IGNORE ops
* File Jira about optionally ignoring other errors with the IGNORE operations
and wait to see demand/need.
** The current plan is to leverage session configs to adjust was is ignored.
> 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, roadmap-candidate
>
> 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.3.4#803005)
