[
https://issues.apache.org/jira/browse/OAK-10890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated OAK-10890:
------------------------------
Description: In cases where we notice a "uuid already exists" constraint
violation - something that eg can happen when 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). (was: 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).)
> Logging for constraint violations (UUID already exists)
> -------------------------------------------------------
>
> Key: OAK-10890
> URL: https://issues.apache.org/jira/browse/OAK-10890
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: documentmk
> Reporter: Ionut Pirlogea
> Priority: Trivial
>
> In cases where we notice a "uuid already exists" constraint violation -
> something that eg can happen when 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)
