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
> On Jan 3, 2014, at 21:35, Shawn Grant 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.
And
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 QueryP
whoops, bad link expansion. Was supposed to be:
getRangeQuery(String field, String part1, String part2, boolean
startInclusive, boolean endInclusive);
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
