[
https://issues.apache.org/jira/browse/HIVE-21487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17045758#comment-17045758
]
Hive QA commented on HIVE-21487:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12994634/HIVE-21487.07.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 18073 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/20838/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/20838/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-20838/
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
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12994634 - PreCommit-HIVE-Build
> COMPLETED_COMPACTIONS and COMPACTION_QUEUE table missing appropriate indexes
> ----------------------------------------------------------------------------
>
> Key: HIVE-21487
> URL: https://issues.apache.org/jira/browse/HIVE-21487
> Project: Hive
> Issue Type: Bug
> Affects Versions: 3.1.1
> Reporter: Todd Lipcon
> Assignee: László Pintér
> Priority: Major
> Attachments: HIVE-21487.03.patch, HIVE-21487.04.patch,
> HIVE-21487.05.patch, HIVE-21487.06.patch, HIVE-21487.07.patch,
> HIVE-21847.01.patch, HIVE-21847.02.patch
>
>
> Looking at a MySQL install where HMS is pointed on Hive 3.1, I see a constant
> stream of queries of the form:
> {code}
> select CC_STATE from COMPLETED_COMPACTIONS where CC_DATABASE =
> 'tpcds_orc_exact_1000' and CC_TABLE = 'catalog_returns' and CC_PARTITION =
> 'cr_returned_date_sk=2452851' and CC_STATE != 'a' order by CC_ID desc;
> {code}
> but the COMPLETED_COMPACTIONS table has no index. In this case it's resulting
> in a full table scan over 115k rows, which takes around 100ms.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
