You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@nutch.apache.org by Ravi Chintakunta <ra...@gmail.com> on 2006/06/06 22:33:19 UTC

Re: Multiple indexes on a single server instance.

See my thread

http://www.mail-archive.com/nutch-user@lucene.apache.org/msg03014.html

where I have modified NutchBean to dynamically pickup the indexes that
have to be searcheed. The web page has checkboxes for each index, and
thus these indexes can be searched in any combination.

- Ravi Chintakunta



On 5/31/06, Andrzej Bialecki <ab...@getopt.org> wrote:
> sudhendra seshachala wrote:
> > Yes. That is wha I am trying. But for some reason it is not working..
> >   Does these fields should be lower case only. ?
> >
>
>
> Preferably. If you use the default NutchDocumentAnalyzer it will
> lowercase field names, so you won't get any match.
>
> --
> Best regards,
> Andrzej Bialecki     <><
>  ___. ___ ___ ___ _ _   __________________________________
> [__ || __|__/|__||\/|  Information Retrieval, Semantic Web
> ___|||__||  \|  ||  |  Embedded Unix, System Integration
> http://www.sigram.com  Contact: info at sigram dot com
>
>
>

Re: Multiple indexes on a single server instance.

Posted by Bud Witney <wi...@osu.edu>.
I would love to see something like that. Currently trying to figure  
out how to convert our htdig solution over to nutch. We use many  
different indexes then merge into searchable groups. We need to group  
by region.

see http://plantfacts.osu.edu/web

We started with phantom , then went to htdig now we wish to use  
NUTCH. We have NUTCH searching well, just don't have any background  
in java to do my own tweaks in code.

-Bud

On Jun 6, 2006, at 4:53 PM, Stefan Neufeind wrote:

> Sounds like others might have use for that as well possibly. Can you
> provide a clean patchset, maybe? How about an "multi-index"-plugin  
> which
> parses a xml-file to find the paths to allow indexes, like
>
> <indexes>
>   <index>
>     <id>index1</id>
>     <path>/data/something/index1</path>
>   </index>
>   <index>
>     <id>index2</id>
>     <path>/data/somethingelse</path>
>   </index>
> </indexes>
>
>
> Regards,
>  Stefan
>
> Ravi Chintakunta wrote:
>> See my thread
>>
>> http://www.mail-archive.com/nutch-user@lucene.apache.org/ 
>> msg03014.html
>>
>> where I have modified NutchBean to dynamically pickup the indexes  
>> that
>> have to be searcheed. The web page has checkboxes for each index, and
>> thus these indexes can be searched in any combination.
>>
>> - Ravi Chintakunta
>>
>>
>>
>> On 5/31/06, Andrzej Bialecki <ab...@getopt.org> wrote:
>>> sudhendra seshachala wrote:
>>>> Yes. That is wha I am trying. But for some reason it is not  
>>>> working..
>>>>   Does these fields should be lower case only. ?
>>>>
>>>
>>>
>>> Preferably. If you use the default NutchDocumentAnalyzer it will
>>> lowercase field names, so you won't get any match.


Re: Multiple indexes on a single server instance.

Posted by Stefan Neufeind <ap...@stefan-neufeind.de>.
Sounds like others might have use for that as well possibly. Can you
provide a clean patchset, maybe? How about an "multi-index"-plugin which
parses a xml-file to find the paths to allow indexes, like

<indexes>
  <index>
    <id>index1</id>
    <path>/data/something/index1</path>
  </index>
  <index>
    <id>index2</id>
    <path>/data/somethingelse</path>
  </index>
</indexes>


Regards,
 Stefan

Ravi Chintakunta wrote:
> See my thread
> 
> http://www.mail-archive.com/nutch-user@lucene.apache.org/msg03014.html
> 
> where I have modified NutchBean to dynamically pickup the indexes that
> have to be searcheed. The web page has checkboxes for each index, and
> thus these indexes can be searched in any combination.
> 
> - Ravi Chintakunta
> 
> 
> 
> On 5/31/06, Andrzej Bialecki <ab...@getopt.org> wrote:
>> sudhendra seshachala wrote:
>> > Yes. That is wha I am trying. But for some reason it is not working..
>> >   Does these fields should be lower case only. ?
>> >
>>
>>
>> Preferably. If you use the default NutchDocumentAnalyzer it will
>> lowercase field names, so you won't get any match.