You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2022/12/12 06:36:00 UTC

[jira] [Updated] (IGNITE-17599) Calcite engine. Support LocalDate/LocalTime types

     [ https://issues.apache.org/jira/browse/IGNITE-17599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Plekhanov updated IGNITE-17599:
---------------------------------------
    Labels: calcite calcite3-required ise  (was: calcite2-required calcite3-required ise)

> Calcite engine. Support LocalDate/LocalTime types
> -------------------------------------------------
>
>                 Key: IGNITE-17599
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17599
>             Project: Ignite
>          Issue Type: Improvement
>    Affects Versions: 2.14
>            Reporter: Aleksey Plekhanov
>            Assignee: Ivan Daschinsky
>            Priority: Major
>              Labels: calcite, calcite3-required, ise
>             Fix For: 2.15
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> H2-based engine works with LocalData/LocalTime types as java.sql.Data/java.sql.Time types. To check if value with LocalDate type can be inserted to descriptor with type java.sql.Data some logic from \{{IgniteH2Indexing.isConvertibleToColumnType}} is used. If Calcite engine used without ignite-indexing this logic is unavailable.
> We should:
>  # Provide an ability to work in Calcite-based engine with LocalDate/LocalTime type in the same way as java.sql.Data/java.sql.Time types.
>  # Move \{{IgniteH2Indexing.isConvertibleToColumnType}} logic to the core module (perhaps delegating this call from the core to the QueryEngine instance)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)