[
https://issues.apache.org/jira/browse/IMPALA-10465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17274526#comment-17274526
]
Grant Henke commented on IMPALA-10465:
--------------------------------------
It looks like there was once support for an IGNORE keyword in Impala but it was
removed in IMPALA-3710.
That Jira suggests adding it back once transactions are supported by Kudu (that
work is in progress in KUDU-2612), but it likely could be added ahead of that
now that Kudu has explicit ignore operations.
> Support Kudu "ignore" operations
> --------------------------------
>
> Key: IMPALA-10465
> URL: https://issues.apache.org/jira/browse/IMPALA-10465
> Project: IMPALA
> Issue Type: Improvement
> Reporter: Grant Henke
> Priority: Major
>
> Kudu recently added support for INSERT_IGNORE, UPDATE_IGNORE, and
> DELETE_IGNORE to handle cases where users want to ignore primary key errors
> in an efficient way. Impala already does this today for it's INSERT behavior,
> however it does so by ignoring the per-row errors from Kudu client side. This
> requires a large error buffer (which may need to be expanded in rare cases)
> to log all of the warning messages which users often do not care about and
> causes significant RPC overhead.
> Instead it would be good to add a property or special IGNORE keyword to
> leverage the new ignore operations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
