calcite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Feng Zhu (Jira)" <>
Subject [jira] [Created] (CALCITE-3414) Unify Expression'type cast and conversion as a robust one
Date Tue, 15 Oct 2019 11:48:00 GMT
Feng Zhu created CALCITE-3414:

             Summary: Unify Expression'type cast and conversion as a robust one
                 Key: CALCITE-3414
             Project: Calcite
          Issue Type: Bug
          Components: core
    Affects Versions: 1.21.0
            Reporter: Feng Zhu
            Assignee: Feng Zhu
         Attachments: RexToLixTranslator.png, TypeConversion.txt, Types.png

 Current now, there are two functions in calcite that can be used to cast/convert Expression
to a specific Type.
 *_Types.castIfNecessary_* and _*RexToLixTranslator.convert*_.

We make a deep investigation on their implementations and demonstrate them as below.





It can be seen that: 
 (1) They have a lot of overlaps; 
 (2) *_RexToLixTranslator.cast_* can cover more cases with tools like _SqlFunctions_ and etc.
 (3) Both of them have limitations and may generate incorrect code, which is listed in attachment(TypeConversion.txt).

Multiple choices usually bring confusion to developers and resulting to the misuse of them.

 For example, CALCITE-3245 exposes that Types.castIfNecessary cannot cast the Expression to

 Fixing the issue in *_Types.castIfNecessary_* directly seems to be not a good idea. 
 On one hand, it is not convenient to call _SqlFunctions_ in linq4j. One the other hand, it
will brings duplicate with _*RexToLixTranslator.cast*_. However, due to some unique logic
in _*Types.castIfNecessary*_, we cannot replace it as _*RexToLixTranslator.cast*_ neither.

Therefore, it is a good idea to integrate implementations into RexToLixTranslator.cast.

This message was sent by Atlassian Jira

View raw message