[ http://issues.apache.org/jira/browse/NUTCH-323?page=all ]
Stefan Groschupf updated NUTCH-323: ----------------------------------- Attachment: MapWritableCopyConstructor.patch Attached patch add a copy constructor to the map writable and use it in the CrawlDatum.set methode. However there are more methods in the code where meta data are passed from one CrawlDatum to a other, but I don't can see any risk of concurent usage of the mapWritable there. > CrawlDatum.set just reference a mapWritable of a other object but not copy it. > ------------------------------------------------------------------------------ > > Key: NUTCH-323 > URL: http://issues.apache.org/jira/browse/NUTCH-323 > Project: Nutch > Issue Type: Bug > Affects Versions: 0.8-dev > Reporter: Stefan Groschupf > Priority: Critical > Fix For: 0.8-dev > > Attachments: MapWritableCopyConstructor.patch > > > Using CrawlDatum.set(aOtherCrawlDatum) copies the data from one CrawlDatum to > a other. > Also a reference of the MapWritable is passed. Means both project share the > same mapWritable and its content. > This causes problems with concurent manipulate mapWritables and its key-value > tuples. -- 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