[
https://issues.apache.org/jira/browse/IMPALA-7007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471256#comment-16471256
]
Dan Hecht commented on IMPALA-7007:
-----------------------------------
Probably overflowing this:
{code:java}
// Error message exchange format
struct TErrorLogEntry {
// Number of error messages reported using the above identifier
1: i32 count = 0 <====== 32-bits
// Sample messages from the above error code
2: list<string> messages
}
{code}
> Kudu duplicate key count can be off
> -----------------------------------
>
> Key: IMPALA-7007
> URL: https://issues.apache.org/jira/browse/IMPALA-7007
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 2.12.0
> Reporter: Balazs Jeszenszky
> Priority: Major
>
> After inserting TPC-H data into Kudu by doing:
> {code}
> insert into lineitem select * from PARQUETIMPALA500.LINEITEM
> {code}
> , the query profile contains this error:
> {code}
> Errors: Key already present in Kudu table 'impala::kudu_impala_500.LINEITEM'.
> (1 of -1831809966 similar)
> {code}
> Clearly, the count is off here. Also, it seems this issue can trigger a
> DCHECK on debug builds. The accompanying log line in that case is:
> {code}
> F0507 09:46:12.673912 29258 error-util.cc:148] Check failed: log_entry.count
> > 0 (-1831809966 vs. 0)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
