[
https://issues.apache.org/jira/browse/SLING-11467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17642398#comment-17642398
]
Angela Schreiber commented on SLING-11467:
------------------------------------------
[~kwin], no worries, it does work :-). i was about to reply to [~joerghoh] and
you were just faster.... there is no need to move around stuff and recreate or
remove.
[~joerghoh], is right though that this operation may fail if the new node type
comes with additional/different constraints that are not automatically
adjusted. so far repo-init doesn't provide any notion of best-effort and if an
operation fails the whole repo-init fails which leads to abortion of repository
startup.
on the other hand one might argue that the customer of the repoinit has the
ability to try it out and eventually fix the script if it doesn't work. i guess
i most cases the changes wold be simple and doable.
> support to update existing paths via repoinit statement
> -------------------------------------------------------
>
> Key: SLING-11467
> URL: https://issues.apache.org/jira/browse/SLING-11467
> Project: Sling
> Issue Type: Improvement
> Components: Repoinit
> Reporter: Darshan Mahor
> Priority: Major
>
> As of now we can't update the path if it already exists in repository[1] via
> repoinit statements like update primary type etc. This request is to support
> the mechanism via which we can modify/update the existing paths with the
> update/modification provided in repoinit statement. e.g. lets suppose we have
> a path in repostiory /content/test/testchild(nt:folder) and we want to
> modify it to /content/test/testchild(sling:Folder).
>
> [1].
> [https://github.com/apache/sling-org-apache-sling-jcr-repoinit/blob/master/src/main/java/org/apache/sling/jcr/repoinit/impl/AclVisitor.java#L189]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
