[
https://issues.apache.org/jira/browse/LUCENE-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Schurman updated LUCENE-996:
-----------------------------------
Attachment: lucene-996.patch
Your absolutely right, I had a problem with the Solr src extending this method.
I don't think there is a nice way to cover all the bases here, but I've updated
the code help alleviate the problem.
I believe the only thing that isn't covered is parsing foo:{a TO bat] with
useOldRangeQueries=false. Classes that extend will still get a query back, but
it might not be what they expect.
> Parsing mixed inclusive/exclusive range queries
> -----------------------------------------------
>
> Key: LUCENE-996
> URL: https://issues.apache.org/jira/browse/LUCENE-996
> Project: Lucene - Java
> Issue Type: Improvement
> Components: QueryParser
> Affects Versions: 2.2
> Reporter: Andrew Schurman
> Priority: Minor
> Attachments: lucene-996.patch, lucene-996.patch
>
>
> The current query parser doesn't handle parsing a range query (i.e.
> ConstantScoreRangeQuery) with mixed inclusive/exclusive bounds.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
