Uploaded image for project: 'Sling'
  1. Sling
  2. SLING-3164

Clarify ClusterView.getId (was: Clarify and deprecate ClusterView.getId)

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • Discovery API 1.0.0
    • Discovery API 1.0.2
    • None
    • None

    Description

      As discussed on the list (at [0]) the ClusterView.getId() is currently unspecific about whether the id is stable/persistent or not. The current implementation of it is not stable and returns a new id with every changing cluster view. Without assumptions on the underlying implementation details it is not trivial to provide a stable id. This contrasts to the slingId of an InstanceDescription - which is guaranteed to be stable. A cluster can reshape and join another cluster, hence a cluster id is not trivial to be stable.

      The suggestion is to clarify the unstable nature of that id in its javadoc and marking it as deprecated - since there is no use for an unstable id really.

      [0] - http://markmail.org/message/kf3pydso7eruiwfg

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            stefanegli Stefan Egli
            stefanegli Stefan Egli
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment