alyzer 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 wrote:
whoops, bad link expansion. Was supposed to be:
getRangeQuery(String field, Strin
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 g
I don't see that pylucene has a wrapper for the
ComplexPhraseQueryParser... am I wrong? Is there any particular
difficulty to making that available?
release along.
On 11/13/2012 02:18 PM, Andi Vajda wrote:
Hi Shawn,
On Tue, 13 Nov 2012, Shawn Grant wrote:
Hi Andi, I was just wondering if Pylucene is on its usual schedule to
release 4-6 weeks after Lucene. I didn't see any discussion of it on
the mailing list or elsewhere. I'm
