[FLINK-14645] Data types defined in DDL will lose precision and nullability when converting to properties

• Type: Sub-task
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.10.0
• Component/s: Table SQL / API
• Labels: pull-request-available

Release Note

The TableSchema derived from properties now bridges to the default conversion class, i.e. LocalDateTime/LocalDate/LocalTime, instead of java.sql.Timestamp/Date/Time. All the connectors consume/produce the java.sql.Timestamp/Date/Time classes should adapt to the new conversion classes.

• Assignee: Jark Wu
• Reporter: Jark Wu
• Created: 07/Nov/19 04:33
• Updated: 18/Sep/22 15:12
• Resolved: 07/Dec/19 12:31

Description

Currently, data types defined in DDL will be converted to TypeInformation and use TypeStringUtils to serialize/deserialize which will lose the precision and nullablitiy information.

We can use LogicalType#asSerializableString and LogicalTypeParser to serialize/deserialize data types which keeps all the information. But we need to figure out how to keep compability with previous versions.

Issue Links

• blocks: FLINK-14925 the return type of TO_TIMESTAMP should be Timestamp(9) instead of Timestamp(3)
• duplicates: FLINK-14987 JDBCTableSource can't support DataTypes.DECIMAL
• is related to: FLINK-17091 AvroRow(De)SerializationSchema doesn't support new Timestamp conversion classes
• relates to: FLINK-14599 Support precision of TimestampType in blink planner
• links to: GitHub Pull Request #10403