[
https://issues.apache.org/jira/browse/HBASE-20286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426208#comment-16426208
]
Appy commented on HBASE-20286:
------------------------------
That issue is unrelated, it's about how to handle values returned by commands
in interactive mode, and not about whether commands should return values or
note in the first place.
{quote}I believe users don't really rely on this hidden command, the idea of a
compaction_state command came from a testing task.
{quote}
Can't know for sure, so let's put it back? Almost everything start with some
idea and outgrows its initial scope. It's plausible that someone can be using
it in a script as some sort of wait condition.
> Improving shell command compaction_state
> ----------------------------------------
>
> Key: HBASE-20286
> URL: https://issues.apache.org/jira/browse/HBASE-20286
> Project: HBase
> Issue Type: Improvement
> Components: shell
> Reporter: Csaba Skrabak
> Priority: Minor
> Attachments: HBASE-20286.patch
>
>
> Command does not output anything, let's add a formatter.row call.
> We should include the possible outputs in the help text.
> *Further improvement possibility.* This command can be used for checking if
> the compaction is done but very impractical if one wants to wait _until_ it
> is done. Wish there would be a flag in the shell that enforces synchronous
> compactions, that is, every time you issue a compact or major_compact in the
> shell while this flag is set, you won't get back the prompt until it finishes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)