[
https://issues.apache.org/jira/browse/NUTCH-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Markus Jelsma updated NUTCH-1024:
---------------------------------
Attachment: Nutch.patch
AdaptiveFetchSchedule.patch
MimeAdaptiveFetchSchedule.java
adaptive-mimetypes.txt
Here's a first WIP. It extends AdaptiveFetchSchedule and changes INC/DEC rates
depending on current MIME-type. It also patches AdaptiveFetch so that INC and
DEC properties are protected and settable from the child. I also added two
propertis to metadata.Nutch for reading the Content-Type key as Writable from
the CrawlDatum MetaData. That was a bit of trickery.
It uses original INC and DEC rate values for CrawlDatum without a Content-Type
in their MetaData or with unconfigured Content-Types.
Please comment. There must be something wrong as it seems to work. :)
> Dynamically set fetchInterval by MIME-type
> ------------------------------------------
>
> Key: NUTCH-1024
> URL: https://issues.apache.org/jira/browse/NUTCH-1024
> Project: Nutch
> Issue Type: New Feature
> Reporter: Markus Jelsma
> Assignee: Markus Jelsma
> Priority: Minor
> Fix For: 2.0
>
> Attachments: AdaptiveFetchSchedule.patch,
> MimeAdaptiveFetchSchedule.java, Nutch.patch, adaptive-mimetypes.txt
>
>
> Add facility to configure default or fixed fetchInterval values by MIME-type.
> This is useful for conserving resources for files that are known to change
> frequently or never and everything in between.
> * simple key\tvalue\n configuration file
> * only set fetchInterval for new documents
> * keep max fetchInterval fixed by current config
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
