[
https://issues.apache.org/jira/browse/OAK-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14965015#comment-14965015
]
Davide Giannella commented on OAK-3529:
---------------------------------------
[~tmueller] I eventually went for a string representation as it gives
us more flexibility in case we would like to implement something
different or we'll have any new persistence layers in the future that
will not rely on integers.
With regards on limiting the number of characters: how would you
enforce it? Simply stating on the javadoc it cannot exceed XXX
characters?
If so I'd say that 36 characters are a good size as it's a String
representation of a UUID.
In any case I'm not convinced about the limit stated in a javadoc as
the limit sounds to me more an implementation detail.
> NodeStore API should expose an Instance ID
> ------------------------------------------
>
> Key: OAK-3529
> URL: https://issues.apache.org/jira/browse/OAK-3529
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Davide Giannella
> Assignee: Davide Giannella
> Fix For: 1.4
>
> Attachments: OAK-3529-1.patch, OAK-3529-2.patch
>
>
> For better leveraging cluster oriented algorithm: discovery, atomic
> operations; it would be very helpful if the NodeStore could expose a
> unique instance id.
> This can be the same as a cluster ID.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
