zjjiang created FLINK-36806:
-------------------------------

             Summary: Support for synchronization between timestamp fields with 
and without time zones to avoid time offsets
                 Key: FLINK-36806
                 URL: https://issues.apache.org/jira/browse/FLINK-36806
             Project: Flink
          Issue Type: Improvement
          Components: Flink CDC
    Affects Versions: cdc-3.2.1, cdc-3.1.0, cdc-3.3.0
            Reporter: zjjiang
         Attachments: image-2024-11-27-16-23-22-995.png

Currently, FlinkCDC can correctly synchronize the same time type (where the 
type indicates whether the time zone is included or not), but time offsets can 
occur when synchronizing between fields of different time types. For example, 
when synchronizing the field DATETIME (without time zone) in MySQL to the field 
TIMESTAMPTZ (with time zone) in Iceberg, there is an 8-hour offset after 
synchronization when the time in mysql represents Beijing time.

This kind of synchronization in different time type fields is very common in 
practical applications, however, the time offset will be very troublesome for 
business. Therefore, Flink CDC's support for the conversion of different time 
types will avoid the time offset and help improve the data consistency and 
accuracy of synchronization.

 

!image-2024-11-27-16-23-22-995.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to