: Does anyone know what is the likely performance impact is when *not* : using this feature? It's not easy for me to tell at a glance.
Assuming we get rid of the createLocalizedTokenMap call in setLocale, it should be relatively minor: one extra boolean test of useLocalizedOperators on each TERM parsed. ... except ... hmmmm.... There is something else going on. As a result of the patch, JavaCC seems to have decided that the generated source for QueryParserTokenManager needs to maintain a "StringBuffer image" that gets continuously appended to, but never seems to be used by anything. Manually removing the autogenerated declaration and refrences to that StringBuffer doesn't seem to adversely affect anything ... but i have no idea why JavaCC decided to put it there. Any JavaCC guru's out there understand what it's doing? : : > 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.zip, LocalizedQueryParserDemo.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] : -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
