[ 
https://issues.apache.org/jira/browse/LUCENE-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073148#comment-13073148
 ] 

Uwe Schindler commented on LUCENE-3338:
---------------------------------------

bq. I wondered that too, so I checked. Both AutomatonQuery and TermRangeQuery 
special-case these to generate a simple TermsEnum, so the same. It makes sense 
to optimize: this query could easily be generated by some app.

And for NumericRangeQuery this is even faster, as it will generate a query that 
only enumerates the lowest precision terms (all of them). For e.g. 
precisionStep 4 this would be 16 terms only :-) So no such optimization is 
needed for NRQ.

bq. Uwe, raise your hand if you want me to hold the commit and sorry for taking 
over your JIRA 

It's all fine to combine both commits! I had not looked in 3343 because I 
thought it's for the good old default QP... We should add changes at the end!

> Flexible query parser does not support open ranges and range queries with 
> mixed inclusive and exclusive ranges
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-3338
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3338
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: modules/queryparser
>    Affects Versions: 3.3
>            Reporter: Vinicius Barros
>            Assignee: Uwe Schindler
>             Fix For: 4.0
>
>         Attachments: LUCENE_3338_and_3343_2011_07_30.patch, 
> week9-merged-nosurround.patch, 
> week9-merged-nosurround_with_failing_junit.patch, week9-merged.patch, 
> week9.patch
>
>
> Flexible query parser does not support open ranges and range queries with 
> mixed inclusive and exclusive ranges.
> These two problems were found while developing LUCENE-1768.

--
This message is automatically generated by JIRA.
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]

Reply via email to