Hi Paul,
In 2.9, you can use the "new query parser" in contrib.
You should look at:
original.config.FieldBoostMapAttribute
original.config.FieldBoostMapFCListener
original.processors.BoostQueryNodeProcessor
original.builders.BoostQueryNodeBuilder
this code implements boost
Uwe Schindler wrote:
Actually what I ideally want I really want is for lucene to realise that
when a particular field is being searched (in this case qdur) it should
convert the values to allow the range to work properly, i.e by flagging
a field as being numeric when you create the index.
> Actually what I ideally want I really want is for lucene to realise that
> when a particular field is being searched (in this case qdur) it should
> convert the values to allow the range to work properly, i.e by flagging
> a field as being numeric when you create the index.
It is simple:
Subclas
:mille...@gmail.com]
> Sent: Wednesday, July 29, 2009 2:33 PM
> To: java-user@lucene.apache.org; paul_t...@fastmail.fm
> Subject: RE: How do you Parse a query to convert numbers to strings
>
> It is explained in the book Lucene in Action.
> So you just need to do some pad
MilleBii wrote:
It is explained in the book Lucene in Action.
So you just need to do some padding on numbers and do a rangeQuery... Lucene implements a lexicographic comparison
Thanks but that doesn't really address the issue.
A user send a lucene query, I then just use QueryParser.parse()
It is explained in the book Lucene in Action.
So you just need to do some padding on numbers and do a rangeQuery... Lucene
implements a lexicographic comparison
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
F
Paul Taylor wrote:
I think this is a common problem, but don't know the correct solution.
Users were doing queries on a numeric field such as qdur:[73 TO 117]
and expecting to find all the values within but this fails because
lucene treats the numbers as strings and just does alphabetical
sea
