ImportAuditConsumerWorker: fixed new audit PK violation detection

Previously the checked string accidentally implied default partition, now it works with any partition as expected.
Evolveum · Dec 17, 2021 · e3efeb8 · e3efeb8
1 parent d3fbcf6
commit e3efeb8
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/...nja/src/main/java/com/evolveum/midpoint/ninja/action/audit/ImportAuditConsumerWorker.java b/...nja/src/main/java/com/evolveum/midpoint/ninja/action/audit/ImportAuditConsumerWorker.java
@@ -60,7 +60,8 @@ public void run() {
                 } catch (Exception ex) {
                     Throwable cause = ExceptionUtil.findRootCause(ex);
                     // Short message for existing audit event conflict, but only for new repo
-                    if (cause.toString().contains("duplicate key value violates unique constraint \"ma_audit_event_default_pkey\"")) {
+                    if (cause.toString().contains("duplicate key value violates unique constraint \"ma_audit_event_")
+                            && cause.toString().contains("Detail: Key (id, \"timestamp\")")) {
                         context.getLog().info("Audit already exists, skipping ({}, {})",
                                 auditRecord.getRepoId(), auditRecord.getTimestamp());
                         operation.incrementSkipped(); // TODO: skipped or still error? also, info or error?