[
https://issues.apache.org/jira/browse/SOLR-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025573#comment-13025573
]
Robert Muir commented on SOLR-2272:
-----------------------------------
Its the same argument we have here, all over again. If we could actually freely
refactor stuff from solr into lucene (e.g. spatial search functionality, which
seems like some lucene users MIGHT just want), then it really doesn't matter
where it goes.
Sure its "ideal" if the patch puts the core functionality in lucene and the
solr bits in solr, but it would still be "great" even if the patch starts
totally solr, and there is at least the hope in the future of refactoring (if
someone is willing to do the work).
> Join
> ----
>
> Key: SOLR-2272
> URL: https://issues.apache.org/jira/browse/SOLR-2272
> Project: Solr
> Issue Type: New Feature
> Components: search
> Reporter: Yonik Seeley
> Fix For: 4.0
>
> Attachments: SOLR-2272.patch, SOLR-2272.patch, SOLR-2272.patch
>
>
> Limited join functionality for Solr, mapping one set of IDs matching a query
> to another set of IDs, based on the indexed tokens of the fields.
> Example:
> fq={!join from=parent_ptr to:parent_id}child_doc:query
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
