[
https://issues.apache.org/jira/browse/SOLR-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971070#action_12971070
]
Yonik Seeley commented on SOLR-2272:
------------------------------------
bq. Yonik, that feature is pretty interesting, but sounds more like a mapping
or replacement than a join to me...
Yeah, I agree.. it's closer to a semi-join
http://en.wikipedia.org/wiki/Hash_join#Hash_semi-join
I experimented with calling it pivot or map, but I think this type of semantic
is realistically the closest we'll get to a join.
bq. Unfortunatelly, I thought I'd be able to perform search restrictions on the
union produced by the join, but I wasn't able to do so
This is mapping from one id space to another, so you need to filter in the
appropriate space.
You're doing a self-join here, so it's a more complex example to figure out.
What about something like:
q={!join from=pivot to=pivot}price:[* TO 200]&fq=title:great
?
> Join
> ----
>
> Key: SOLR-2272
> URL: https://issues.apache.org/jira/browse/SOLR-2272
> Project: Solr
> Issue Type: New Feature
> Reporter: Yonik Seeley
> Fix For: 4.0
>
> Attachments: 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
