[
https://issues.apache.org/jira/browse/OAK-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-3529:
----------------------------------
Attachment: OAK-3529-7.patch
here's a [last review|^OAK-3529-7.patch] of the problem where I implemented the
approach by providing {{with(Clusterable)}} on both Jcr and Oak builder.
This should allow us with as much flexibility as possible. It won't touch an
existing behavior and when/if we need it in UT/IT we simply need to construct
the repository by using it. So far we didn't have the need.
[~mduerig] please review
/cc [~mreutegg]
> 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, OAK-3529-3.patch,
> OAK-3529-4.patch, OAK-3529-5.patch, OAK-3529-6.patch, OAK-3529-7.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)
