Hi Brandon,
Can you start by calling toString on the parse result (the Query object) to
see what is being produced and post that here.
On the face of it it sounds like it should work OK. What happens if you use
the "normal" query parser on your query "time to leave" - that should parse ok
as
We are still having the issue where ComplexPhraseQueryParser fails on
quoted expressions that include stop words. Does the original
developer of this class still contribute to Lucene?
On Fri, Oct 26, 2012 at 3:37 PM, Brandon Mintern wrote:
> We recently switched from QueryParser to ComplexPhraseQ
We recently switched from QueryParser to ComplexPhraseQueryParser
(from lucene-queryparser-3.6.0.jar), and we've come across two
separate problems.
The first is that because it parses quoted expressions twice, it is
necessary to double-escape any escaped characters. So if I do not want
to allow us
