[ 
https://issues.apache.org/jira/browse/SOLR-13271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16779814#comment-16779814
 ] 

Christine Poerschke commented on SOLR-13271:
--------------------------------------------

{quote}... In some scenarios it's useful to be able to block any updates to a 
collection, while still being able to search its contents. ...
{quote}
One edge case scenario could be even a collection that is deliberately empty 
i.e. it has no content of its own but its replicas serve as 'federators' i.e. 
callers pass the {{&collection=fooBar}} parameter in queries sent to the 
'empty' collection and the empty collection replicas do load balancing, 
federating and collating work.
{quote}... A more natural API would be to use a primary collection attribute: 
...
{quote}
{quote}... Using property makes the API a little awkward, it should be a 
primary attribute I think. ...
{quote}
I agree, a primary collection attribute seems clearer.
{quote}... We should be careful to document that setting the readOnly mode can 
take a long time because the reload can cause IW.close which can trigger merges 
etc.
{quote}
Great point! On initial thought it would be easy to think "read only" is quick 
and the merge connection is not obviously apparent.

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.

> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to