[
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-6.patch
[~mduerig]
bq. Re. the patch, there is a problem in the order of initialisation: the store
member is used before it is initialised in Jcr(Oak)
True. In [OAK-3529-6.patch|^OAK-3529-6.patch] there's a last attempt to
workaround the fact that we expect the NodeStore to provide Clusterable. It's
quite a refactoring. IMO it's better to go straight for adding
{{.with(Clusterable}}.
Thoughts?
/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
>
>
> 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)
