[IGNITE-21567] Sql. Conversion from TIMESTAMP to TIMESTAMP_WITH_LOCAL_TIME_ZONE trims millis

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: sql
• Labels: ignite-3
• Assignee: Pavel Pereslegin
• Reporter: Pavel Pereslegin
• Created: 20/Feb/24 07:50
• Updated: 03/Apr/24 09:49
• Resolved: 03/Apr/24 09:49

Description

Conversion from TIMESTAMP to TIMESTAMP_WITH_LOCAL_TIME_ZONE loses precision

String ts  = "1992-01-18 02:30:00.123";
assertQuery(format("select TIMESTAMP '{}'::TIMESTAMP WITH LOCAL TIME ZONE ", ts))
        .returns(LocalDateTime.parse(ts, DateTimeFormatter.ofPattern("yyyy-MM-dd HH:mm:ss.SSS"))
                .atZone(ZoneId.systemDefault())
                .toInstant())
        .check();

// Expected: 1992-01-17T22:30:00.123Z <class java.time.Instant>
// Actual:   1992-01-17T22:30:00Z <class java.time.Instant>

Issue Links

• blocks: IGNITE-19274 Sql. Jdbc client. Support TIMESTAMP WITH LOCAL TIME ZONE type
• is caused by: IGNITE-21551 Sql. Enable TIMESTAMP_WITH_LOCAL_TIME_ZONE data type
• is related to: IGNITE-15622 Calcite. TIME and TIMESTAMP types are trim milliseconds.
• links to: GitHub Pull Request #3513