[
https://issues.apache.org/jira/browse/SOLR-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699403#action_12699403
]
Grant Ingersoll commented on SOLR-773:
--------------------------------------
OK, I think I understand why it does this, but it seems a little odd to me.
The reason is due to the fact that the geo handler uses the geo QParser, which
ignores the query parameter and produces a query solely based on the lat/lon
information.
Like I said, I'm a newbie to geo search, but it seems like the QParser should
delegate the parsing of the q param to some other parser and then it would only
do distance calculations on the docset returned from the QueryComponent. Of
course, I guess one could ask what the semantics are of combining a text query
with a spatial query, but I would suppose we could combine them with either AND
or OR, right, such that if I OR'd them together, I would get all docs matching
the query term OR'd with all docs in the bounding box. Similarily, AND would
yield all docs with the term in the bounding box, right?
Again, I am likely missing something, so bear with me.
> Incorporate Local Lucene/Solr
> -----------------------------
>
> Key: SOLR-773
> URL: https://issues.apache.org/jira/browse/SOLR-773
> Project: Solr
> Issue Type: New Feature
> Reporter: Grant Ingersoll
> Assignee: Grant Ingersoll
> Priority: Minor
> Attachments: lucene.tar.gz, SOLR-773-local-lucene.patch,
> SOLR-773-local-lucene.patch, SOLR-773-local-lucene.patch,
> SOLR-773-local-lucene.patch, SOLR-773-local-lucene.patch, SOLR-773.patch,
> spatial-solr.tar.gz
>
>
> Local Lucene has been donated to the Lucene project. It has some Solr
> components, but we should evaluate how best to incorporate it into Solr.
> See http://lucene.markmail.org/message/orzro22sqdj3wows?q=LocalLucene
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
