[
https://issues.apache.org/jira/browse/OAK-6419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080085#comment-16080085
]
Torgeir Veimo edited comment on OAK-6419 at 7/10/17 10:34 AM:
--------------------------------------------------------------
Would it be possible to have someone with intimate knowledge of the clustering
setup provide an example method implemented with the Clusterable api?
The instanceId available through the Clusterable api seems only to be
guaranteed to be non-null, and is not necessarily persisted between restarts,
so it cannot really be used in a meaningful way to generate ids that are unique
in time.
was (Author: [email protected]):
Would it be possible to have someone with intimate knowledge of the clustering
setup provide an example method implemented with the clusterable api?
> unique id generator
> -------------------
>
> Key: OAK-6419
> URL: https://issues.apache.org/jira/browse/OAK-6419
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Reporter: Torgeir Veimo
> Priority: Minor
> Labels: counters, locking, sequence
>
> It would be great to have a way to safely generate unique id's for node
> names, with oak configured in a cluster configuration.
> This is useful for creating unique slug names for documents, and ensuring
> unique names for node siblings, or node names repository wide.
> It could be implemented as a sequence generator, or similar to how mongodb
> generates object ids; https://docs.mongodb.org/manual/reference/object-id/.
> With the older jackrabbit implementation it is possible to have a sequence
> guaranteed to provide unique id's, using enforceable locks. With oak theres
> no such guarantee when used in a clustered configuration.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
