[
https://issues.apache.org/jira/browse/IMPALA-9163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong updated IMPALA-9163:
----------------------------------
Component/s: Backend
> Log more information about duplicate row errors when inserting into Kudu
> ------------------------------------------------------------------------
>
> Key: IMPALA-9163
> URL: https://issues.apache.org/jira/browse/IMPALA-9163
> Project: IMPALA
> Issue Type: Wish
> Components: Backend
> Reporter: Andrew Wong
> Priority: Major
> Labels: kudu, usability
>
> When inserting rows into a Kudu table wherein some row keys already exist,
> depending on the expectations of the dataset, it might be nice to know which
> write operations were rejected due to a duplicate key error. Today, when
> inserting such rows through Hue or Impala shell, users are met with a more
> general error:
> {{Key already present in Kudu table
> 'default.loadgen_auto_157eac2da1dc4df2824c9a1d51bb3f3f'.}}
> While this nicely avoids excessive error messages (per IMPALA-3704) when
> there are many duplicate rows, in cases where few duplicate rows are
> expected, knowing exactly which rows offended the uniqueness constraint might
> be nice instead. Not sure what exact form factor this might take, but it
> seems like it'd be a usability win in some cases.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
