[
https://issues.apache.org/jira/browse/SOLR-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16439935#comment-16439935
]
Shalin Shekhar Mangar commented on SOLR-11990:
----------------------------------------------
First cut of the feature. It only supports `withCollection` for collections
with a single shard because we do not have access to the other clauses
(specifically the collection and shard values) at the time of the Operand.match
operation. There is still a lot of work and tests left:
# Collection APIs need to be fixed to pre-create `withCollection` replicas
before replicas of `collection` can be created.
# Delete `withCollection` replicas if `collection` replicas are moved or deleted
> Make it possible to co-locate replicas of multiple collections together in a
> node using policy
> ----------------------------------------------------------------------------------------------
>
> Key: SOLR-11990
> URL: https://issues.apache.org/jira/browse/SOLR-11990
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: AutoScaling, SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: SOLR-11990.patch
>
>
> It is necessary to co-locate replicas of different collection together in a
> node when cross-collection joins are performed. The policy rules framework
> should support this use-case.
> Example: Co-locate exactly 1 replica of collection A in each node where a
> replica of collection B is present.
> {code}
> {"replica":1, "collection":"A", "shard":"#EACH", "withCollection":"B"}
> {code}
> This requires changing create collection, create shard and add replica APIs
> as well because we want a replica of collection A to be created first before
> a replica of collection B is created so that join queries etc are always
> possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
