David Smiley created SOLR-17817:
-----------------------------------
Summary: Collection's AUTOCREATED configSet should move to the
col's ZNode
Key: SOLR-17817
URL: https://issues.apache.org/jira/browse/SOLR-17817
Project: Solr
Issue Type: Improvement
Reporter: David Smiley
The auto-created configSets are used to create a configSet for a collection in
some cases. It would make more sense for a Collection's own configSet to live
in Zookeeper under the collection's ZNode, in a "conf" node. Not an entire
copy of one, no, but an empty shell that could then be further manipulated with
a collection/core's config APIs without touching the reference. Can think of
this as a private ConfigSet instance that is mutable, layering / inheriting a
base configSet that is not. Such configSets would not be listable by the
ConfigSet API. This private configSet layer should always be backed up and
restored for collection backup & restore.
Why: ConfigSet mutability with doing collection specific config APIs would be
clearer – modify a collection's own private ConfigSet, not the base/foundation
one. Don't want ConfigSets to be mutable, except for explicit ConfigSet file
API uploads if that's exposed.
Additionally, within Solr it'd be nice if a collection could watch for updates
to its configset.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
