[
https://issues.apache.org/jira/browse/SOLR-7090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15678251#comment-15678251
]
Erick Erickson commented on SOLR-7090:
--------------------------------------
Phil:
Streaming should definitely _not_ require that the fields be stored. If you use
qt=/export it should throw an error if they're not docValues. They must be
docValues=true fields though.
And you'd have to be sure and index from scratch with the fields set with
docValues. IIUC if this is really a requirement, then it's a bug in streaming
so could you double check the field definitions? If stored=true is required,
we'll want to know b/c it sounds at this remove like a bug.
> 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]
