[
https://issues.apache.org/jira/browse/SOLR-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976992#comment-14976992
]
Mikhail Khludnev commented on SOLR-4905:
----------------------------------------
[~thelabdude], I want to got further, but not too far..
[~joel.bernstein] wrote in
https://lucidworks.com/blog/2013/06/13/solr-cloud-document-routing/
bq. Certain Solr features such as grouping’s ngroups feature and _*joins*_
require documents to be co-located in the same core or vm.
Is it worth to raise a jira to allow q-time join for collection with shards
collocated via {{compositeId}} or {{implicit}} router with {{router.field}}?
Concerns and suggestions are welcome!
> Allow fromIndex parameter to JoinQParserPlugin to refer to a single-sharded
> collection that has a replica on all nodes
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-4905
> URL: https://issues.apache.org/jira/browse/SOLR-4905
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Philip K. Warren
> Assignee: Timothy Potter
> Fix For: 5.1, Trunk
>
> Attachments: SOLR-4905.patch, SOLR-4905.patch, patch.txt
>
>
> Using a non-SolrCloud setup, it is possible to perform cross core joins
> (http://wiki.apache.org/solr/Join). When testing with SolrCloud, however,
> neither the collection name, alias name (we have created aliases to SolrCloud
> collections), or the automatically generated core name (i.e.
> <collection>_shard1_replica1) work as the fromIndex parameter for a
> cross-core join.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
