-
Bug
-
Resolution: Done
-
Major
-
2.7.3.Final
-
None
-
False
-
None
-
False
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?
2.7.3.Final
What is the connector configuration?
Relevant section:
transforms=convertTimezone
transforms.convertTimezone.type=io.debezium.transforms.TimezoneConverter
transforms.convertTimezone.converted.timezone=Australia/Sydney
transforms.convertTimezone.include.list=source:table_one:DATE_CREATED,table_one:LAST_UPDATED,table_two:CREATED_AT,table_two:UPDATED_AT
What is the captured database version and mode of deployment?
AWS MSK Connect
AWS Aurora MySQL 3.05.2 (MySQL 8.0.32)
What behavior do you expect?
For above config, I do not expect any columns from any table other than `table_one` or `table_two` to have TZ conversion applied.
What behavior do you see?
Any table that is not in the include list, will have all columns converted.
Do you see the same behaviour using the latest released Debezium version?
(Ideally, also verify with latest Alpha/Beta/CR version)
As using AWS MSK Connect, I am stuck on the 2.7.x line, but main also has the offending code.
Do you have the connector logs, ideally from start till finish?
(You might be asked later to provide DEBUG/TRACE level log)
For a column from another table not specified in the include list.
Skipping conversion for unsupported logical type: io.debezium.time.Date for field: FROM_DATE (io.debezium.transforms.TimezoneConverter:375)
How to reproduce the issue using our tutorial deployment?
Simply add include.list config for one table only, and send updates for a datetime or timestamp column on another table on source database.
See https://github.com/debezium/debezium/pull/6055 (main)
See https://github.com/debezium/debezium/pull/6051 (2.7.x)
Feature request or enhancement
For feature requests or enhancements, provide this information, please:
Which use case/requirement will be addressed by the proposed feature?
<Your answer>
Implementation ideas (optional)
<Your answer>