crawlId not supported by all Tools
--
Key: NUTCH-1290
URL: https://issues.apache.org/jira/browse/NUTCH-1290
Project: Nutch
Issue Type: Bug
Components: indexer
Affects Versions: nutchgora
[
https://issues.apache.org/jira/browse/NUTCH-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13218098#comment-13218098
]
Lewis John McGibbney commented on NUTCH-670:
Sure is. Not to worry. Thanks
[
https://issues.apache.org/jira/browse/NUTCH-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriele Kahlout updated NUTCH-1001:
Attachment: (was: nutch-1001_fetcher.patch)
bin/nutch fetch/parse handle
https://issues.apache.org/jira/browse/NUTCH-578
https://issues.apache.org/jira/browse/NUTCH-1245
Is you issue similar to these?
On Tuesday 28 February 2012 14:09:25 Mathijs Homminga wrote:
Hi,
Does anyone know why the AbstractFetchSchedule.forceFetch method sets the
page.status to
Yes, thanks.
It is related. However, it does not apply to DB_GONE pages (only), but to all
pages that have their fetchInterval max interval.
Actually, I'm still a bit puzzled by the scheduling related parameters and the
way the AbstractFetchSchedule handles them.
Why do pages with a
[
https://issues.apache.org/jira/browse/NUTCH-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sujit Pal updated NUTCH-945:
Attachment: patch-NUTCH-945.txt
Patch file to make updates to SolrConstants (add new property),
[
https://issues.apache.org/jira/browse/NUTCH-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sujit Pal updated NUTCH-945:
Attachment: NonPartitioningPartitioner.java
Partitioner that always returns 0 (for handling single SOLR
FYI...awesome!
Begin forwarded message:
From: Jason Trost jason.tr...@gmail.com
Date: February 28, 2012 5:41:23 PM PST
To: common-u...@hadoop.apache.org common-u...@hadoop.apache.org
Subject: [blog post] Accumulo, Nutch, and Gora
Reply-To: common-u...@hadoop.apache.org
8 matches
Mail list logo