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

Posted to dev@nutch.apache.org by "Otis Gospodnetic (JIRA)" <ji...@apache.org> on 2013/12/02 02:34:35 UTC

[jira] [Commented] (NUTCH-1667) Updatedb always ignore batchId

    [ https://issues.apache.org/jira/browse/NUTCH-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13836174#comment-13836174 ] 

Otis Gospodnetic commented on NUTCH-1667:
-----------------------------------------

The description mentions batchId, but the patch changes stuff crawlId?
I see [~lewismc] is talking about making a release and may want to commit this simple change before that.

> Updatedb always ignore batchId
> ------------------------------
>
>                 Key: NUTCH-1667
>                 URL: https://issues.apache.org/jira/browse/NUTCH-1667
>             Project: Nutch
>          Issue Type: Bug
>    Affects Versions: 2.3
>            Reporter: Nguyen Manh Tien
>            Priority: Minor
>             Fix For: 2.3
>
>         Attachments: NUTCH-1556-batchId.patch
>
>
> batchId is not set in currentJob because we set batchId after creating currentJob, so in UpdateDbMapper batchId is null and will be assign to -all.
> I change to set batchId befor creating currentJob



--
This message was sent by Atlassian JIRA
(v6.1#6144)