-
Task
-
Resolution: Unresolved
-
Major
-
None
-
None
Embedded engine and Debezium Server currently re-use the OffsetBackingStore contract from Kafka Connect. That can be confusing when implementing a custom store. We therefore should provide a Debezium-specific contract instead. This also applies to the configuration properties used e.g. to configure the file based store with the embedded engine.
One specific requirement we should address is to avoid the usage of FQNs in the configuration. Instead, each implementation should expose a short name such as "file", "kafka", "dynamodb" etc. This would be retrieved from a store-specific factory which is discovered via the service loader. In the configuration then those short names woul be used by default, and the engine looks up the right implementation via the service loader. FQNs might still be supported as a fallback, should there be multiple implementations exposing the same short name.
- is depended on by
-
DBZ-6234 Separating Debezium from Kafka
- Open
- is related to
-
DBZ-1823 Provide a Debezium engine implementation based on framework classes
- Open
- relates to
-
DBZ-3621 Saving Debezium states to JDBC database
- Resolved
-
DBZ-7024 Create new implementation of DebeziumEngine
- Resolved
-
DBZ-1807 Support converters for embedded engine
- Closed
-
DBZ-3678 Provide Debezium-specific abstraction for offset storage SPI
- Closed
-
DBZ-4509 Save and load offsets in Redis
- Closed
-
DBZ-2292 Creating Offset Store using MySql database
- Open