Content Downsync can cause Oak Conflict

[pat-lego]

The Content Downsync tool can cause an Oak conflict originating from here [1]. This occurs if the content was copied from source to target one time, and then the same content is copied from the same source to the same target but in a different location.

Of course there is a small probabilistic chance that there is a UUID collision, even if the use of the content copy tool was not executed. This is due to the fact that two of the exact same random UUID's can exist on two distinct systems causing a collision.

This should be disclosed to customers in the case that the content sync fails, one of the possible reasons is due to the fact that there was an oak conflict due to the unique constraint enforced by the UUID property index.

This information should be reflected in the Limitations section of the documentation.

[1] https://github.com/apache/jackrabbit-oak/blob/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/index/property/PropertyIndexEditor.java#L319-L340

[aheim0]

Thanks for raising this - we will investigate.

[aheim0]

@adobe export issue to Jira project CQDOC

[github-jira-sync-bot]

:white_check_mark: Jira issue CQDOC-21710 is successfully created for this GitHub issue.

[aheim0]

@pat-lego

Can you please confirm which page of the documentation you are requesting be updated (the page with the Limitations section)?

Thanks.

[pat-lego]

This is for the following documentation https://experienceleague.adobe.com/en/docs/experience-manager-cloud-manager/content/using/content-copy

The Limitations section is omitting the fact that an Oak Conflict exception occurs when the following scenarios described in comment occurs.

[aheim0]

@pat-lego Thanks for the additional information.