TED]
> Sent: den 19 september 2008 13:43
> To: java-user@lucene.apache.org
> Subject: Re: Using separate index for each user
>
> IF you create a field in the index which would hold username
> then you can
> create search queries to reject entries which don;t belong to
> the
IF you create a field in the index which would hold username then you can
create search queries to reject entries which don;t belong to the user?
it's much efficient
Alexander
2008/9/16 Tobias Larsson Hult <[EMAIL PROTECTED]>
> Hi,
>
> We're thinking of using Lucene to integrate search in a b
uuu, take anything Otis says as *much* more informed than anything I say
on this topic .
Erick
On Thu, Sep 18, 2008 at 2:32 AM, Tobias Larsson Hult <
[EMAIL PROTECTED]> wrote:
> Thanks for the quick responses!
>
> Good point about the warmup issues Erick, that's something we will
> consider.
Thanks for the quick responses!
Good point about the warmup issues Erick, that's something we will
consider. Good to know that this kind of setup has been proved working
for at least one :) I think we will do a small setup and test the
performance.
Thanks again for valuable input!
Best R
Tobias,
That's the approach I took with Simpy.com and it's been working well for
several years now. You'll have to keep track of searchers and close them when
appropriate, of course.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
> From: Tobias
The main arguments against using many separate indexes are
1> search warmup time. That is, each time you open an index
the first few queries take much longer than subsequent searches.
2> Managing a bazillion indexes is non-trivial.
That said, in your particular case these may not apply. I gu
