[
https://issues.apache.org/jira/browse/HIVE-21398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16792289#comment-16792289
]
Hive QA commented on HIVE-21398:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12962363/HIVE-21398.02.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 15825 tests
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[test_teradatabinaryfile]
(batchId=2)
{noformat}
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/16496/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/16496/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-16496/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12962363 - PreCommit-HIVE-Build
> Columns which has estimated statistics should not be considered as unique keys
> ------------------------------------------------------------------------------
>
> Key: HIVE-21398
> URL: https://issues.apache.org/jira/browse/HIVE-21398
> Project: Hive
> Issue Type: Bug
> Reporter: Zoltan Haindrich
> Assignee: Zoltan Haindrich
> Priority: Major
> Attachments: HIVE-21398.01.patch, HIVE-21398.02.patch
>
>
> Right now for a column to qualify as a unique column it has to meet the
> criteria:
> {code}
> NDV >= numRows
> {code}
> when numRows is 1 this tends to be true ; but numRows is also 1 in cases when
> we are kinda operate in the blind - don't know how many row there are - more
> generatlly: with estimated column statistics.
> As a sideeffect of qualifying all columns to be unique; after a few joins all
> column combinations became unique....so for a join between 3 tables which
> have (i,j,k) columns; then it will allocate {{i*j*k}} triplets of "unique
> column triplets".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
