[
https://issues.apache.org/jira/browse/SOLR-12967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677299#comment-16677299
]
Erick Erickson commented on SOLR-12967:
---------------------------------------
Shawn:
I would think that the original proposal of "use the source replica's type or
an explicit override" is best for MOVEREPLICA.
For other kinds of operations, <2> is confusing to me. ADDREPLICA already has a
"type" you can specify that defaults to NRT. What other operations do you think
need this? At any rate the general approach of "use NRT unless there's a 'type'
override" seems like the right thing to do.
> 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: [email protected]
For additional commands, e-mail: [email protected]
