[
https://issues.apache.org/jira/browse/SOLR-12967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677188#comment-16677188
]
Shawn Heisey commented on SOLR-12967:
-------------------------------------
I advised Gilson to open this issue in the #solr channel.
Do we need separate issues for work on other Collections API actions that don't
consider the replica type, or will we just expand this issue to cover checking
the whole API?
I had a thought for a feature request -- add a couple of new settings: 1) a
default replica type, to be used instead of NRT when nothing else indicates
what type to use. 2) A flag to indicate whether the default replica type
should override an existing type, which would cover things like MOVEREPLICA and
maybe others. When the user's request explicitly asks for a type, that would
of course take precedence over both of these settings.
> 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]
