hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (Jira)" <>
Subject [jira] [Commented] (HIVE-21487) COMPLETED_COMPACTIONS and COMPACTION_QUEUE table missing appropriate indexes
Date Tue, 25 Feb 2020 19:23:00 GMT


Hive QA commented on HIVE-21487:

Here are the results of testing the latest attachment:

{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), 18073 tests executed
*Failed tests:*
org.apache.hadoop.hive.ql.TestMTQueries.testMTQueries1 (batchId=281)

Test results:
Console output:
Test logs:

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

This message is automatically generated.

ATTACHMENT ID: 12994557 - PreCommit-HIVE-Build

> COMPLETED_COMPACTIONS and COMPACTION_QUEUE table missing appropriate indexes
> ----------------------------------------------------------------------------
>                 Key: HIVE-21487
>                 URL:
>             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-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

View raw message