You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2008/11/13 03:23:44 UTC
[jira] Updated: (LUCENE-996) Parsing mixed inclusive/exclusive
range queries
[ https://issues.apache.org/jira/browse/LUCENE-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller updated LUCENE-996:
-------------------------------
Attachment: LUCENE-996.patch
Bit of a pain catching everything that was slightly off, but I think we want this, especially since RangeQuery accepts separate start/end point inclusive/exclusive now.
Patch brings everything up to trunk, but definitely still needs a strong look over. I'll come back to it in a few days.
> 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
> Fix For: 2.9
>
> Attachments: LUCENE-996.patch, 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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org