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

2014-01-13 Thread Hudson (JIRA)

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

Hudson commented on NUTCH-1667:
---

SUCCESS: Integrated in Nutch-nutchgora #884 (See 
[https://builds.apache.org/job/Nutch-nutchgora/884/])
NUTCH-1667 Updatedb always ignore batchId (lewismc: 
http://svn.apache.org/viewvc/nutch/branches/2.x/?view=rev&rev=1557705)
* /nutch/branches/2.x/CHANGES.txt
* /nutch/branches/2.x/src/java/org/apache/nutch/crawl/DbUpdaterJob.java


> 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: Tien Nguyen Manh
>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.5#6160)


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

2013-12-01 Thread Otis Gospodnetic (JIRA)

[ 
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)


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

2013-11-22 Thread lufeng (JIRA)

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

lufeng commented on NUTCH-1667:
---

yes, u are right. +1

> 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
> 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)