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

Allow special characters in signal table name

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 2.6.0.Beta1
    • 2.6.0.Alpha2
    • core-library
    • None
    • False
    • None
    • False
    • Low

      When using the source signal channel, the CommonConnectorConfig.isSignalDataCollection() method compares the data collection that a change is from with the string literal passed as the signal.data.collection.

       

      This means signalingDataCollection.equals(dataCollectionId.identifier()) will always return false if any character escaping is used for the signal table config value, even if it can correctly be parsed into database.schema.table using the TableIdParser.

       

      My suggested fix here is to use a parsed signal table TableId object to compare with the dataCollectionId.identifier() value instead of the config string value.

              ywyuewei Harvey Yue (Inactive)
              bmotts Ben Mottershead (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: