[jira] [Updated] (IGNITE-18556) Sql. TypeSystem. Default implementation of getDefaultPrecision for FLOAT and DECIMAL returns the same value.

["Maksim Zhuravkov (Jira)" <ji...@apache.org>]

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

Maksim Zhuravkov updated IGNITE-18556:
--------------------------------------
    Summary: Sql. TypeSystem. Default implementation of getDefaultPrecision for FLOAT and DECIMAL returns the same value.  (was: Sql. TypeSystem. Default implementation of getDefaultPrecision FLOAT and DECIMAL returns the same value.)

> Sql. TypeSystem. Default implementation of getDefaultPrecision for FLOAT and DECIMAL returns the same value.
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-18556
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18556
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>    Affects Versions: 3.0.0-beta1
>            Reporter: Maksim Zhuravkov
>            Priority: Minor
>              Labels: calcite2-required, calcite3-required, ignite-3
>             Fix For: 3.0.0-beta1
>
>
> Default implementation of TypeSystem::getDefaultPrecision, provided by Calcite, returns the same value for FLOAT and DOUBLE types. Such behaviour causes TypeFactory::leastRestrictiveType to return different results for (FLOAT, DOUBLE) and (DOUBLE, FLOAT).
> We fixed getDefaultPrecision to return different values to resolve the problem with leastRestrictiveType in IGNITE-18163.
> 1) Investigate how this change affects behaviour of other operators.
> 2) Choose the appropriate value for default precision in IgniteTypeSystem for FLOAT and DOUBLE if necessary.
>  
>  
>  
>  



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