[
https://issues.apache.org/jira/browse/HBASE-13787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563891#comment-14563891
]
Gabor Liptak commented on HBASE-13787:
--------------------------------------
In examples:
org.apache.hadoop.hbase.client.example.BufferedMutatorExample uses
org.apache.hadoop.util.ToolRunner which uses
org.apache.hadoop.util.GenericOptionsParser which uses
org.apache.commons.cli.CommandLine
org.apache.hadoop.hbase.mapreduce.IndexBuilder uses
org.apache.hadoop.util.GenericOptionsParser which uses
org.apache.commons.cli.CommandLine, and reads two other parameters directly
from args
org.apache.hadoop.hbase.mapreduce.SampleUploader uses
org.apache.hadoop.util.GenericOptionsParser which uses
org.apache.commons.cli.CommandLine, and reads two other parameters directly
from args
org.apache.hadoop.hbase.thrift.DemoClient parses arguments directly
org.apache.hadoop.hbase.thrift.HttpDoAsClient parses arguments directly
org.apache.hadoop.hbase.thrift2.DemoClient parses arguments directly
> use a cli argument parsing library instead of ad-hoc string handling
> --------------------------------------------------------------------
>
> Key: HBASE-13787
> URL: https://issues.apache.org/jira/browse/HBASE-13787
> Project: HBase
> Issue Type: Sub-task
> Components: mapreduce, util
> Reporter: Sean Busbey
>
> several of our mapreduce based tools manually parse strings or rely on system
> properties for hteir configuration. update all to use the same cli argument
> parsing library.
> The particular library used isn't important, but it should be one we already
> bring in for some other reason.
> If possible try to make the arguments consistent across all the tools, since
> you'll be looking broadly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
