We have several versions of lucene running on different systems. It could be
that we didn't notice the problem in 4.1 and it was 3.3 where it seemed to work.
At any rate, I escaped the slash and now all of the unit tests run. Should
have thought to try that myself. Thanks for the help.
Scott
Yeah, just go ahead and escape the slash, either with a backslash or by
enclosing the whole term in quotes. Otherwise the slash (even embedded in
the middle of a term!) indicates the start of a regex query term.
-- Jack Krupansky
-Original Message-
From: Scott Smith
Sent: Sunday, May
Just a thought - this looks like it could be due to the regexp (/pattern/
syntax) support added, but that was added in Lucene 4.0 so it doesn't quite fit
that it would be a difference between 4.1 and 4.2.1.
Erik
On May 19, 2013, at 14:50 , Scott Smith wrote:
> I just upgraded from lu
I just upgraded from lucene 4.1 to 4.2.1. We believe we are seeing some
different behavior.
I'm using org.apache.lucene.queryparser.classic.QueryParser. If I pass the
string "20110920/EXPIRED" (w/o quotes) to the parser, I get:
org.apache.lucene.queryparser.classic.ParseException: Cannot pars
