[jira] [Commented] (IMPALA-10465) Improve Kudu DML error logging in Impala

["Riza Suminto (Jira)" <ji...@apache.org>]

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

Riza Suminto commented on IMPALA-10465:
---------------------------------------

It is probably OK for impala to switch to using IGNORE variant of Kudu write operation by default (IMPALA-3710).

For multi-row transaction though ([IMPALA-10557|http://issues.apache.org/jira/browse/IMPALA-10557]), there is a value to keep using the non-IGNORE write operation because it can then inform Impala to abort the transaction.

> Improve Kudu DML error logging in Impala
> ----------------------------------------
>
>                 Key: IMPALA-10465
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10465
>             Project: IMPALA
>          Issue Type: Improvement
>            Reporter: Grant Henke
>            Assignee: Riza Suminto
>            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.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org