You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Konstantin Orlov (Jira)" <ji...@apache.org> on 2022/06/16 17:00:00 UTC

[jira] [Resolved] (IGNITE-16635) Sql. Introduce a separate enum for types supported by sql engine

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

Konstantin Orlov resolved IGNITE-16635.
---------------------------------------
    Resolution: Duplicate

> Sql. Introduce a separate enum for types supported by sql engine
> ----------------------------------------------------------------
>
>                 Key: IGNITE-16635
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16635
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Evgeny Stanilovsky
>            Assignee: Konstantin Orlov
>            Priority: Major
>              Labels: ignite-3
>
> For now, we're using the NativeType enum to create metadata for the columns in the result set. The problem here is that range of types supported by sql engine is much wider then the range types supported by storage (For example, interval types or collection types could be easilly supported by the sql engine). Hence, we need to decouple those types and introduce a separe enumeration for the types supported by the sql engine to use it for metadata creation.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)