nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrzej Bialecki (JIRA)" <>
Subject [jira] Commented: (NUTCH-407) Make Nutch crawling parent directories for file protocol configurable
Date Mon, 27 Nov 2006 08:42:22 GMT
    [ ] 
Andrzej Bialecki  commented on NUTCH-407:

As far as I understand it, the original issue that you refer to (and your issue) both come
from misconfigured URLFilters - I don't understand why this fix is needed if you configure
them properly.

First, let's establish the names for directions - normally "up" refers to a parent directory,
and "down" refers to a child directory.

Current behavior is to collect ANY urls that we find pointing out from the current URL, unless
prohibited by filters. In case of crawling local FS, unless you prohibit it in URLFilters
from collecting parent dirs it will also collect such URLs - that's why it behaved the way
it did. This behavior is consistent with HTTP and FTP crawling.

So, instead of your "special case" fix you should simply put the root directory in your URLFilters
configuration. E.g. for urlfilter-regex you should put the following in regex-urlfilter.txt


> Make Nutch crawling parent directories for file protocol configurable
> ---------------------------------------------------------------------
>                 Key: NUTCH-407
>                 URL:
>             Project: Nutch
>          Issue Type: Improvement
>    Affects Versions: 0.8
>            Reporter: Thorsten Scherler
>         Attachments: 407.fix.diff
> I am looking into fixing some very weird behavior of the file protocol.
> I am using 0.8.
> Researching this topic I found 
> and
> I am on Ubuntu but I have the same problem that nutch is going down the
> tree (including parents) and not up (including children from the root
> url).
> Further I would vote to make the fetch-parents optional and defined per
> a property whether I would like this not very intuitive "feature".

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message