The API shouldn't be changing, did you run into any errors? Don't bother to raise a JIRA, I checked through IM and the /clusterstate.json is still being used as a watch point for things like creating collections, and there are other JIRAs afoot that will take care of this at the at the right time.
Best, Erick On Wed, Aug 5, 2015 at 1:54 PM, Suma Shivaprasad <sumasai.shivapra...@gmail.com> wrote: > Thanks Shawn. > > Does this mean in client code, wherever we are using the API > > "ZkStateReader.getClusterState.getCollections" to get status should be > changed to > "CollectionsAdminRequest.ClusterStatus" for each collection or will that > API continue to work ? > > Thanks > Suma > > On Wed, Aug 5, 2015 at 11:00 PM, Shawn Heisey <apa...@elyograg.org> wrote: > >> On 8/5/2015 9:22 AM, Suma Shivaprasad wrote: >> > Hello, >> > >> > Is /clusterstate.json in Zookeeper updated with collection state if a >> > collection is created with server running in Solr Cloud mode without >> > creating a core through coreAdmin or providing a core.properties . I find >> > that there is a "state.json" present under /collections/<collection_name> >> > which reflects the collection status . However dont find the >> > /clusterstate.json updated. Is this an expected behaviour ? >> >> Yes, that is expected behavior. A separate clusterstate for each >> collection was one of the big new features in Solr 5.0: >> >> https://issues.apache.org/jira/browse/SOLR-5473 >> >> Thanks, >> Shawn >> >>
