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

history records were filtered by white/black list before storing to kafka db history topic

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Major
    • None
    • None
    • None
    • None

    Description

      History records were filtered by white/black list before storing to kafka db history topic, which will cause some debezium connector config modification not to take effect.

      As we know, kafka connect will restart debezium connector when it detected config modification, and debezium will restore `tables` from db history topic.
      Then we will found the extended table white list didn't take effect, since the related table meta was filtered before.

      Can you help resolve it?

      Attachments

        Issue Links

          duplicates

          Feature Request - Feature requests from customers and/or users DBZ-175 table.whitelist option update for an existing connector doesn't work

          • 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
              tminglei Minglei Tu (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: