[
https://issues.apache.org/jira/browse/SOLR-16717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17717933#comment-17717933
]
Mikhail Khludnev commented on SOLR-16717:
-----------------------------------------
Pushed the following changes. Now it supports the following modes:
# both collections has router=Implicit. Hand off integrity check to the user
# both collections has router=PlainId mandatory check: from/toField should be
either uniqueKey or router.field. No way to disable this constraint.
# both collections has router=CompositeId - same as above, but there's the
next option
# both collections has router=CompositeId and checkRouterField=false is
provided in local param. There's no check in this case. It assumes that one of
the sides has composite ids assigned as: id=<FK>!<PK> that allows to collocate
docs with the same join filed values.
Number of shards should be equals on both sides always.
> Join collocated shards
> ----------------------
>
> Key: SOLR-16717
> URL: https://issues.apache.org/jira/browse/SOLR-16717
> Project: Solr
> Issue Type: Improvement
> Reporter: Mikhail Khludnev
> Priority: Major
>
> h3. Context
> It's about \{!join} query parser and distributed mode.
> h3. As is
> SOLR-4905 allows to join from single shard collection to many shards
> collection.
> h3. Challenge
> * Support multiple shards on from side as well,
> * but strictly stick to collocated indices that promise much performance.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
