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

Unable to specify column or table include list if name contains a backslash \




      In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

      Bug report

      For bug reports, provide this information, please:

      What Debezium connector do you use and what version?


      What is the connector configuration?

      Debezium engine (tested with mysql and postgres)

      What is the captured database version and mode of depoyment?

      Tested with local mysql, postgres

      What behaviour do you expect?

      When a column name or a table name contains a backslash character (e.g "sales\APAC")

      specifying table.include.name or column.include.name make it impossible to read the table or column.

      I cannot find a way to escape a backslash. All other characters I tested with work when escaped, including emojis, different writing systems, crazy unicode characters and also characters which have a meaning for regex such as + * , ().

      for example. Starting the debezlum engine with with escaping.

      table.include.list = \\Qpublic.id_and_name\\E,\\Qpublic.starships\\\\E"}}

      should find the tables "public.id_and_name" and also "public.starships\" (note the backslash after starships).

      In effect only id_and_name table is found.

      What behaviour do you see?

      if using the column and table include/exclude lists with names containing a backslash \, debzium fails to match.

      Do you see the same behaviour using the latest relesead Debezium version?

      (Ideally, also verify with latest Alpha/Beta/CR version)

      <Your answer>

      Do you have the connector logs, ideally from start till finish?

      Didn't check with 2.x

      How to reproduce the issue using our tutorial deployment?

      Create a table whose name contain a "\" and try to include it it table.include.list prop.

      Feature request or enhancement

      For feature requests or enhancements, provide this information, please:

      Which use case/requirement will be addressed by the proposed feature?

      Since backslash is a legal character for postgres, MySQL 

      Implementation ideas (optional)

      I assume that regex matching is handling backslash differently than other characters.


        Issue Links



              vjuranek@redhat.com Vojtech Juranek
              rodirz Rodi Reich Zilberman (Inactive)
              0 Vote for this issue
              4 Start watching this issue