[
https://issues.apache.org/jira/browse/SOLR-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025479#comment-13025479
]
Jonathan Rochkind commented on SOLR-2272:
-----------------------------------------
This is a feature that would be very useful to me, thus I've had a watch
on the ticket.
I am not a solr committer and have never even contributed a patch, just
a user. But this is a feature I've been wanting for a while, and would
be excited to see it in Solr. On the one hand I see the argument that
it would ideally go at the lucene layer; on the other hand, if someone
has working, tested, well-written code that is is ready at the Solr
layer, as a user, I'd really like to see it go in there, to be
refactored to lucene at a later date when/if someone else has
time/interest -- rather than delaying working code indefinitely for
hypothetical future (potentially time-consuming) refactoring at a
different layer by yet-to-be-volunteered labor.
I put this in only to make clear that there are users in the general
population who would like to see this feature get into Solr sooner
rather than later, delaying it does matter to 'ordinary' users. (I am
neither a Solr contractor nor a customer of a Solr contracter, I don't
have any such 'business interests', I am just an in-house developer who
writes (open source) software on top of Solr. Not that there's anything
wrong with being a Solr contractor, it's a fine way to fund open source
development and I think it's odd to imply there's something wrong with
it; I'm just saying I'm not one.)
Hopefully you committers can work it out amongst yourself in a way that
balances the codebase's architectural health with the need to get
working code out there.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
