[
https://issues.apache.org/jira/browse/JCRVLT-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17734381#comment-17734381
]
Konrad Windszus commented on JCRVLT-709:
----------------------------------------
This issue tracker is for the Open Source tool Jackrabbit FileVault only (not
an AEM bug tracker). If you found an issue, please provide steps to reproduce
with just Jackrabbit modules (including the custom nodetypes if those are the
culprit here).
> VLT RCP command failing with NoSuchNodeTypeException
> -----------------------------------------------------
>
> Key: JCRVLT-709
> URL: https://issues.apache.org/jira/browse/JCRVLT-709
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: RCP
> Affects Versions: 3.6.8
> Reporter: CBVLT
> Priority: Major
> Attachments: image-2023-06-19-16-42-32-874.png
>
>
> Customer is using VLT RCP command (with the latest 3.6.8 version of
> vault-cli) to sync content from one author environment to another in AEM
> 6.5.17
> The newly created content fragments (post SP17 installation) now also get a
> node called "indexedData" under jcr:content which creates issues with this
> VLT RCP command that is failing with NoSuchNodeTypeException (screenshot
> attached). This new node was introduced for SITES-8297/SITES-97
> When removing these "indexedData" nodes from the affected content fragment
> the VLT RCP command runs perfectly. It seems as if VLT RCP doesn't recognize
> this node type.
> In AEM 6.5.16 the node "indexedData" didn't existed and VLT RCP worked fine.
> It seems that VLT RCP doesn't recognize this node type "indexedData" under
> jcr:content and it needs to add it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
