ose();
}
}
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-----
> From: Uwe Schindler [mailto:u...@thetaphi.de]
> Sent: Monday, October 12, 2009 8:10 PM
> To: java-user@lucene.apach
hetaphi.de]
> Sent: Monday, October 12, 2009 5:49 PM
> To: java-user@lucene.apache.org; paul_t...@fastmail.fm
> Subject: RE: How do you properly use NumericField
>
> Can you print the upper and lower term or the term you received in
> newRangeQuery and newTermQuery also to System.
Uwe Schindler wrote:
Can you print the upper and lower term or the term you received in
newRangeQuery and newTermQuery also to System.out? Maybe it is converted
somehow by your Analyzer, that is used for parsing the query.
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.theta
...@thetaphi.de
> -Original Message-
> From: Paul Taylor [mailto:paul_t...@fastmail.fm]
> Sent: Monday, October 12, 2009 1:00 PM
> To: java-user@lucene.apache.org
> Subject: Re: How do you properly use NumericField
>
> Uwe Schindler wrote:
> > I forgot: The format of
Uwe Schindler wrote:
I forgot: The format of numeric fields is also not plain text, because of
this a simple TermQuery as generated by your query parser will not work,
too.
If you want to hit numeric values without a NumericRangeQuery with lower and
upper bound equal, you have to use NumericUtil
Uwe Schindler wrote:
As we told you before. The default QueryParser has no support fro
NumericField (as it doesn't know the schema). To get it running, subclass it
and overwrite newRangeQuery method to create a NumericRangeQuery for field
names that are indexed using NumericField.
Hi, yes I di
ul Taylor [mailto:paul_t...@fastmail.fm]
> > Sent: Sunday, October 11, 2009 7:58 PM
> > Cc: Michael McCandless; Lucene Users
> > Subject: Re: How do you properly use NumericField
> >
> > Michael McCandless wrote:
> > > On the indexing side you do this:
>
nding QueryParser.
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Paul Taylor [mailto:paul_t...@fastmail.fm]
> Sent: Sunday, October 11, 2009 7:58 PM
> Cc: Michael McCandless; Lucene Users
> Sub
Michael McCandless wrote:
On the indexing side you do this:
doc.add(new NumericField("price").setDoubleValue(19.99));
The NumericField is not stored by default (there's also a ctor to
specify Store.YES or Store.NO).
If the numeric field is not being used in a range query, how is it
being u
Michael McCandless wrote:
On Fri, Oct 9, 2009 at 3:26 PM, Paul Taylor wrote
It still relies on super.getRangeQuery() for non-numeric fields. If
you don't have non-numeric fields that accept range queries you can
simply call NumericRangeQuery.newXXXRange directly.
For some indexes I hav
Michael McCandless wrote:
On Fri, Oct 9, 2009 at 3:26 PM, Paul Taylor wrote:
I currently use NumberTools.longToString() to add integer fields to
an index and allow range searching, then when searching I then
preprocess the query (using regular expressions) and convert integer
fields to Numb
fm
> Subject: Re: How do you properly use NumericField
>
> On Fri, Oct 9, 2009 at 3:26 PM, Paul Taylor wrote:
>
> > I currently use NumberTools.longToString() to add integer fields to
> > an index and allow range searching, then when searching I then
> > preprocess
On Fri, Oct 9, 2009 at 3:26 PM, Paul Taylor wrote:
> I currently use NumberTools.longToString() to add integer fields to
> an index and allow range searching, then when searching I then
> preprocess the query (using regular expressions) and convert integer
> fields to NumberTools.longToString bef
Hi
I currently use NumberTools.longToString() to add integer fields to an
index and allow range searching, then when searching I then preprocess
the query (using regular expressions) and convert integer fields to
NumberTools.longToString before it is parsed by the QueryParser, then
when I re
14 matches
Mail list logo
