docete opened a new pull request #10268: [Flink-14599][table-planner-blink] Support precision of TimestampType in blink planner URL: https://github.com/apache/flink/pull/10268 ## What is the purpose of the change Since FLINK-14080 introduced an internal representation(SqlTimestamp) of TimestampType with precision. This subtask will replace current long with SqlTimestamp, and let blink planner support precision of TimestampType. Note: - Tables defined by DDL is not supported in this PR since de/serializing DataTypes lost precision information. Would open another ticket to cover. ## Brief change log - 799b0be - fb77dd9 replace current long with SqlTimestamp, and Fix all existing failure cases - ad19558 introduces LegacyTimestampTypeInfo and LegacyLocalDateTimeTypeInfo to represent Types.SQL_TIMESTAMP and Types.LOCAL_DATE_TIME with precision - eb98df4 support precision of Timestamp type in table source - eb574ab support precision of Timestamp type for timestamp literals - 78cb2cf support precision of Timestamp type for builtin functions, such as extract/to_timestamp/cast ## Verifying this change This change is already covered by existing tests and added tests, such as *testHighPrecisionTimestamp* in *TemporalTypesTest. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (yes / **no**) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**) - The serializers: (yes / **no** / don't know) - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know) - The S3 file system connector: (yes / **no** / don't know) ## Documentation - Does this pull request introduce a new feature? (**yes** / no) - If yes, how is the feature documented? (not applicable / docs / **JavaDocs** / not documented)
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
