[
https://issues.apache.org/jira/browse/SOLR-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779662#action_12779662
]
Grant Ingersoll commented on SOLR-1568:
---------------------------------------
Honestly, it's a bit tricky and I'm not sure how best to resolve it (keep in
mind that I'm not recommending the above piece be committed). There are a few
pieces that can be improved in the CartesianShapeFilter to perform better (I
still need to fix them in Lucene) but if I go that route, then I need to update
the Lucene JARs associated with that in Solr. I can't really do that, b/c that
likely means one of two things:
1. Patching the 2.9.1 branch and packaging up that JAR for Solr or wait for a
2.9.2 release from Lucene which isn't likely.
2. Patching trunk and including it. This would be a huge undertaking for Solr
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
> 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.
