[ 
https://issues.apache.org/jira/browse/HIVE-21443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798322#comment-16798322
 ] 

Peter Vary commented on HIVE-21443:
-----------------------------------

[~gopalv], [~tlipcon]: I think adding this to the sys.COMPACTIONS could be done 
adding the new tables here. See: 
[https://github.com/apache/hive/blob/master/metastore/scripts/upgrade/hive/hive-schema-4.0.0.hive.sql]

As a follow-up jira, maybe the SQL scripts creating the schema should be moved 
to the standalone-metastore directory as well (just to make the review easier).

Is it enough to have the same data exposed as for the SHOW COMPACTIONS command?:
 * CompactionId
 * Database
 * Table
 * Partition
 * Type
 * State
 * Hostname
 * Worker
 * Start Time
 * Duration(ms)
 * HadoopJobId

The missing columns are:
 * CC_TBLPROPERTIES varchar(2048),
 * CC_WORKER_ID varchar(128),
 * CC_RUN_AS varchar(128),
 * CC_HIGHEST_WRITE_ID bigint,
 * CC_META_INFO varbinary(2048),

If you guys do not have an opinion, I would go for the same data as for the 
original command.

What should we do with the SHOW COMPACTIONS command? Will this expose 
dbnames/tablenames/partitionnames for unauthorized users?

Thanks,
 Peter
  

 

> Better usability for SHOW COMPACTIONS
> -------------------------------------
>
>                 Key: HIVE-21443
>                 URL: https://issues.apache.org/jira/browse/HIVE-21443
>             Project: Hive
>          Issue Type: Improvement
>          Components: Transactions
>            Reporter: Todd Lipcon
>            Priority: Major
>
> 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
(v7.6.3#76005)

Reply via email to