You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Stamatis Zampetakis (JIRA)" <ji...@apache.org> on 2019/07/25 17:45:00 UTC

[jira] [Resolved] (CALCITE-1975) Allow SqlTypeFactoryImpl#leastRestrictive support methods to be overridden

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

Stamatis Zampetakis resolved CALCITE-1975.
------------------------------------------
       Resolution: Won't Fix
    Fix Version/s: 1.21.0

It appears from the discussion that overriding these support methods is not desirable. 

Plus the benefit would not be huge since the public leastRestrictive method is already overridable so I guess we don't plan to fix this. 

I am marking this as resolved.

> Allow SqlTypeFactoryImpl#leastRestrictive support methods to be overridden
> --------------------------------------------------------------------------
>
>                 Key: CALCITE-1975
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1975
>             Project: Calcite
>          Issue Type: Improvement
>          Components: core
>            Reporter: Ruidong Li
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.21.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Some other project which use calcite may have it's own logic in {{leastRestrictiveByCast}} and {{leastRestrictiveSqlType}}. For example, Flink's {{ANY}} SqlType differs from calcite's , it'e better to implementing it's own logic.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)