and I've never had to
> find any other jars from the Lucene site, they've all
> been in contrib
>
> Hope this helps
> Erick
>
> On 8/16/07, dontspamterry <[EMAIL PROTECTED]> wrote:
>>
>>
>> Hi,
>>
>> While researching support f
Hi,
While researching support for wildcards in a PhraseQuery, I see various
references to SpanRegexQuery which is not part of the 2.2 distribution. I
checked the Lucene site to see if it's some add-on jar, but couldn't find
anything so I'm wondering where can I obtain the .class/jar file(s) for t
Here you go:
import junit.framework.TestCase;
import org.apache.lucene.analysis.WhitespaceAnalyzer;
import org.apache.lucene.queryParser.QueryParser;
import org.apache.lucene.search.PrefixQuery;
import org.apache.lucene.search.Query;
import org.apache.lucene.search.WildcardQuery;
public class W
I'm using 2.1.0 and I'm calling setAllowLeadingWildcard(true) first on my
QueryParser instance. I'm using a PerFieldAnalyzerWrapper where the field of
interest uses the WhiteSpaceAnalyzer.
-Terry
hossman_lucene wrote:
>
>
> : gets parsed to the PrefixQuery *abc. I did enable the leading wildc
Hi all,
I was experimenting with queries using wildcard on an untokenized field and
noticed that a query with both a starting and trailing wildcard, e.g. *abc*,
gets parsed to the PrefixQuery *abc. I did enable the leading wildcard in
the QueryParser to allow the query above to be parsed so I'm w
eed.
>
> Otis
> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
> Simpy -- http://www.simpy.com/ - Tag - Search - Share
>
> - Original Message
> From: dontspamterry <[EMAIL PROTECTED]>
> To: java-user@lucene.apache.org
> Sent: Thursday, May 24, 2007 1:20:11 PM
> Subject: KeywordAn
Hi all,
I have an ID field which I index using the KeywordAnalyzer. Since this
analyzer tokenizes the entire stream as a single token, would you say the
end result is the same as using any analyzer and specifying this ID field as
untokenized? The latter approach does not use the analyzer so would
Hi all,
I know this whole distinct query has been discussed a bunch of times for
various scenarios because I've been scouring the forums trying to find a
clue as to how I could solve my problem. I'm indexing a large set of
parent-child term relations (~1 million). The number of unique terms is
ab
