[
https://issues.apache.org/jira/browse/SOLR-13271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16780307#comment-16780307
]
Andrzej Bialecki commented on SOLR-13271:
------------------------------------------
Thanks for the comments - I'll upload a new patch shortly.
bq. And I guess if segment merging cannot happen in read-only mode then "shard
splitting" (or indeed "shard merging") would also be out of the question in
read-only but replica additions or moves could be okay? That's out of scope
here though perhaps in the context of the .system collection migration.
Hmm, the read-only aspect in this issue applies only to index updates - I
should've made it clearer. Replica movements / additions / deletions are not
strictly index updates so they are still possible.
Also, the way SOLR-11127 is shaping up it will be possible to specify a
different layout of the collection when reindexing, basically all collection
CREATE params will be available.
> Implement a read-only mode for a collection
> -------------------------------------------
>
> Key: SOLR-13271
> URL: https://issues.apache.org/jira/browse/SOLR-13271
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 8.x, master (9.0)
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Major
> Fix For: 8.x, master (9.0)
>
> Attachments: SOLR-13271.patch
>
>
> Spin-off from SOLR-11127. In some scenarios it's useful to be able to block
> any updates to a collection, while still being able to search its contents.
> Currently the scope of this issue is SolrCloud, ie. standalone Solr will not
> be supported.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
