[
https://issues.apache.org/jira/browse/SOLR-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779670#action_12779670
]
Chris A. Mattmann commented on SOLR-1568:
-----------------------------------------
bq. So, in the end, my decision was based on the fact that the code for it was
pretty simple and wouldn't be a big deal to fix. Longer term, I will fix the
issue in trunk of Lucene and then over time Solr can adapt to use that once we
are on 3.x
+1 on this. My group at JPL has gone the route of trying to co-develop Lucene
and SOLR patches for this without much success. I think the best way is to
maintain the code pieces in SOLR, try and flow them back into Lucene (those
updates needed there), and then flow back into SOLR as releases in Lucene-ville
are made.
> Implement Cartesian Tier Filter
> -------------------------------
>
> Key: SOLR-1568
> URL: https://issues.apache.org/jira/browse/SOLR-1568
> Project: Solr
> Issue Type: New Feature
> Reporter: Grant Ingersoll
> Assignee: Grant Ingersoll
> Priority: Minor
> Fix For: 1.5
>
> Attachments: CartesianTierQParserPlugin.java
>
>
> Given an index with cartesian tiers, we should be able to pass in a filter
> query that takes in the field name, lat, lon and radius and produces an
> appropriate Filter for use by Solr. Note, contrib/spatial has such a filter,
> so it may just be that we need to hook in a QParserPlugin to handle it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
