You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Such columns are converted into an equivalent io.debezium.time.ZonedTimestamp in UTC based on the server (or session’s) current time zone. The time zone will be queried from the server by default.
However, the queried time zone may be an ambiguous one (allowed by MySQL). For example, "CST" can mean China Standard Time, Cuba Standard Time and Central Standard Time (ref). This leads to wrong instant values.
Describe the solution you'd like
Rather than relying on the user to use unambiguous time zone names in their upstream MySQL, we could set the session timezone when our connector node (debezium) connects to MySQL.
Is your feature request related to a problem? Please describe.
https://debezium.io/documentation/reference/2.4/connectors/mysql.html#mysql-temporal-types
However, the queried time zone may be an ambiguous one (allowed by MySQL). For example, "CST" can mean China Standard Time, Cuba Standard Time and Central Standard Time (ref). This leads to wrong instant values.
Describe the solution you'd like
Rather than relying on the user to use unambiguous time zone names in their upstream MySQL, we could set the session timezone when our connector node (debezium) connects to MySQL.
https://debezium.io/documentation/faq/#why_do_change_event_values_for_mysql_timestamp_columns_differ_between_snapshotting_and_streaming
https://dev.mysql.com/doc/connector-j/8.1/en/connector-j-connp-props-datetime-types-processing.html
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: