hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-21443) Better usability for SHOW COMPACTIONS
Date Sun, 31 Mar 2019 16:33:00 GMT


Hive QA commented on HIVE-21443:

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 due to 2 test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 15883 tests passed

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

This message is automatically generated.

ATTACHMENT ID: 12964364 - PreCommit-HIVE-Build

> Better usability for SHOW COMPACTIONS
> -------------------------------------
>                 Key: HIVE-21443
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Transactions
>            Reporter: Todd Lipcon
>            Assignee: Peter Vary
>            Priority: Major
>         Attachments: HIVE-21443.02.patch, HIVE-21443.03.patch, HIVE-21443.addendum.patch,
> Currently on a test cluster the output of 'SHOW COMPACTIONS' has 117k rows. This makes
it basically useless to work with.
> For better usability, we should support syntax like 'SHOW COMPACTIONS IN <database>'
or maybe 'SHOW COMPACTIONS ON <table>' (particular syntax to be chosen for consistency
with other operations I suppose).
> Alternatively (or maybe in addition) it seems like it would be nice to expose the same
data in a queryable table (eg in information_schema or a system namespace) so that I could
do things like: SELECT dbname, state, count(*) from compactions group by 1,2;

This message was sent by Atlassian JIRA

View raw message