accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-107) shell's GrepCommand sets options under same flag
Date Tue, 01 Nov 2011 19:41:32 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

John Vines updated ACCUMULO-107:
--------------------------------

    Affects Version/s:     (was: 1.4.0)
        Fix Version/s:     (was: 1.4.0)

For 1.5 I think we want to create a master map of Options to use so we can be aware of everything
used.
                
> shell's GrepCommand sets options under same flag
> ------------------------------------------------
>
>                 Key: ACCUMULO-107
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-107
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.3.5, 1.5.0
>            Reporter: John Vines
>            Assignee: Billie Rinaldi
>             Fix For: 1.5.0
>
>
> The shell sets two options for GrepCommand (and child class EgrepCommand) - numThreads
and table. numThreads uses the flag "t" while table uses an enum which is "t". Not only that,
but GrepCommand extends ScanCommand (and also calls the super.getOptions) which also sets
the table Option. The strange part is that num-threads takes precedence even though it's sandwiched
within calls. This may call for a check of all Shell Commands to make sure this isn't done
elsewhere. We may want to create of a master index of Shell options to make sure we don't
have this collision space again.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message