You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2015/12/08 11:23:11 UTC

[jira] [Commented] (OAK-3529) NodeStore API should expose an Instance ID

    [ https://issues.apache.org/jira/browse/OAK-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046694#comment-15046694 ] 

Michael Dürig commented on OAK-3529:
------------------------------------

Looks good re. {{Clusterable}}. Maybe [~mreutegg] should have a quick look re. the DocumentMK specifics. 

I'm not too happy with the {{getInstanceId()}} methods on the builder though. Are those really necessary? After all, users of those builders usually pass the node store along so they have access to the instance id already. 

> 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
>
>
> 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)