[
https://issues.apache.org/jira/browse/SOLR-16717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17711421#comment-17711421
]
Mikhail Khludnev commented on SOLR-16717:
-----------------------------------------
I limit this functionality to default CompositeIdRouter, however PlainIdRouter
will also work. I just need to put parent doc and its children into
corresponding shards eg: parents.shard1 and children.shard1. Now patch checks
that collections joined by the same fields which are used for routing:
||collection:||parents||children||
|router.field:|id|parent_id|
|{!join } params:|to=id|from=parent_id|
However, there might be two other routing approach, which can't be checked in
query time:
* ImplicitRouter with specifying _route_=shardN
* CompositeIdRouter when we actually use composite feature to put children
into certain shards via childDoc: \{id:"${parent_id}!123"}
Thanks to [~dsmiley] for reminding the latter yesterday. Actually, I like this
composite approach more than specifying parent field explicitly.
Question:
# should join parser check router.field (relying on the table above), or
# just check that number of shards are equal (or from side is single shard).
# expect 1. but let user to override restriction to go 2 with local parameter
like \{!join to= from=.. godmode=iddqd} ?
> 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: [email protected]
For additional commands, e-mail: [email protected]