[ https://issues.apache.org/jira/browse/SOLR-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13452611#comment-13452611 ]
Yonik Seeley commented on SOLR-3815: ------------------------------------ As discussed in SOLR-3755, I've added an additional level to Slice so things like "range" and "replicationFactor" can be siblings of "replicas" (in my local copy - currently uncommitted). Example: {code} "shard5":{"replicas":{"127.0.0.1:58050_solr_collection1":{ "shard":"shard5", "leader":"true", "roles":null, "state":"active", "core":"collection1", "collection":"collection1", "node_name":"127.0.0.1:58050_solr", "base_url":"http://127.0.0.1:58050/solr"}}}}, {code} Since we're breaking back compat (just with older trunk), we should take the opportunity to make other changes as well. One candidate is to make the same change for Collections - adding an additional level so that other collection stats/properties can live alongside "shards" that contain the shards for the collection. Current: {code} "collection1":{ "shard3":{"replicas":{"127.0.0.1:58046_solr_collection1":{ {code} Proposal: {code} "collection1":{ "shards" : { "shard3":{"replicas":{"127.0.0.1:58046_solr_collection1":{ {code} Thoughts? Any other candidates for name changes while we are breaking compat anyway? > add hash range to shard > ----------------------- > > Key: SOLR-3815 > URL: https://issues.apache.org/jira/browse/SOLR-3815 > Project: Solr > Issue Type: Sub-task > Reporter: Yonik Seeley > Attachments: SOLR-3815.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org