[
https://issues.apache.org/jira/browse/HBASE-22903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16917097#comment-16917097
]
stack commented on HBASE-22903:
-------------------------------
Two scenarios. Shell starts the operation and then the case where shell did not
start the operation. Both legit.
Your patch looks like it is trying to restore the old get alter schema status;
i.e. a dedicated method added to Admin to look up state on one of the many
operations we run on Master via Admin. It queries using tablename. This route
would seem to dictate a status method for every long-running operation we have
in Admin. We might want to avoid going this route.
A general query on currently running operations that showed detail on each
operation that allowed you narrow in using pid or tablename would be sweet.
Probably more than you are interested in.
On RIT, there is 'status' in the shell (and there is the UI with RIT panel
and/or procedures listing). The status command does simple, detailed, and
replication currently. The 'detailed' prints out a RIT count. You'd want RIT
count for a table I suppose.... listing current RITs?
> alter_status command is broken
> ------------------------------
>
> Key: HBASE-22903
> URL: https://issues.apache.org/jira/browse/HBASE-22903
> Project: HBase
> Issue Type: Bug
> Components: Admin, asyncclient, shell
> Affects Versions: 3.0.0
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: HBASE-22903.master.000.patch,
> HBASE-22903.master.001.patch, HBASE-22903.master.002.patch
>
>
> This is applicable to master branch only:
> {code:java}
> > alter_status 't1'
> ERROR: undefined method `getAlterStatus' for
> #<Java::OrgApacheHadoopHbaseClient::AdminOverAsyncAdmin:0x252ec02e>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
