Hi Andrzej

Even i had done the first thing when i added lines to IndexMerger

Thanks for the change..

I was wondering when we recreate a master index from the segments, how will
it behave.

Say that a content has changed and new thing has been fetched and parsed.

When the index merger is run and the entire index is rebuilt, will the entry
from the old one be removed and  only the new one remain.(I am rebuilding
the index to fasten up search)

So will the old index also remain and show up in search result


Rgds
Prabhu




On 3/7/06, Andrzej Bialecki <[EMAIL PROTECTED]> wrote:
>
> Andrzej Bialecki wrote:
> > D.Saravanaraj wrote:
> >> Hi  Andrzej,
> >>
> >> I applied your patch for adaptive refetch. In the Indexer.java, the
> case
> >> statement for STATUS_FETCH_UNMODIFIED is missing in the reduce()
> >> method. I
> >> hope a simple break statement is to be added there.
> >>
> >
> > Good catch!  Yes, this case needs to be added to the list, just next
> > to STATUS_FETCH_GONE.
>
> Actually, I was wrong, please add this (it will be added to the new
> version of the patch):
>
>        case CrawlDatum.STATUS_FETCH_UNMODIFIED:
>          // we don't really have the new version of this page,
>          // so skip it - it's already in some older segment
>          fetchDatum = null;
>          break;
>
>
>
> --
> Best regards,
> Andrzej Bialecki     <><
> ___. ___ ___ ___ _ _   __________________________________
> [__ || __|__/|__||\/|  Information Retrieval, Semantic Web
> ___|||__||  \|  ||  |  Embedded Unix, System Integration
> http://www.sigram.com  Contact: info at sigram dot com
>
>
>

Reply via email to