[
https://issues.apache.org/jira/browse/NUTCH-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13612263#comment-13612263
]
Roland von Herget commented on NUTCH-1393:
------------------------------------------
This patch adds:
{code}
if (args.length <= 0) {
...
}
{code}
So, now we have to start the generatorJob this way:
{code}
./bin/nutch generate -x
{code}
(else you will just get the usage info)
> Display consistent usage of GeneratorJob with 1.X
> -------------------------------------------------
>
> Key: NUTCH-1393
> URL: https://issues.apache.org/jira/browse/NUTCH-1393
> Project: Nutch
> Issue Type: Bug
> Components: administration gui, generator
> Affects Versions: nutchgora
> Reporter: Lewis John McGibbney
> Fix For: 2.2
>
> Attachments: NUTCH-1393.patch, NUTCH-1393-v2.patch,
> NUTCH-1393-v3.patch
>
>
> If we pass the generate argument to the nutch script, the Generator
> auto-spings into action and begins generating fetchlists. This should not be
> the case, instead it should print traditional usage to stdout. An example is
> below
> {code}
> lewis@lewis:~/ASF/nutchgora/runtime/local$ ./bin/nutch generate
> GeneratorJob: Selecting best-scoring urls due for fetch.
> GeneratorJob: starting
> GeneratorJob: filtering: true
> GeneratorJob: done
> GeneratorJob: generated batch id: 1339628223-1694200031
> {code}
> All I wanted to do was get the usage params printed to stdout but instead it
> generated my batch willy nilly.
--
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
