Unify actions processing to use data-import flow

Description

Purpose:
All actions in quickMarc should be processed with the data-import flow and use a status-ping approach while providing a response to UI.
mod-quick-marc should support HA

Approach:

  • Use already implemented for derive MARC bib and create MARC holdings code base for data-import job initializing

  • Using ReplyingKafkaTemplate instead of the combination of DeferredResult and cache

    • Configure template to receive events from DI_COMPLETED and DI_ERROR topics

    • Start data-import process record by sending DI_RAW_RECORDS_CHUNK_READ instead of using POST /jobExecutions/jobExecutionId/records endpoint

    • Specify a timeout for confirmation receiving (1 min ??)

    • If the timeout is exceeded then use combination of GET /metadata-provider/jobLogEntries/jobExecutionId and GET /metadata-provider/jobLogEntries/jobExecutionId/records/кecordId endpoints to get the status of job and error message if it failed.

Acceptance criteria:

  • Update unit/integration tests

  • Update Karate tests

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Kateryna SenchenkoApril 28, 2022 at 1:26 PM

Hi , we are currently working on implementing Flow control functionality that should allow single record imports to take precedence over regular import. I assume the same should apply to quick marc updates in case they are going to use the same topics as a regular data import. That's something we should take into account, so maybe lets set up a meeting and discuss it. Thank you!

CC: , , ,

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Spitfire

Release

Morning Glory (R2 2022)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created April 18, 2022 at 10:10 AM
Updated October 5, 2022 at 10:52 AM
Resolved May 13, 2022 at 1:20 PM
TestRail: Cases
TestRail: Runs