-
Task
-
Resolution: Done
-
Major
-
None
-
False
-
False
-
Once we have the multi-partition mode (DBZ-2975), there's essentially two working modes for connectors. I think we could converge on the multi-partition mode eventually, as single partition essentially just is a special case of that: multi-partition with exactly one partition. I.e. we could remove the bespoke single partition mode, e.g. in terms of metrics, etc.
The following things should happen:
- Remove methods io.debezium.pipeline.spi.Offsets.getTheOnlyPartition() and getTheOnlyOffset()
- In regards to metrics (see discussion in PR #2946 for more details):
- Keep the connector type as a part of the root MBean name, allowing to set up dashboards for particular connector types
- Remove superfluous intermediary folder node "connector-metrics"
- Pull up the queue metrics to a task-scoped MBean, reducing the duplication between snapshotting and streaming metrics
- Metrics docs will need updating as per the final structure we converge on; currently, multi-partition metrics aren't documented yet
- causes
-
DBZ-5845 SQL Server Connector cannot be upgraded to 2.0
- Pull Request Sent
- relates to
-
DBZ-4808 Multi-partition streaming metrics expose CapturedTables from all partitions
- Open
-
DBZ-4478 Partition-scoped metrics for the SQL Server connector
- Closed
-
DBZ-4809 Add task id and partition to the logging context for multi-partition connectors
- Closed
-
DBZ-4799 Incremental snapshotting in multi-partition mode
- Open