[
https://issues.apache.org/jira/browse/IGNITE-25556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Zhuravkov reassigned IGNITE-25556:
-----------------------------------------
Assignee: Maksim Zhuravkov
> Sql. Date/Time. Datetime format scanner
> ---------------------------------------
>
> Key: IGNITE-25556
> URL: https://issues.apache.org/jira/browse/IGNITE-25556
> Project: Ignite
> Issue Type: Improvement
> Components: sql ai3
> Reporter: Maksim Zhuravkov
> Assignee: Maksim Zhuravkov
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> FormatModels shipped with Apache Calcite can not be used to implement an SQL
> standard compliant parser. Consider the following code:
> {code:java}
> {
> List<FormatElement> elements =
> FormatModels.DEFAULT.parseNoCache("YYYY/MM/DD");
> System.err.println(elements);
> }
> {
> List<FormatElement> elements =
> FormatModels.DEFAULT.parseNoCache("RR/MM/DD");
> System.err.println(elements);
> }
> {
> List<FormatElement> elements =
> FormatModels.DEFAULT.parseNoCache("RR/MM/DD HH.MI");
> System.err.println(elements);
> }
> {code}
> Output:
> {code:java}
> [Y, Y, Y, Y, /, MM, /, D, D] - Expected: YYYY, / , MM , / DD
> [RR/, MM, /, D, D] - Expected: RR, MM, DD
> [RR/, MM, /, D, D, HH., MI] - Expected: RR, / , MM, / , DD, HH, . , MI
> {code}
> To resolve these issues, we have to implement a reader for a SQL datetime
> format.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
