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 "Alex Deparvu (JIRA)" <ji...@apache.org> on 2018/06/12 09:15:00 UTC

[jira] [Commented] (OAK-7532) VersionStorageEditor should allow bootstraping of initial content

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

Alex Deparvu commented on OAK-7532:
-----------------------------------

proposed solution on a wip branch [0]. the tricky part is to figure out when we're dealing with that initial creation, and I tried to use the {{:initialized}} property, but it kinda looks funky. would like to get other opinions on this. also, I would like to move this property to (probably?) the {{VersionConstants}} class. [~mreutegg] could you take a look?




[0] https://github.com/apache/jackrabbit-oak/compare/trunk...stillalex:oak-7532

> VersionStorageEditor should allow bootstraping of initial content
> -----------------------------------------------------------------
>
>                 Key: OAK-7532
>                 URL: https://issues.apache.org/jira/browse/OAK-7532
>             Project: Jackrabbit Oak
>          Issue Type: Technical task
>          Components: core
>            Reporter: Alex Deparvu
>            Assignee: Alex Deparvu
>            Priority: Major
>
> Right now the VersionStorageEditor does not allow any node creation to happen under its root, but the InitialContent has a flag that effectively creates a barebones structure. this works because this happens as a repository initializer which bypasses the integrity checks.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)