hive-issues mailing list archives

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


Peter Vary commented on HIVE-21443:

So the original failures:
 * resourceplan - Runs the changed {{hive-schema-4.0.0.hive.sql}}, so the q.out has to be
 * strict_managed_tables_sysdb - Runs the changed {{hive-schema-4.0.0.hive.sql}}, so the
q.out has to be updated
 * sysdb - The transaction/compaction data is not cleaned up between the runs - could cause
flakiness depending on the batch queries. Needed to change {{QTestUtil.clearTestSideEffects}}
to drop and recreate transactional data

The failure found by [~gopalv]: Unrelated issue caused by HIVE-21554

Have a green run. [~kgyrtkirk]/[~vgarg]/[~gopalv] review please?

Thanks, and sorry for the extra rounds!


> 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