lucene-lucene-net-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Digy" <digyd...@gmail.com>
Subject RE: Designing an index with constant speed no matter how big
Date Sun, 03 May 2009 10:27:28 GMT
Can it be related with your code? Since Lucene.Net can handle very large
indeces easily. 
Have you tried the search speed improvement techniques in
http://wiki.apache.org/jakarta-lucene/ImproveSearchingSpeed


> My current implementation is to have a property OwnerId in each document
and use it as a clause in the searches. Eg: OwnerId:123 AND
MailContent:Something
> However, this doesn't work...

I don't understand why this didn't work.

DIGY

-----Original Message-----
From: Pierre Henri Kuaté [mailto:phkuate@yahoo.fr] 
Sent: Saturday, May 02, 2009 11:02 PM
To: lucene-net-user@incubator.apache.org
Subject: Designing an index with constant speed no matter how big

Hi,

I am working on a project where full-text search gets slower as the number
of (group of) documents increases.

Here is a simplified description of the project: It is an email system, so
each user has its emails and can search for them using Lucene.net.
So logically, it should be possible to implement it so that its performance
doesn't (really) drop as the number of users increases. The speed of a
search should be based on the amount of documents that the logged user has.

My current implementation is to have a property OwnerId in each document and
use it as a clause in the searches. Eg: OwnerId:123 AND
MailContent:Something
However, this doesn't work...

The extreme solution would be to completely dissociate each user's index.
But that would make my implementation harder to maintain.

Do you have any suggestions?

Pierre Henri.



      


Mime
View raw message