Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
This is an umbrella issue for adding support for timezones in the Table & SQL API.
Usually companies work with different timezones simultaneously. We could add support for the new time classes introduced with Java 8 and enable our scalar functions to also work with those (or some custom time class implementations like those from Calcite). We need a good design for this to address most of the problems users face related to timestamp and timezones.
It is up for discussion how to ship date, time, timestamp instances through the cluster.
Attachments
Issue Links
- is related to
-
FLINK-21617 FLIP-162: Consistent Flink SQL time function behavior
- Resolved
-
FLINK-8094 Support other types for ExistingField rowtime extractor
- Closed
- relates to
-
FLINK-10032 Rework SQL DATE_FORMAT function
- Resolved
-
FLINK-7735 Improve date/time handling in publically-facing Expressions
- Open
1.
|
JSON format does not convert timestamps correctly | Open | Unassigned |