Mailing-List: contact lucene-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lucene Users List" <lucene-user@jakarta.apache.org>
Message-ID: <3ED4C8C4.4030606@syr.edu>
Date: Wed, 28 May 2003 10:33:40 -0400
From: Steve Rowe <sarowe@syr.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.0.2) Gecko/20021120 Netscape/7.01
MIME-Version: 1.0
To: Lucene Users List <lucene-user@jakarta.apache.org>
Subject: Re: Wildcard workaround
References: <336674949053D511BF4D00A0C9B3D3649EAF0D@SONIA>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Andrei,

If this sort of thing is important enough, you could implement a 
customized analyzer which would reverse all terms and store them in a 
separate field (in addition to the a non-reversed field).  This will 
double your index size, of course.

Then, when searching, suffix query terms (those beginning with '*') 
could be reversed and wildcard-searched on the reverse-term field.

Hope it helps,
Steve Rowe

Andrei Melis wrote:
> Hello all,
>  
> As far as I have understood, lucene does not allow search queries starting
> with wildcards.
> I have a file database indexed by content and also by filename. It would be
> nice if the user could perform a usual search like "*.ext".
>  
> Anybody tried a workaround for this issue ? ( this is needed only for the
> name of the file, for the rest of the terms the rules are fine with me)
>  
> I assume that this will produce a decrease of search speed... is this
> correct ?
>  
>  
> 10q,
> Andrei
> 


-- 
Steve Rowe
Software Engineer
Center for Natural Language Processing
School of Information Studies
Syracuse University
www.cnlp.org


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