You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Ionut Pirlogea (Jira)" <ji...@apache.org> on 2024/06/17 09:41:00 UTC

[jira] [Comment Edited] (OAK-10895) Logging for constraint violations (UUID already exists)

    [ https://issues.apache.org/jira/browse/OAK-10895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855567#comment-17855567 ] 

Ionut Pirlogea edited comment on OAK-10895 at 6/17/24 9:40 AM:
---------------------------------------------------------------

Yes, actually is another message for error, this was the confusion. 


was (Author: JIRAUSER305793):
Yes, actually is another message for error, this was the confusion. I will close this ticket.

> Logging for constraint violations (UUID already exists)
> -------------------------------------------------------
>
>                 Key: OAK-10895
>                 URL: https://issues.apache.org/jira/browse/OAK-10895
>             Project: Jackrabbit Oak
>          Issue Type: Task
>            Reporter: Ionut Pirlogea
>            Priority: Trivial
>
> In cases where we notice a "uuid already exists" constraint violation - something that eg can happen in Content Backflow reimporting the same content which was previously semi-imported - we should increment a metric and ensure we log the required information (unless the latter is already done through the current exception - but even then we might want to add perhaps an additional, explicit log about just the encounter, independent-of/in-addition-to the exception).



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