[NUTCH-2233] Index-basic incorrect assignment of next fetch time when using Mongodb as storage backend

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.3.1
• Component/s: plugin

Environment

Mongodb, Elasticsearch.

• External issue ID: NUTCH-2045
• Assignee: Unassigned
• Reporter: Pablo Torres
• Created: 24/Feb/16 13:50
• Updated: 20/Jan/17 02:12
• Resolved: 02/Mar/16 15:52

Description

This patch https://issues.apache.org/jira/browse/NUTCH-2045 does not work when using Mongodb as storage since date properties are stored as Longs in mongodb rather than objects, therefore the null date in this case is 0 which is accepted as valid by this patch. The system indexes 01/01/1970 as tstamp.

I found this issue using Mongodb as storage and Elastic Search as index.