accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Newton (JIRA)" <>
Subject [jira] [Resolved] (ACCUMULO-1513) Shell du command doesn't work unless in table context
Date Thu, 20 Jun 2013 17:33:21 GMT


Eric Newton resolved ACCUMULO-1513.

    Resolution: Fixed

root@test> du
2013-06-20 13:30:01,124 [shell.Shell] ERROR: java.lang.IllegalStateException: Not in a table
context. Please use 'table <tableName>' to switch to a table, or use '-t' to specify
a table if option is available.
root@test> du -t test_ingest
               4,342,325 [test_ingest]
root@test> table test_ingest
root@test test_ingest> du
               4,342,325 [test_ingest]
root@test test_ingest> du -t !METADATA
                   2,035 [!METADATA]
root@test test_ingest> du !METADATA
                   2,035 [!METADATA]
> Shell du command doesn't work unless in table context
> -----------------------------------------------------
>                 Key: ACCUMULO-1513
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: shell
>    Affects Versions: 1.5.0
>            Reporter: Billie Rinaldi
>            Assignee: Eric Newton
>             Fix For: 1.5.1, 1.6.0
> The du command is borrowing some of our standard TableOperation syntax but not all of
it, and it's confusing.  For other table operations, you can either specify a table name as
in "command -t tableName", or enter a table context with "table tableName" and then enter
just "command".
> Du takes a list of tables.  Currently it doesn't work unless you're in a table context.
 When you're in a table context, it adds that table to the list of tables specified for the
> My initial thought is that it should ignore the table context entirely, just take the
list of tables and du them.  I'm not sure it makes a lot of sense to run "table t1", "du t2",
and get back the results of "du t1 t2".  On the other hand, I could see it being useful to
just run du with no options in a table context and get back the du for that table, so I'm
neutral on implementing this.  However, we should definitely make du work outside of a table

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message