[
https://issues.apache.org/jira/browse/SLING-10463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17359360#comment-17359360
]
Tom Blackford commented on SLING-10463:
---------------------------------------
Sorry for slow reply [~bdelacretaz] / [~angela].
Yes - the more conservative approach would be fine from my perspective. I toyed
with doing something like that - but I wasn't sure that there were not
situations where creating a node at a path which matches the path of an
existing property might be required.
My only concern is that failures in RepoInit are hard to troubleshoot etc (see
this case) since AEM itself isn't up (and therefore pods keep getting killed in
a K8s-based deployment).
Alternatively I guess we could emit a WARN message but I doubt anybody would
notice.
> Repoinit fails to create node if property already exists at the same path
> -------------------------------------------------------------------------
>
> Key: SLING-10463
> URL: https://issues.apache.org/jira/browse/SLING-10463
> Project: Sling
> Issue Type: Bug
> Components: Repoinit
> Reporter: Tom Blackford
> Priority: Minor
> Attachments: SLING-10463.patch
>
>
> If a property already exists at the path of a node described in repoinit,
> then the repoinit will incorrectly assume the node does not need to be
> created.
> Test case & fix - [^SLING-10463.patch]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
