You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Gregory Chanan (JIRA)" <ji...@apache.org> on 2015/09/26 03:22:04 UTC

[jira] [Created] (SOLR-8098) Immutable ConfigSets can still change in ZK

Gregory Chanan created SOLR-8098:
------------------------------------

             Summary: Immutable ConfigSets can still change in ZK
                 Key: SOLR-8098
                 URL: https://issues.apache.org/jira/browse/SOLR-8098
             Project: Solr
          Issue Type: Bug
          Components: SolrCloud
    Affects Versions: 5.3, Trunk
            Reporter: Gregory Chanan


I don't think this is necessarily a bug, just writing it down here and tracking it so we have a reference.

Came up with an interesting case when I was testing Immutable ConfigSets.  I had defined a managed schema example as Immutable and was checking that all the files defined as part of the ConfigSet were present in ZooKeeper.  Occasionally, schema.xml was missing, which was surprising to me because I wasn't able to modify the schema (because it was Immutable).  Turns out that the managed schema renames the schema.xml when a collection is created using the schema, it doesn't need to be modified.

In theory we could build in some smarts to the ManagedIndexSchema to know it's immutable and so can avoid doing the rename, but it doesn't seem like we can handle this in general, i.e. any user-written schema can just do all sorts of schema modifications under the covers and decide not to check immutability.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org