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

Posted to dev@nutch.apache.org by "Pablo Torres (JIRA)" <ji...@apache.org> on 2016/03/02 16:53:18 UTC

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

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

Pablo Torres closed NUTCH-2233.
-------------------------------
    Resolution: Duplicate

> Index-basic incorrect assignment of next fetch time when using Mongodb as storage backend
> -----------------------------------------------------------------------------------------
>
>                 Key: NUTCH-2233
>                 URL: https://issues.apache.org/jira/browse/NUTCH-2233
>             Project: Nutch
>          Issue Type: Bug
>          Components: plugin
>    Affects Versions: 2.3.1
>         Environment: Mongodb, Elasticsearch.
>            Reporter: Pablo Torres
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)