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
e
>> of queries?
>>
>> I'd only be comfortable with choosing an approach if I tried
>> it out with a single computer's content and generated a few
>> stats
>>
>> Best
>> Erick
>>
>> - Original Message
>>
>>> From:
<[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Tuesday, September 16, 2008 10:55:09 AM
Subject: Using separate index for each user
Hi,
We're thinking of using Lucene to integrate search in a backup
service
application. The background is that we have a bunch of users using a
age
> From: Tobias Larsson Hult <[EMAIL PROTECTED]>
> To: java-user@lucene.apache.org
> Sent: Tuesday, September 16, 2008 10:55:09 AM
> Subject: Using separate index for each user
>
> Hi,
>
> We're thinking of using Lucene to integrate search in a backup service
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
Hi,
We're thinking of using Lucene to integrate search in a backup service
application. The background is that we have a bunch of users using a
backup service, and we want them to be able to search their own, and
only their own, backups.
The total amount of data that's being backed up is
