On 05/03/2015 15:53, Paul Taylor wrote:
On 05/03/2015 14:43, Michael McCandless wrote:
It looks like field was null?
Back in 4.1.0 we just assert field != null, but in newer releases it's
a real check.
Mike McCandless
Hi, thankyou Il try and get the query logged for when it next happens
Okay here are two lucene queries that cause the issue
artist:pandora /reyli barba recording:Solo el y yo/Alguien llena mi lugar
artist:Jeremih recording:Rated R (The Masterpiece) (Bear//Face Bootleg Edit)
So I think the problem is that the users are not aware of the regular
expression syntax, escaping or removing the slashes and it works
(Interestingly just removing one of the slashes
artist:pandora /reyli barba recording:Solo el y yo Alguien llena mi lugar
gives me the ParseException instead of the NullPointerException
)
But how can I fix this at my end so that Lucene returns an ParseException
rather than NullPointerException ?
Do you know the earliest verion of Lucene after 4.1.0 to handle this ?
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
