lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "G.Long" <jde...@gmail.com>
Subject Re: query performance with leading *
Date Mon, 13 Feb 2012 17:06:13 GMT
Thank you for the tips,

Is there an analyzer which uses this tokenizer? If not, do you know any 
tutorial which explain how to implement a custom analyzer? I didn't find 
any.

Regards.

Le 13/02/2012 17:46, Robert Muir a écrit :
> I think you can solve this with the tokenizers in the
> org.apache.lucene.analysis.path package (in lucene-analyzers.jar)
>
> In your case, looks like ReversePathHierarchyTokenizer might be what
> you want, though you will need to upgrade to at least 3.2 to get it.
>
> On Mon, Feb 13, 2012 at 11:38 AM, G.Long<jdevgl@gmail.com>  wrote:
>> Hi,
>>
>> Is there a way to improve query performance when using a leading * as a
>> wildcard on a path property?
>>
>> I have hundreds of queries to run on a lucene index (~250mo). Executing
>> those queries without the leading * is about 5x faster than with the leading
>> *. My problem is that I sometimes need to use the leading *.
>>
>> Most of the queries have the full path as parameter but some of them have
>> only a part of it.
>>
>> The queries look like:
>> "+projet:CCOM +path:*/folder5/folder6/folder_ab/
>>
>> I'm using lucene 3.1.0
>>
>> Regards,
>> Gary
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: java-user-help@lucene.apache.org
>>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org


Mime
View raw message