If Solr/Lucene dev were merged, and queryParser is it's own module, this user could simply upgrade his queryParser JAR to get this fix.
Mike ---------- Forwarded message ---------- From: Alexander S (JIRA) <j...@apache.org> Date: Thu, Mar 4, 2010 at 2:24 AM Subject: (SOLR-355) Parsing mixed inclusive/exclusive range queries To: solr-...@lucene.apache.org [ https://issues.apache.org/jira/browse/SOLR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841105#action_12841105 ] Alexander S commented on SOLR-355: ---------------------------------- It is fixed in Lucene, can we get it to SOLR? > Parsing mixed inclusive/exclusive range queries > ----------------------------------------------- > > Key: SOLR-355 > URL: https://issues.apache.org/jira/browse/SOLR-355 > Project: Solr > Issue Type: Improvement > Components: search > Affects Versions: 1.2 > Reporter: Andrew Schurman > Priority: Minor > Attachments: solr-355.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-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
