[ https://issues.apache.org/jira/browse/SLING-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13800694#comment-13800694 ]
Stefan Egli commented on SLING-3195: ------------------------------------ As mentioned on the thread I suggest to revert SLING-3164 - ie *not* deprecating ClusterView.getId() - adjusting the API stating that the ID should be stable (following best-effort - ie exceptions with cluster-reformations are allowed) - and adjusting the implementation accordingly > Provide a property to uniquely identify a Cluster > ------------------------------------------------- > > Key: SLING-3195 > URL: https://issues.apache.org/jira/browse/SLING-3195 > Project: Sling > Issue Type: New Feature > Components: Commons > Reporter: Chetan Mehrotra > > In some scenarios we need to unique idenitfy a cluster via stable identifier. > ClusterView provides an ID property but that is termed as unstable > [SLING-3164]. It would be helpful if it can be made stable or some other > mechanism is provided to identify the cluster > Mail Thread - http://markmail.org/message/kf3pydso7eruiwfg -- This message was sent by Atlassian JIRA (v6.1#6144)