[
https://issues.apache.org/jira/browse/SOLR-13271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17929897#comment-17929897
]
Jason Gerlowski commented on SOLR-13271:
----------------------------------------
I noticed recently that MODIFYCOLLECTION allows users to set arbitrary
properties for a collection, that are distinct from that collection's
"[collection
properties|https://solr.apache.org/guide/solr/latest/deployment-guide/collection-management.html#collectionprop]";.
As far as I can tell from a bit of code spelunking, that came about as a part
of this ticket. The first draft/patch here added {{readOnly}} support by
adding support for arbitrary properties more generally. Later revisions pivoted
to handling {{readOnly}} as a "first-class" property, similar to
replicationFactor, collection.configName, etc, but the plumbing for arbitrary
props stuck around into the final commit and wasn't commented on (afaict).
("Collection props" had been around for about a year at the time this ticket
was merged, having been previously added by
[SOLR-11960|https://issues.apache.org/jira/browse/SOLR-11960]...but they didn't
have a ton of use at that point, which maybe explains why they never came up as
an option here?)
Anyway, my question at this point: is there a reason to keep the arbitrary-prop
support in MODIFYCOLLECTION, or is there a reason to support these two
different avenues of prop-setting? Absent any objections or corrections here,
I'll file a separate ticket for that and discussion can continue there...
> 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
> Affects Versions: 8.0, 9.0
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Major
> Fix For: 8.1, 9.0
>
> Attachments: SOLR-13271.patch, SOLR-13271.patch
>
>
> Spin-off from SOLR-11127. In some scenarios it's useful to be able to block
> any index 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
