[
https://issues.apache.org/jira/browse/NUTCH-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Markus Jelsma updated NUTCH-1028:
---------------------------------
Description:
The parser can take ages (many hours) to complete. During this time the only
output is an error or warning if it's unable to parse something (which is very
common). Sometimes the parser can run for several hours without any output:
this is scary. I propose to add a LOG.info to the mapper and write the key when
parsing, similar to the fetcher.
Thoughts?
was:The parser can take ages (many hours) to complete. During this time the
only output is an error or warning if it's unable to parse something (which is
very common). Sometimes the parser can run for several hours without any
output: this is scary. I propose to add a LOG.info to the mapper and write the
key when parsing, similar to the fetcher.
> Log parser keys
> ---------------
>
> Key: NUTCH-1028
> URL: https://issues.apache.org/jira/browse/NUTCH-1028
> Project: Nutch
> Issue Type: Task
> Reporter: Markus Jelsma
> Priority: Trivial
> Fix For: 1.4, 2.0
>
>
> The parser can take ages (many hours) to complete. During this time the only
> output is an error or warning if it's unable to parse something (which is
> very common). Sometimes the parser can run for several hours without any
> output: this is scary. I propose to add a LOG.info to the mapper and write
> the key when parsing, similar to the fetcher.
> Thoughts?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
