@cap-js-community/event-queue - npm Package Versions

v1.4.1 - 2024-03-27

Changed

• Removed authInfo from context.http.req and moved to a full-fledged xssec/xsuaa authInfo attached to context.user.authInfo
• [cds-plugin] return promise for init for cds to wait until plugin is fully initialized

v1.4.0 - 2024-03-21

Added

• add to supply custom redis options for create client.

Changed

• Reworked periodic processing of all events to be more efficient and to reduce the load on the database and use less database connections.
• Removed support for custom tables. The event-queue now uses always the provided tables.

v1.3.6 - 2024-03-14

Fixed

• Redis reconnects

v1.3.5 - 2024-03-12

Fixed

• In instances of overlapping intervals, periodic events may fall behind schedule.

v1.3.4 - 2024-03-08

Added

• Trigger processing again if time is exceeded for event processing.

Changed

• removed CF check to enable redis to allow using redis even if process.env.USER is not vcap.

v1.3.3 - 2024-03-06

Changed

• Default for runInterval changed from 5 minutes to 25 minutes. This is to reduce the load on the database.
• The load of the internal periodic event DELETE_EVENTS is increased to 20 to only process 5 tenants in parallel. This is to reduce the load on the database.
• The max processing time for the event-queue is set to the runInterval.

v1.3.2 - 2024-03-01

Added

• option for delayed events for cds outboxed services: documentation

Fixed

• Delay registration of processors until the database connection is established.

v1.3.1 - 2024-02-21

Fixed

• Log message for blocked events

Changed

• Reduce log severity for skip publish redis event as no lock is available to debug
• Only do etag checks after a processing time of 10 minutes to improve performance

v1.3.0 - 2024-02-21

Added

• add option to block ad-hoc events. More information in documentation.
• Define priorities for event types. More information in documentation.

Fixed

• In more cases the global cds.context was not set correctly because the async-chain could break in high load scenarios.

v1.2.6 - 2024-02-15

Fixed

• In some cases the global cds.context was not set correctly because the async-chain could break in high load scenarios.