[ 
https://issues.apache.org/jira/browse/HIVE-13353?focusedWorklogId=818833&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-818833
 ]

ASF GitHub Bot logged work on HIVE-13353:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 20/Oct/22 15:09
            Start Date: 20/Oct/22 15:09
    Worklog Time Spent: 10m 
      Work Description: deniskuzZ commented on code in PR #3608:
URL: https://github.com/apache/hive/pull/3608#discussion_r1000765761


##########
standalone-metastore/metastore-server/src/main/java/org/apache/hadoop/hive/metastore/txn/TxnUtils.java:
##########
@@ -565,4 +566,75 @@ public static String findUserToRunAs(String location, 
Table t, Configuration con
         UserGroupInformation.getLoginUser(), t.getOwner());
     throw new IOException("Unable to stat file: " + p);
   }
+
+  public static String compactorStateToResponse(char s) {

Review Comment:
   same method is in TxnHandler, should we remove it from there?





Issue Time Tracking
-------------------

    Worklog Id:     (was: 818833)
    Time Spent: 7h 20m  (was: 7h 10m)

> SHOW COMPACTIONS should support filtering options
> -------------------------------------------------
>
>                 Key: HIVE-13353
>                 URL: https://issues.apache.org/jira/browse/HIVE-13353
>             Project: Hive
>          Issue Type: Improvement
>          Components: Transactions
>    Affects Versions: 1.3.0, 2.0.0
>            Reporter: Eugene Koifman
>            Assignee: KIRTI RUGE
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: HIVE-13353.01.patch
>
>          Time Spent: 7h 20m
>  Remaining Estimate: 0h
>
> Since we now have historical information in SHOW COMPACTIONS the output can 
> easily become unwieldy. (e.g. 1000 partitions with 3 lines of history each)
> this is a significant usability issue
> Need to add ability to filter by db/table/partition
> Perhaps would also be useful to filter by status



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to