[CALCITE-1947] Add time/timestamp with local time zone types to optimizer

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.14.0
• Component/s: core
• Assignee: Jesús Camacho Rodríguez
• Reporter: Jesús Camacho Rodríguez
• Created: 16/Aug/17 22:20
• Updated: 27/Feb/24 22:24
• Resolved: 05/Sep/17 21:56

Description

Implementation would be similar to PostgreSQL (the time/timestamp with timezone types do not store the timezone) and conversion from/to timezone-less types follows similar semantics.

https://www.postgresql.org/docs/9.6/static/functions-datetime.html

This would also allow us to integrate easily with Hive and Druid, which follow similar storage models/semantics for timestamp with timezone.

Follow-up work will be needed to introduce these new types in Avatica and extend Calcite SQL parser.

Issue Links

• blocks: CALCITE-1970 Release Calcite 1.14.0
• is related to: CALCITE-1784 SqlTypeName doesn't have timestamp with time zone type
• is related to: CALCITE-208 Support TIMESTAMP WITH TIME ZONE data type
• relates to: CALCITE-2107 Timezone not passed as part of granularity when passing TimeExtractionFunction to Druid
• relates to: CALCITE-4555 Invalid zero literal value is used for TIMESTAMP WITH LOCAL TIME ZONE type in RexBuilder
• relates to: CALCITE-3611 Introduce TIME/TIMESTAMP WITH TIME ZONE types