[ http://issues.apache.org/jira/browse/NUTCH-54?page=comments#action_64320 ] Andrzej Bialecki commented on NUTCH-54: ----------------------------------------
In the current workflow ParseStatus doesn't really need to be persistent (except for nicer error reporting when analyzing segment data). That's why I made it a field of Parse, because Parse itself is not persistent, only its fields are. ParseStatus extends and takes over the role of FetcherOutput.CANT_PARSE. This status code is currently not in use by any other part of the system except in Fetcher and ParseSegment to control a part of the logic flow, and since ParseStatus would replace it in this role I propose to remove it. Do you think it would be good to persist ParseStatus for other reasons? Then I agree that it should be moved to ParseData. > Fetcher improvements > --------------------- > > Key: NUTCH-54 > URL: http://issues.apache.org/jira/browse/NUTCH-54 > Project: Nutch > Type: Improvement > Components: fetcher > Reporter: Andrzej Bialecki > Assignee: Andrzej Bialecki > Attachments: parsestatus.patch > > Fetcher improvements. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
