On 06/03/2015 17:34, Michael McCandless wrote:
On Fri, Mar 6, 2015 at 11:03 AM, Paul Taylor <paul_t...@fastmail.fm> wrote:
Right, did you see my last post the query parser does trap the exception if
you enable assertions. I thought this was what you were saying was fixed in
a later version, but assume you actually mean search is fixed not parser
Well it's both: Lucene should catch illegal null to all its Query
classes, and Robert opened
https://issues.apache.org/jira/browse/LUCENE-6345 for that.
And then no query parser should ever send an invalid null down to
Lucene queries ... that's the bug/test I think you should open?
Ok Ive done it with test case , I think at least the starting issue is
specific to MultiFieldQueryParser
https://issues.apache.org/jira/browse/LUCENE-6347
Is SimpleQueryParser identical to ClassicQueryParser without regular
expressions, or not ?
It's completely different. It's goals are to support only the common
reasonable-performing queries and do it's best-effort to make a query
even on invalid input (not throw a ParseException).
Right I cant change the query syntax of a live system, although a way to
disable just regualr expressions would be good as we dont officiallly
support that.
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
