RHEA-2024:7859 - Product Enhancement Advisory

Topic

Red Hat build of Debezium connectors in version 2.7.3 is now available for Red Hat Application Foundations.

Description

Debezium is a distributed platform that turns your existing databases into event streams, so applications can see and respond immediately to each row-level change in the databases.

Debezium is built on top of Apache Kafka and provides Kafka Connect compatible connectors that monitor specific database management systems. Debezium records the history of data changes in Kafka logs, from where your application consumes them. This makes it possible for your application to easily consume all of the events correctly and completely. Even if your application stops unexpectedly, it will not miss anything: when the application restarts, it will resume consuming the events where it left off.

Solution

To apply this update just follow standard installation procedure

• https://docs.redhat.com/en/documentation/red_hat_build_of_debezium/2.7.3/html-single/installing_debezium_on_openshift/index

https://docs.redhat.com/en/documentation/red_hat_build_of_debezium/2.7.3/html-single/installing_debezium_on_rhel/index

Affected Products

• Red Hat Integration Text-Only Advisories x86_64
• Red Hat Integration 1 x86_64

Fixes

• DBZ-4332 - Add ROW_ID as part of source information block for LogMiner sources
• DBZ-5009 - Make ORA-00600 - krvrdccs10 automatically retriable
• DBZ-5071 - Use row value constructors to speed up multi-column queries for incremental snapshots
• DBZ-5182 - Debezium 1.9.2 cannot capture field that is date type of postgres
• DBZ-6432 - Add Number of records captured and processed as metrics for Debezium MongoDB Connector
• DBZ-6522 - Unable to use resume token of some documents with composite IDs
• DBZ-6618 - Document the use of the "source" prefix usage for table name formats
• DBZ-6722 - Decompose provide.transaction.metadata into components
• DBZ-6900 - debezium-connector-jdbc occurred java.sql.SQLException: ORA-01461: can bind a LONG value only
• DBZ-7079 - Oracle property column.truncate.to.length.chars does not support length zero
• DBZ-7107 - Introduce a new microsecond/nanosecond precision timestamp in envelope
• DBZ-7138 - Adding additional-conditions into Incremental Snapshot to MongoDB
• DBZ-7147 - Document MongoDB connector inactivity pause and it's performance implications
• DBZ-7167 - Provide a public API from the connector implementations to retrieve the list of matching collections or tables based on the different include-/exclude lists
• DBZ-7212 - Reduce RS Discovery overhead for RS clusters and Sharded clusters with sharded connection mode
• DBZ-7233 - Unify snapshot modes across all connectors
• DBZ-7249 - Notifications are Missing the ID field in log channel
• DBZ-7258 - JDBC Storage does not support connection recovery
• DBZ-7260 - Remove replica_set connection mode
• DBZ-7273 - Provide alternative direct query for faster execution
• DBZ-7284 - Provide config option to customize CloudEvents.data schema name
• DBZ-7286 - Enhance Oracle's CREATE TABLE for Multiple Table Specifications
• DBZ-7287 - Clarify comment on serialization of document ids
• DBZ-7288 - Unittest for hasCommitAlreadyBeenHandled in CommitScn Class
• DBZ-7300 - Move Snapshotter interface to core module as SPI
• DBZ-7301 - Implement Snapshotter SPI MySQL/MariaDB
• DBZ-7304 - Align snapshot modes for MongoDB
• DBZ-7305 - Align snapshot modes for DB2
• DBZ-7308 - Align all snapshot mode on all connectors
• DBZ-7309 - Update snapshot mode documentation
• DBZ-7342 - errors.max.retries is not used to stop retrying
• DBZ-7355 - MySqlJdbcSinkDataTypeConverterIT#testBooleanDataTypeMapping fails
• DBZ-7362 - Support DECFLOAT in Db2 connector
• DBZ-7370 - Create PubSub example for DS deployed via operator
• DBZ-7376 - Fix logging for schema only recovery mode in mysql connector
• DBZ-7380 - Put transaction id in offsets only when it's present
• DBZ-7382 - Records from snapshot delivered out of order
• DBZ-7387 - Use Java 17 as compile-time dependency
• DBZ-7389 - Oracle connector unable to find SCN after Exadata maintenance updates
• DBZ-7416 - Duplicate Debezium SMT transform
• DBZ-7435 - Need to be able to set an ordering key value
• DBZ-7439 - Adopt Oracle 23 to Testing Farm
• DBZ-7446 - Reduce string creation during SQL_REDO column read
• DBZ-7451 - Support UUID as document key for incremental snapshotting
• DBZ-7458 - Oracle LOB requery on Primary Key change does not work for all column types
• DBZ-7461 - Align snapshot modes for PostgreSQL, MySQL, Oracle
• DBZ-7463 - SQL Server queries with special characters fail after applying DBZ-7273
• DBZ-7473 - Defer transaction capture until the first DML event occurs
• DBZ-7480 - Allow special characters in signal table name
• DBZ-7481 - Snapshotter SPI wrongly loaded on Debezium Server
• DBZ-7485 - Builtin database name filter is incorrectly applied only to collections instead of databases in snapshot
• DBZ-7495 - Unify and adjust thread time outs
• DBZ-7496 - Completion callback called before connector stop
• DBZ-7497 - Provide a generic snapshot mode configurable via connector properties
• DBZ-7498 - Add "IF [NOT] EXISTS" DDL support for Oracle 23
• DBZ-7499 - Deployment examples show attribute name instead of its value
• DBZ-7505 - Support Oracle 23 SELECT without FROM
• DBZ-7506 - Add Oracle 23 Annotation support for CREATE/ALTER TABLE statements
• DBZ-7512 - Support arbitrary payloads with outbox event router on debezium server
• DBZ-7526 - signalLogWithEscapedCharacter fails with pgoutput-decoder
• DBZ-7530 - Rework shouldGenerateSnapshotAndContinueStreaming assertions to deal with parallelization
• DBZ-7534 - Multi-threaded snapshot can enqueue changes out of order
• DBZ-7545 - Explicitly import jakarta dependencies that are excluded via glassfish filter
• DBZ-7570 - Log exception details early in case MySQL keep-alive causes deadlock on shutdown
• DBZ-7575 - Debezium Server Kafka BLOCKED forever when Kafka send failed
• DBZ-7585 - Snapshot skipping records
• DBZ-7600 - Allow schema_only_recovery where history exists
• DBZ-7601 - Incremental snapshots don't work with CloudEvent converter
• DBZ-7610 - Remove LogMiner continuous mining configuration option
• DBZ-7615 - Enhanced event timestamp precision combined with ExtractNewRecordState not working
• DBZ-7616 - Provide query timeout property to avoid indefinitely hangs during queries
• DBZ-7618 - Implement Versioned interfaces in Transformation and Converter plugins
• DBZ-7620 - JDBC connector does not process ByteBuffer field value
• DBZ-7640 - Allow skipping of table row count in snapshot phase
• DBZ-7645 - Revert removal of Oracle LogMiner continuous mining
• DBZ-7652 - Bump MySQL driver from 8.0.33 to 8.3.0
• DBZ-7693 - Move MariaDB connector from MySQL to its own separate connector
• DBZ-7695 - Mongodb Delete events should have `_id` in the payload
• DBZ-7697 - After the initial deployment of Debezium, if a new table is added to MSSQL, its schema is was captured
• DBZ-7716 - Incremental Snapshot: read duplicate data when database has 1000 tables
• DBZ-7717 - Move LogPositionValidator outside the JdbcConnection
• DBZ-7718 - Manage escaping when captured table are determined for snapshot
• DBZ-7732 - Snapshot fails with an error of invalid lock
• DBZ-7737 - Column CON_ID queried on V$THREAD is not available in Oracle 11
• DBZ-7743 - The MySQL Debezium connector is not doing the snapshot after the reset.
• DBZ-7744 - MongoDb connector doesn't work with Load Balanced cluster
• DBZ-7750 - Update max.iteration.transactions to a sensible default
• DBZ-7752 - Support for ARRAY data types for postgres
• DBZ-7753 - Introduce `RawToString` transform for converting GUIDs stored in Oracle `RAW(16)` columns to Guid string
• DBZ-7755 - Refactor exporting to CloudEvents
• DBZ-7757 - Apply MySQL binlog client version 0.29.1 - bugfix: read long value when deserializing gtid transaction's length
• DBZ-7759 - Change streaming exceptions are swallowed by BufferedChangeStreamCursor
• DBZ-7760 - Suport collection scoped streaming
• DBZ-7761 - Improve NLS character set support by including orai18n dependency
• DBZ-7763 - Use thread cap only for deault value
• DBZ-7765 - Sql-Server connector fails after initial start / processed record on subsequent starts
• DBZ-7767 - Debezium Server cannot pass empty string to Kafka config
• DBZ-7770 - Valid resume token is considered invalid which leads to new snapshot with some snapshot modes
• DBZ-7780 - NO_DATA snapshot mode validation throw DebeziumException on restarts if snapshot is not completed
• DBZ-7783 - Remove dependency on MySQL driver, add custom CharacterSet Mapper
• DBZ-7786 - Document new MariaDB connector
• DBZ-7788 - DDL statement couldn't be parsed
• DBZ-7789 - Document potential null values in the after field for lookup full update type
• DBZ-7790 - Debezium oracle connector will lose the data of the update operation when the table has no primary key and contains lob type
• DBZ-7797 - Incremental snapshot fails with NPE if surrogate key doesn't exist
• DBZ-7798 - Documentation for Debezium Scripting mentions wrong property
• DBZ-7800 - Enhance documentation about using tags to customize connector snapshot/streaming MBean names
• DBZ-7801 - Add heartbeat action query to SQL Server
• DBZ-7803 - Debezium User Guide 2.5.4: Grammatical error
• DBZ-7805 - > io.debezium.text.ParsingException : SQL Contains Partition
• DBZ-7806 - Ad-hoc blocking snapshot not working through file channeling without inserting a row in the database.
• DBZ-7811 - Fix invalid date/timestamp check & logging level
• DBZ-7815 - Fix anchor ID collisions that prevent downstream documentation from building
• DBZ-7816 - Postgres: Potential data loss on connector restart
• DBZ-7819 - Allow specifying the log mining flush table with an optional schema
• DBZ-7822 - Add c3p0 timeout configuration example to JDBC sink
• DBZ-7826 - Abnormal Behavior in Debezium Monitoring Example - mysql connector
• DBZ-7828 - Sql Server incorrectly applying quoted snapshot statement overrides
• DBZ-7829 - Added nats JWT/seed authentication config options
• DBZ-7830 - Debezium JDBC Sink not handle order correctly
• DBZ-7831 - Oracle connector failed to work when the table name contains single quote
• DBZ-7844 - Fix typo in documentation/modules doc
• DBZ-7845 - Rewrite batch statement not supported for jdbc debezium sink
• DBZ-7847 - Debezium oracle connectors needs to support IN clause for log miner query for more than 1000 tables as it creates performance issue
• DBZ-7858 - Debezium MySQL Snapshot Connector Fails
• DBZ-7859 - Reduce enum array allocation
• DBZ-7862 - MongoDB documentation still mentions replica_set connection mode
• DBZ-7864 - Support Oracle DDL Alter Audit Policy
• DBZ-7865 - Support Oracle DDL Create Audit Policy
• DBZ-7870 - Default value of error retries not interpreted correctly
• DBZ-7871 - Too much logs after Debezium update
• DBZ-7874 - MariaDB target should support 'upsert' for insert.mode
• DBZ-7878 - Test Geometry and Geography columns during Initial Snapshot
• DBZ-7880 - Avro schema compatibility issues when upgrading from Oracle Debezium 2.5.3.Final to 2.6.1.Final
• DBZ-7881 - ParsingException (MySQL 8): create trigger if exists
• DBZ-7882 - Oracle connector decimal.handling.mode improvement
• DBZ-7886 - Oracle Debezium Connector cannot startup due to failing incremental snapshot
• DBZ-7887 - Allow customizing ObjectMapper in JsonSerde
• DBZ-7889 - Multiple completed reading from a capture instance notifications
• DBZ-7890 - Remove incubating note from post-processors index.adoc file
• DBZ-7893 - Debezium can't handle columns with # in its name
• DBZ-7895 - Clarify that Oracle connector does not read from physical standby
• DBZ-7898 - Oracle interval default values are not properly parsed
• DBZ-7902 - Add configurable delay after successful snapshot before starting streaming
• DBZ-7904 - Debezium server unable to shutdown on pubsub error
• DBZ-7906 - Enhancing the threads utility class for broader use
• DBZ-7908 - Oracle connector cannot parse SUBPARTITION when altering table
• DBZ-7912 - The explanation in the documentation is insufficient - metric
• DBZ-7917 - Read-only incremental snapshots for PostgreSQL
• DBZ-7926 - Incorrect documentation for CE type
• DBZ-7931 - DDL statement couldn't be parsed
• DBZ-7933 - SQL Server default value resolution for TIME data types causes precision loss
• DBZ-7935 - OlrNetworkClient does not disconnect when error occurs
• DBZ-7938 - Multiple ARRAY types in single table causing error
• DBZ-7939 - Clarify documentation for log.mining.archive.destination.name Oracle configuration property
• DBZ-7942 - Ad-hoc snapshot raises ORA-00911 when table name uses non-standard characters requiring quotations
• DBZ-7944 - Exclude signaling data collection from the snapshot process
• DBZ-7946 - JdbcSinkTask doesn't clear offsets on stop
• DBZ-7947 - Warn about incompatible usage of read.only property for PostgreSQL
• DBZ-7951 - Commit is not called after DDLs in JDBC stores
• DBZ-7956 - Database case sensitivity can lead to NullPointerException on column lookups
• DBZ-7964 - Error counter reset in poll() can cause infinite retries
• DBZ-7967 - Oracle DDL parser fails using NOMONITORING clause
• DBZ-7987 - Mongo Oversized Document FAQ documentation issue
• DBZ-7991 - Issue with Hybrid mode and DDL change
• DBZ-8008 - Move JDBC sink connector into main repository
• DBZ-8011 - StackOverflow exception on incremental snapshot
• DBZ-8018 - JDBC primary.key.fields cannot be empty when i set insert.mode to upsert and primary.key.mode record_value
• DBZ-8022 - Unable to acquire buffer lock, buffer queue is likely full
• DBZ-8023 - ORA-65090: operation only allowed in a container database when connecting to a non-CDB database
• DBZ-8027 - Postgres connector - null value processing for "money" type column.
• DBZ-8031 - Add disclaimer that PostProcessors and CustomConverters are Debezium source connectors only
• DBZ-8032 - Using snapshot.include.collection.list with Oracle raises NullPointerException
• DBZ-8037 - Add `kafka.producer` metrics to debezium-server jmx exporter config
• DBZ-8044 - Log additional details about abandoned transactions
• DBZ-8050 - "Unexpected input: ." when snapshot incremental empty Database
• DBZ-8055 - Oracle connector inconsistency in redo log switches
• DBZ-8058 - Blocking snapshot can fail due to CommunicationsException
• DBZ-8066 - ParsingException (MySQL/MariaDB): rename table syntax
• DBZ-8068 - Oracle histogram metrics are no longer printed in logs correctly
• DBZ-8070 - In hybrid log.mining.strategy reconstruction logs should be set to DEBUG
• DBZ-8071 - Performance degradation when reconstructing (log.mining.stragtegy hybrid mode)
• DBZ-8076 - Support capturing BLOB column types during snapshot for MySQL/MariaDB
• DBZ-8081 - Conditionalize reference to the MySQL default value in description of `schema.history.internal.store.only.captured.databases.ddl`
• DBZ-8089 - After changing the column datatype from int to float the Debezium fails to round it and i get a null value for this field in the stream
• DBZ-8090 - Documentation for signals provides incorrect data-collection format for some connectors
• DBZ-8092 - MySQL and MariaDB keyword YES cannot be parsed as a column name
• DBZ-8099 - Update third-party LICENSE with LGPL forMariaDB Connector/J
• DBZ-8104 - Converters documentation uses incorrect examples
• DBZ-8107 - Remove reference to`additional condition` signal parameter from ad hoc snapshots doc
• DBZ-8113 - Primary Key Update/ Snapshot Race Condition
• DBZ-8117 - Docs: connect-log4j.properties instead log4j.properties
• DBZ-8119 - Recalculating mining range upper bounds causes getScnFromTimestamp to fail
• DBZ-8124 - Update Oracle connector doc to describe options for restricting access permissions for the Debezium LogMiner user
• DBZ-8125 - ORA-00600: internal error code, arguments: [krvrdGetUID:2], [18446744073709551614], [], [], [], [], [], [], [], [], [], []
• DBZ-8130 - Unpredicatable ordering of table rows during insertion causing foreign key error
• DBZ-8134 - Support larger database.server.id values
• DBZ-8137 - Error registering JMX signal and notification for multi task SQLServer
• DBZ-8143 - Add LogMiner start mining session retry attempt counter to logs
• DBZ-8144 - Open redo thread consistency check can lead to ORA-01291 - missing logfile
• DBZ-8147 - SchemaOnlyRecoverySnapshotter not registered as an SPI service implementation
• DBZ-8149 - When stopping the Oracle rac node the Debezium server throws an expections - ORA-12514: Cannot connect to database and retries
• DBZ-8150 - Issue with Debezium Snapshot: DateTimeParseException with plugin pgoutput
• DBZ-8151 - JDBC connector validation fails when using record_value with no primary.key.fields
• DBZ-8162 - Taking RAC node offline and back online can lead to thread inconsistency
• DBZ-8168 - Postgres JSONB Fields are not supported with Reselect Post Processor
• DBZ-8177 - Avoid 3 second delay in Oracle when one of the RAC nodes is offline
• DBZ-8186 - Add MariaDB connector server distribution
• DBZ-8187 - NullPointerException (schemaUpdateCache is null) when restarting Oracle engine
• DBZ-8189 - Truncate byte buffer should return a new array
• DBZ-8198 - Exclude Oracle 23 VECSYS tablespace from capture
• DBZ-8209 - DDL statement couldn't be parsed: REVOKE IF EXISTS
• DBZ-8217 - Oracle TableSchemaBuilder provides wrong column name in error message
• DBZ-8220 - Implement separate source and sink connector sections in documentation navigation
• DBZ-8223 - Debezium does not restart automatically after throwing an ORA-00600 krvrdccs30 error
• DBZ-8224 - JDBC sink doesn't include fields as per documentation
• DBZ-8226 - Support MariaDB 11.4.3
• DBZ-8231 - Broken link to Streams doc about configuring logging
• DBZ-8232 - Document passthrough hibernate.* properties for the JDBC connector
• DBZ-8237 - Unbounded number of processing threads in async engine
• DBZ-8238 - Streaming metrics are stuck after an ad-hoc blocking snapshot
• DBZ-8240 - DDL statement couldn't be parsed with IF EXISTS
• DBZ-8248 - Support BLOB with EMPTY_BLOB() as default

CVEs

(none)

References

(none)