: And as I understand it, current behavior is the silent misinterpretation. : To me, the failure to require a space after the regex (and either not : become a regex in that case or complain about invalid regex) might be : considered a bug...
I would agree ... : >> However, today people can search for : : >> /foo.com/index.html : >> and not get an error. The searcher may think this is a query for a URL : >> but it's actually parsed as a regex "foo.com" ORed with a term query. ... i didn't realize that was happening. To me that seems like it should definitely be considered a bug, and the "regex" branch of the grammer shouldn't be used if there is any unexpected characters after the closing "/" ... the current behavior Mark is describgin seems analogous to the grammer assuming "WESS ANDERSON" should be parsed as "WESS +DERSON" : > You could avoid (some of?) these problems by supporting /(?i)foo/ : > instead of /foo/i : : I like this idea. The only downside is that folks will tend to think : it's a full Java Pattern and try other options. :) If they try to use any other options then 'i' we throow a ParseException -Hoss http://www.lucidworks.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
