[
https://issues.apache.org/jira/browse/JCR-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977334#action_12977334
]
Michael Dürig commented on JCR-2857:
------------------------------------
I'm a bit skeptical whether generating sequential node ids is the right
approach in general. It relies on assumptions about the underlying persistent
store and exposes these throughout the implementation and partially up to the
JCR api. I'd rather separate the concepts 'identifier' and 'locality'. That is,
I wouldn't encode locality hints into the identifiers directly (like you do)
but pass some locality hint (i.e. which nodes are likely to be accessed
together) to the persistent store. The later can use these and its knowledge
about the characteristics of the storage mechanism to optimize access.
For the original discussion see http://markmail.org/thread/3jzqjy6cavxcrpbq
> Support sequential (non-random) node ids
> ----------------------------------------
>
> Key: JCR-2857
> URL: https://issues.apache.org/jira/browse/JCR-2857
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Attachments: jcr-2857.patch
>
>
> Currently, node ids are generated using a (cryptographically secure pseudo-)
> random number generator. This has a many advantages (easy to implement, easy
> to merge nodes from multiple repositories or cluster nodes), but is a
> performance bottleneck for large repositories.
> In addition to generating random node ids, Jackrabbit should support
> generating sequential node ids.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
