Properly handle DB failures during events processing

Description

In SRS in ParsedRecordChunksKafkaHandler when duplicate comes for processing - it not handles. For described situation at the second attempt to store record to database exception from DB will occur and DI_ERROR will be sent. We should handle this situation and do nothing if ConstraintViolation exception throws. For all other DB exception we should contain to send DI_ERROR events through already implemented error handler.

Environment

None

Potential Workaround

None

CSP Request Details

None

CSP Approved

None

CSP Rejection Details

None

Checklist

hide

TestRail: Results

Activity

Show:

Khamidulla AbdulkhakimovNovember 10, 2021 at 1:38 PM

Hello , . In SRS, DI_ERROR is sent in all cases with a database problem except for the specified case (ConstraintViolation). Sending DI_ERROR occurs from mod-inventory after receiving the DI_SRS_MARC_BIB_RECORD_CREATED event from SRS.

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Folijet

Fix versions

Release

Lotus R1 2022

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created November 8, 2021 at 3:33 PM
Updated February 23, 2022 at 2:49 PM
Resolved November 19, 2021 at 1:43 PM
TestRail: Cases
TestRail: Runs