You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Danilo Banjac (Jira)" <ji...@apache.org> on 2024/05/15 06:51:00 UTC

[jira] [Updated] (JCRVLT-753) FORCE_REMOVE_CONFLICTING_ID Strategy Causing Constraint Violation Exception in AEM Replication

     [ https://issues.apache.org/jira/browse/JCRVLT-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Danilo Banjac updated JCRVLT-753:
---------------------------------
    Fix Version/s:     (was: 3.7.4)

> FORCE_REMOVE_CONFLICTING_ID Strategy Causing Constraint Violation Exception in AEM Replication
> ----------------------------------------------------------------------------------------------
>
>                 Key: JCRVLT-753
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-753
>             Project: Jackrabbit FileVault
>          Issue Type: Bug
>          Components: vlt
>            Reporter: Danilo Banjac
>            Assignee: Konrad Windszus
>            Priority: Major
>              Labels: vault
>
> AEM has a user synchronisation capability in the publish tier. The synchronisation mechanism relies on FileVault to export and import content.
> Users stored in the repository under a path that starts with a _ and that contain another _ can be exported but fail to be re-imported. For instance, the user stored under the path /home/users/test/_6k_test-user-a won't be imported.
> Debugging this issue, it seems that FileVault treats the _6k_ pattern as a namespace and thus skip the resource upon import because the paths don't match.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)