nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrzej Bialecki (JIRA)" <>
Subject [jira] Commented: (NUTCH-882) Design a Host table in GORA
Date Fri, 01 Oct 2010 12:45:33 GMT


Andrzej Bialecki  commented on NUTCH-882:

Do─čacan, I missed your previous comment... the issue with partial bloom filters is usually
solved that each task stores each own filter - this worked well for MapFile-s because they
consisted of multiple parts, so then a Reader would open a part and a corresponding bloom

Here it's more complicated, I agree... though this reminds me of the situation that is handled
by DynamicBloomFilter: it's basically a set of Bloom filters with a facade that hides this
fact from the user. Here we could construct something similar, i.e. don't merge partial filters
after closing the output, but instead when opening a Reader read all partial filters and pretend
they are one.

> Design a Host table in GORA
> ---------------------------
>                 Key: NUTCH-882
>                 URL:
>             Project: Nutch
>          Issue Type: New Feature
>    Affects Versions: 2.0
>            Reporter: Julien Nioche
>            Assignee: Julien Nioche
>             Fix For: 2.0
>         Attachments: hostdb.patch, NUTCH-882-v1.patch
> Having a separate GORA table for storing information about hosts (and domains?) would
be very useful for : 
> * customising the behaviour of the fetching on a host basis e.g. number of threads, min
time between threads etc...
> * storing stats
> * keeping metadata and possibly propagate them to the webpages 
> * keeping a copy of the robots.txt and possibly use that later to filter the webtable
> * store sitemaps files and update the webtable accordingly
> I'll try to come up with a GORA schema for such a host table but any comments are of
course already welcome 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message