You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Eric Newton (JIRA)" <ji...@apache.org> on 2013/06/14 17:33:20 UTC
[jira] [Updated] (ACCUMULO-1513) Shell du command doesn't work
unless in table context
[ https://issues.apache.org/jira/browse/ACCUMULO-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Newton updated ACCUMULO-1513:
----------------------------------
Assignee: Eric Newton
> Shell du command doesn't work unless in table context
> -----------------------------------------------------
>
> Key: ACCUMULO-1513
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1513
> Project: Accumulo
> Issue Type: Bug
> Components: shell
> Affects Versions: 1.5.0
> Reporter: Billie Rinaldi
> Assignee: Eric Newton
>
> 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 command.
> 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 context.
--
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: http://www.atlassian.com/software/jira