[
https://issues.apache.org/jira/browse/SOLR-7742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616984#comment-14616984
]
Gregory Chanan commented on SOLR-7742:
--------------------------------------
bq. Yeah, I think that's a good idea to plan ahead and prevent a proliferation
of files-as-boolean-flags in the future. Then the other decision is whether to
expose a generic properties interface (i.e. the ability to set/get arbitrary
configset properties).
Good points. My thought here is to introduce a ConfigSet API that lets you
modify the properties on copy (this is required for immutable, since otherwise
a ConfigSet isn't really immutable and you can't use it as a template), but
there is no reason we have to limit the modifiable properties to just
immutability on copy. As for exposing a generic properties interface outside
of copy, that seems reasonable as well, though it's not on my short to-do list.
But we could have something like
/admin/configs/myConfig/properties GET/PUT/POST style interfaces.
> Support for Immutable ConfigSets
> --------------------------------
>
> Key: SOLR-7742
> URL: https://issues.apache.org/jira/browse/SOLR-7742
> Project: Solr
> Issue Type: New Feature
> Reporter: Gregory Chanan
> Assignee: Gregory Chanan
> Attachments: SOLR-7742
>
>
> See the discussion in SOLR-5955; to properly support collection "templates"
> that can be specified as the starting point for a collection configuration,
> we need support for ConfigSets that are immutable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
