Content Downsync can cause Oak Conflict

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

Start by reviewing the linked PropertyIndexEditor.java lines 319-340 to understand the Oak conflict cause. Locate the documentation's Limitations section and document that content downsync can fail because of UUID conflicts, including the stated customer disclosure. Done means the limitation and possible sync failure reason are clearly reflected there.

Written by the indexing model from the issue text.