[
https://issues.apache.org/jira/browse/SOLR-12967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677352#comment-16677352
]
Shawn Heisey commented on SOLR-12967:
-------------------------------------
In general, I completely agree that MOVEREPLICA should preserve the replica
type that already exists.
But when I was thinking about the idea where somebody could specify a default
replica type, I wondered if some people might want that to override what things
like MOVEREPLICA do by default. I'm not sure that such an option should be
implemented, but I did think of it.
[~gilson.nascimento] also noticed that UTILIZENODE created NRT replicas. Which
might really be the same problem -- it would be reasonable for UTILIZENODE to
be implemented internally as MOVEREPLICA.
> MOVEREPLICA converting replica to NRT
> -------------------------------------
>
> Key: SOLR-12967
> URL: https://issues.apache.org/jira/browse/SOLR-12967
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 7.5
> Reporter: Gilson
> Priority: Minor
> Labels: collection-api, solr
>
> When calling Collections API's MOVEREPLICA, the new replica created is always
> NRT type, even when the original replica is PULL or TLOG. As discussed on
> IRC, it should use the source replica type, or provide a parameter for the
> user to choose the new replica's type, similar to ADDREPLICA <type> parameter.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
