[
https://issues.apache.org/jira/browse/SOLR-7090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15684139#comment-15684139
]
Kevin Risden commented on SOLR-7090:
------------------------------------
Not 100% sure on this, but my guess is that [~irphilli] was using just a
regular /select search in the streaming expression. There is nothing stopping
that from a streaming expressions point of view. As you pointed out, using
qt=/export and then docValues will help a lot. The simple /select search may
just do regular paging (not sure it uses cursor marks?).
Some items to check:
* was search() being used against normal /select without qt=/export
* search() - does it use cursormark instead of regular paging?
> Cross collection join
> ---------------------
>
> Key: SOLR-7090
> URL: https://issues.apache.org/jira/browse/SOLR-7090
> Project: Solr
> Issue Type: New Feature
> Reporter: Ishan Chattopadhyaya
> Fix For: 5.2, 6.0
>
> Attachments: SOLR-7090-fulljoin.patch, SOLR-7090.patch
>
>
> Although SOLR-4905 supports joins across collections in Cloud mode, there are
> limitations, (i) the secondary collection must be replicated at each node
> where the primary collection has a replica, (ii) the secondary collection
> must be singly sharded.
> This issue explores ideas/possibilities of cross collection joins, even
> across nodes. This will be helpful for users who wish to maintain boosts or
> signals in a secondary, more frequently updated collection, and perform query
> time join of these boosts/signals with results from the primary collection.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
