[
https://issues.apache.org/jira/browse/OAK-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15060186#comment-15060186
]
Davide Giannella commented on OAK-3529:
---------------------------------------
Don't know about multiple registration of the same class. The
DocumentNodeStoreServive already register itself as Clusterable with
deployed in OSGi.
https://github.com/davidegiannella/jackrabbit-oak/blob/OAK-3529/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/document/DocumentNodeStoreService.java#L496
What we need to think is about having a repository construction that
can provide .with(Clusterable) for plain java. I think in this case we
could register it with the whiteboard itself but still if done OOTB in
the Oak/Jcr constructor it's assuming the NodeStore will implement the
Clusterable, while it could actually be implemented by anything else.
Overall I'm in favour for the with() approach as it's transparent to
our current implementation and respect the Builder paradigm we're
using.
> 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)
