/
Authority DI Events Migration: mod-inventory → mod-entities-links

Authority DI Events Migration: mod-inventory → mod-entities-links

Authority DI Events Migration: mod-inventory → mod-entities-links

Related Jira: APPAUTHREC-3 Module version: mod-entities-links v5.0.0

Overview

Starting from mod-entities-links v5.0.0, the responsibility for consuming Authority-related Data Import (DI) Kafka events has been moved from mod-inventory to mod-entities-links. This eliminates the intermediate hop through mod-inventory and brings Authority record processing closer to its natural domain boundary.

The outdated Authority DI event handling code has already been removed from mod-inventory — no coordination with the mod-inventory team is required.

Previous flow:

data-import → Kafka → mod-inventory → (HTTP) → mod-entities-links

New flow:

data-import → Kafka → mod-entities-links

Required Actions for Operators

Migrate the AUTHORITY_EXTENDED Environment Variable

The AUTHORITY_EXTENDED environment variable was previously set on mod-inventory. It must now be set on mod-entities-links instead.

Action: Copy the current value of AUTHORITY_EXTENDED from your mod-inventory deployment and add it to your mod-entities-links deployment configuration.

Kafka Topics Reference

mod-entities-links automatically creates and subscribes to all required Kafka topics on startup — no manual topic management is needed.

Topics published:

Topic name (pattern)

Partitions (default)

Topic name (pattern)

Partitions (default)

{ENV}.{TENANT}.DI_INVENTORY_AUTHORITY_UPDATED

8

{ENV}.{TENANT}.DI_INVENTORY_AUTHORITY_CREATED_READY_FOR_POST_PROCESSING

8

Topics consumed:

Topic name pattern

Topic name pattern

{ENV}.[A-Za-z0-9-]+.\w+.DI_SRS_MARC_AUTHORITY_RECORD_CREATED

{ENV}.[A-Za-z0-9-]+.\w+.DI_SRS_MARC_AUTHORITY_RECORD_MODIFIED_READY_FOR_POST_PROCESSING

{ENV}.[A-Za-z0-9-]+.\w+.DI_SRS_MARC_AUTHORITY_RECORD_DELETED

{ENV}.[A-Za-z0-9-]+.\w+.DI_SRS_MARC_AUTHORITY_RECORD_NOT_MATCHED

{ENV}.[A-Za-z0-9-]+.\w+.DI_JOB_CANCELLED

The number of partitions and replication factor for published topics can be tuned via the environment variables listed in the next section.

Environment Variable Changes

New Environment Variables

The following environment variables have been introduced in mod-entities-links v5.0.0:

Variable

Default

Description

Variable

Default

Description

KAFKA_DI_CONSUMER_CONCURRENCY

4

Number of concurrent consumers for DI authority events

KAFKA_DI_CANCELED_CONSUMER_CONCURRENCY

1

Number of concurrent consumers for canceled DI job events

KAFKA_DI_INVENTORY_AUTHORITY_UPDATED_PARTITIONS

8

Number of partitions for the DI_INVENTORY_AUTHORITY_UPDATED topic

KAFKA_DI_INVENTORY_AUTHORITY_UPDATED_REPLICATION_FACTOR

(broker default)

Replication factor for the DI_INVENTORY_AUTHORITY_UPDATED topic

KAFKA_DI_INVENTORY_AUTHORITY_CREATED_READY_FOR_POST_PROCESSING_PARTITIONS

8

Number of partitions for the DI_INVENTORY_AUTHORITY_CREATED_READY_FOR_POST_PROCESSING topic

KAFKA_DI_INVENTORY_AUTHORITY_CREATED_READY_FOR_POST_PROCESSING_REPLICATION_FACTOR

(broker default)

Replication factor for the DI_INVENTORY_AUTHORITY_CREATED_READY_FOR_POST_PROCESSING topic

DI_CANCELED_JOB_CACHE_MAX_SIZE

500

Maximum number of canceled job IDs to cache

DI_CANCELED_JOB_CACHE_TTL

24h

Time-to-live for cached canceled job IDs

Migrated Environment Variables

The following variable was previously configured on mod-inventory and must now be configured on mod-entities-links:

Variable

Description

Variable

Description

AUTHORITY_EXTENDED

Enables extended MARC-to-Authority mapping rules. Move this value from your mod-inventory configuration to mod-entities-links.

Unchanged Environment Variables

All other previously defined environment variables remain valid and unchanged. No existing variables have been removed or renamed.

Related Issues

  • APPAUTHREC-3 — Authority refactoring: move consumption of DI events from mod-inventory