[ http://issues.apache.org/jira/browse/LUCENE-682?page=comments#action_12456258 ] Yonik Seeley commented on LUCENE-682: -------------------------------------
Frankly, I'm not excited about a 6% performance loss so that someone can customize a total of 3 tokens that don't add additional expressive power or features. AND, OR, and NOT, are short and easy to understand even for foreign-language speakers. Consider that to construct raw Lucene queries themselves, they would need to know Lucene, and for that, they will most likely have a passing familiarity with English anyway. I think this would be better implemented as a preprocessor, outside of the query parser. I don't think that would be too hard, and then there would be no performance impact for the 99% of people who will stick with AND/OR/NOT (or +/-) It might even be expressible as a regular expression. Maybe it's just me though, so I wouldn't mind hearing some other opinions. > QueryParser with Locale Based Operators (French included) > --------------------------------------------------------- > > Key: LUCENE-682 > URL: http://issues.apache.org/jira/browse/LUCENE-682 > Project: Lucene - Java > Issue Type: New Feature > Components: QueryParser > Reporter: Patrick Turcotte > Assigned To: Hoss Man > Priority: Minor > Attachments: LocalizedQueryParser.patch, LocalizedQueryParser.patch, > LocalizedQueryParser.zip, LocalizedQueryParserDemo.java, > LocalizedQueryParserOperatorsMicroBench.java, QueryParser.jj, > QueryParser.jj.patch, QueryParser.properties, QueryParser_fr.properties, > TestQueryParserLocaleOperators.java > > > Here is a version of the QueryParser that can "understand" the AND, OR and > NOT keyword in other languages. > If activated, > - "a ET b" should return the same query as "a AND b", namely: "+a +b" > - "a OU b" should return the same query as "a OR b", namely: "a b" > - "a SAUF b" should return the same query as "a NOT b", namely: "a -b" > Here are its main points : > 1) Patched from revision 454774 of lucene 2.1dev (trunk) (probably could be > used with other versions) > 2) The "ant test" target is still successful when the modified QueryParser is > used > 3) It doesn't break actual code > 4) The default behavior is the same as before > 5) It has to be deliberately activated > 6) It use ResourceBundle to find the keywords translation > 7) Comes with FRENCH translation > 8) Comes with JUnit testCases > 9) Adds 1 public method to QueryParser > 10) Expands the TOKEN <TERM> > 11) Use TOKEN_MGR_DECLS to set some field for the TokenManager -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
