[ http://issues.apache.org/jira/browse/LUCENE-682?page=all ]
Hoss Man updated LUCENE-682:
----------------------------
Attachment: LocalizedQueryParserOperatorsMicroBench.java
microbenchmark of the "default" (no ResourceBundle) usage, run against the
current trunk, and with this change (to determine the performance costs of the
added work in the Javacc generated code)
two tests, one of a new instance for each parse call, one of reusing the same
instance for 5 parse calls; 3 runs each, 10000 iterations each, time in
seconds...
1 1 1 5 5 5
trunk: 1.897 1.904 1.913 7.415 7.447 7.446
w/patch: 2.01 2.005 2.01 7.851 7.888 7.886
...doesn't seem like a big enough factor to worry about (unless i missed
something obvious when i wrote the test ... i was on a plane at the time and
slightly distracted by the very chatty woman next to me)
> 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]
