Updating the parameters in the extension's method and rebuilding wasn't
enough to fix the problem for me. Not sure what I'm missing.
It looks like this bug also affects the analysis of the range clause. I
need the terms to be case sensitive so I'm using a per-field analyzer to
make sure that field doesn't get lowercased but it's getting ignored and
sent to the default analyzer.
On 01/03/2014 05:38 PM, Andi Vajda wrote:
On Jan 3, 2014, at 21:35, Shawn Grant <shawn.gr...@orcatec.com> wrote:
whoops, bad link expansion. Was supposed to be:
getRangeQuery(String field, String part1, String part2, boolean startInclusive,
boolean endInclusive);
Yes, that would be the problem. The signature changed but the extension's
didn't.
Andi..
On 01/03/2014 04:33 PM, Shawn Grant wrote:
I have a subclass of PythonQueryParser that overrides several methods but I
can't seem to get it to use getRangeQuery. I noticed that the method
definition in PythonQueryParser is:
getRangeQuery(String field, String part1, String part2, boolean inclusive);
but the lucene definition for QueryParser (in QueryParserBase) is:
|*getRangeQuery
<https://lucene.apache.org/core/4_4_0/queryparser/org/apache/lucene/queryparser/classic/QueryParserBase.html#getRangeQuery%28java.lang.String,%20java.lang.String,%20java.lang.String,%20boolean,%20boolean%29>*(String
<http://download.oracle.com/javase/6/docs/api/java/lang/String.html?is-external=true> field,
String <http://download.oracle.com/javase/6/docs/api/java/lang/String.html?is-external=true>
part1, String
<http://download.oracle.com/javase/6/docs/api/java/lang/String.html?is-external=true> part2,
boolean startInclusive, boolean endInclusive)|
Is that an issue?
