You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@nutch.apache.org by "Markus Jelsma (Closed) (JIRA)" <ji...@apache.org> on 2011/12/20 12:31:31 UTC

[jira] [Closed] (NUTCH-1028) Log parser keys

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

Markus Jelsma closed NUTCH-1028.
--------------------------------


Bulk close of resolved issues of 1.4. bulkclose-1.4-20111220
                
> Log parser keys
> ---------------
>
>                 Key: NUTCH-1028
>                 URL: https://issues.apache.org/jira/browse/NUTCH-1028
>             Project: Nutch
>          Issue Type: Task
>            Reporter: Markus Jelsma
>            Assignee: Markus Jelsma
>            Priority: Trivial
>             Fix For: 1.4
>
>         Attachments: NUTCH-1028-1.4-1.patch
>
>
> 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.
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