I believe this is caused by the regex support in https://issues.apache.org/jira/browse/LUCENE-2039
It certainly seems wrong to interpret a slash in the middle of the word as the start of a regex, so I've reopened the issue. -Yonik http://lucidworks.com On Thu, Sep 6, 2012 at 9:34 AM, Alexandre Rafalovitch <arafa...@gmail.com> wrote: > Hello, > > I was under the impression that edismax was supposed to be crash proof > and just ignore bad syntax. But I am either misconfiguring it or hit a > weird bug. I basically searched for text containing '/' and got this: > > { > 'responseHeader'=>{ > 'status'=>400, > 'QTime'=>9, > 'params'=>{ > 'qf'=>'TitleEN DescEN', > 'indent'=>'true', > 'wt'=>'ruby', > 'q'=>'foo/bar', > 'defType'=>'edismax'}}, > 'error'=>{ > 'msg'=>'org.apache.lucene.queryparser.classic.ParseException: > Cannot parse \'foo/bar \': Lexical error at line 1, column 9. > Encountered: <EOF> after : "/bar "', > 'code'=>400}} > > Is that normal? If it is, is there a known list of characters I need > to escape or do I just have to catch the exception and tell user to > not do this again? > > Regards, > Alex. > > Personal blog: http://blog.outerthoughts.com/ > LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch > - Time is the quality of nature that keeps events from happening all > at once. Lately, it doesn't seem to be working. (Anonymous - via GTD > book)
