Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-4808

Multi-partition streaming metrics expose CapturedTables from all partitions

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • 1.9-backlog
    • 1.9.0.Beta1
    • sqlserver-connector
    • None
    • False
    • False
    • Hide
      1. Use the steps to run a connector configured to capture two databases documented in #3261.
      2. Before starting the connector on step 4, replace the value of tasks.max from 2 to 1 to have a single task capture both databases.
      3. Observe the JMX metrics exposed by the connector. Both the testDB1 and testDB2 streaming metrics will contain the testDB1.dbo.producs and testDB2.dbo.customers as their CapturedTables. See the attached screenshot.
      Show
      Use the steps to run a connector configured to capture two databases documented in #3261 . Before starting the connector on step 4, replace the value of tasks.max from 2 to 1 to have a single task capture both databases. Observe the JMX metrics exposed by the connector. Both the testDB1 and testDB2 streaming metrics will contain the testDB1.dbo.producs and testDB2.dbo.customers as their CapturedTables . See the attached screenshot.

    Description

      While the expected behavior is known as not yet implemented, it may be considered a bug from the end-user's perspective.

      If a connector task captures more than one database, the CapturedTables attribute of the streaming metrics of each partition will contain the table names of all tasks instead of containing only the names that correspond to the partition of the metrics.

      The reason is that the partition-scoped metrics still expose the value returned by taskContext.capturedDataCollections() as is. See more details in #3261 (comment).

      Attachments

        Issue Links

          is blocked by

          Task - Represents a small unit of work that is not end-user facing. DBZ-5470 Remove the dependency of JdbcConnection on DatabaseSchema

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is related to

          Task - Represents a small unit of work that is not end-user facing. DBZ-4726 Remove "single partition" mode

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              Unassigned Unassigned
              sergeimorozov Sergei Morozov
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: