[
https://issues.apache.org/jira/browse/NUTCH-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13627917#comment-13627917
]
lufeng commented on NUTCH-1555:
-------------------------------
Hi Lewis, yes, like you said that we can choose an established CLI framework to
enforce more checking. when we use a CLI framework, maybe the command output
like this.
{code:java}
law@CEE279Law3-Linux:~/Downloads/asf/2.x/runtime/local$ ./bin/nutch parse
-batchId updatedb
ParserJob: starting
ParserJob: resuming: false
ParserJob: forced reparse: false
ParserJob: batchId: updatedb
ParserJob: success
{code}
we can not guarantee that user input parameter values are all correct. or maybe
the fast way to fixed this bug is to add -batchId to parse command. but use CLI
framework is a good idea, it can let us parsing command line options more
easily.
I am +1 to port all command line parsing to CLI framework.
> bug in 2.x ParserJob command line parsing
> ------------------------------------------
>
> Key: NUTCH-1555
> URL: https://issues.apache.org/jira/browse/NUTCH-1555
> Project: Nutch
> Issue Type: Bug
> Components: parser
> Affects Versions: 2.1
> Reporter: Lewis John McGibbney
> Fix For: 2.2
>
>
> I just accidentally passed in the following argument to parser job
> {code}
> law@CEE279Law3-Linux:~/Downloads/asf/2.x/runtime/local$ ./bin/nutch parse
> updatedb
> ParserJob: starting
> ParserJob: resuming: false
> ParserJob: forced reparse: false
> ParserJob: batchId: updatedb
> ParserJob: success
> {code}
> This is a bug for sure
--
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
