@lucene.apache.org
Subject: Re: thoughts/suggestions for analyzing/tokenizing class names
Either index them as a series of tokens:
org
org.apache
org.apache.lucene
org.apache.lucene.document
org.apache.lucene.document.Document
or index them as a single token, and use prefix queries (this is what
I do for reverse
Message-
> From: Mike Klaas [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 17, 2007 11:29 AM
> To: java-user@lucene.apache.org
> Subject: Re: thoughts/suggestions for analyzing/tokenizing class names
>
> On 15-Dec-07, at 3:14 PM, Beyer,Nathan wrote:
>
>> I h
day, December 17, 2007 11:29 AM
To: java-user@lucene.apache.org
Subject: Re: thoughts/suggestions for analyzing/tokenizing class names
On 15-Dec-07, at 3:14 PM, Beyer,Nathan wrote:
I have a few fields that use package names and class names and I've
been
looking for
ucene", "document"
-Nathan
-Original Message-
From: Mike Klaas [mailto:[EMAIL PROTECTED]
Sent: Monday, December 17, 2007 11:29 AM
To: java-user@lucene.apache.org
Subject: Re: thoughts/suggestions for analyzing/tokenizing class names
On 15-Dec-07, at 3:14 PM, Beyer,Nathan wro
On 15-Dec-07, at 3:14 PM, Beyer,Nathan wrote:
I have a few fields that use package names and class names and I've
been
looking for some suggestions for analyzing these fields.
A few examples -
Text (class name)
- "org.apache.lucene.document.Document"
Queries that would match
- "org.apache" ,
I have a few fields that use package names and class names and I've been
looking for some suggestions for analyzing these fields.
A few examples -
Text (class name)
- "org.apache.lucene.document.Document"
Queries that would match
- "org.apache" , "org.apache.lucene.document"
Text (class name +
