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

Posted to issues@beam.apache.org by "Andrew Pilloud (Jira)" <ji...@apache.org> on 2021/05/11 01:16:00 UTC

[jira] [Updated] (BEAM-3633) [SQL] Reduce usage of Calcite's SqlTypeName

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

Andrew Pilloud updated BEAM-3633:
---------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Open)

This appears to have been cleaned up.

> [SQL] Reduce usage of Calcite's SqlTypeName
> -------------------------------------------
>
>                 Key: BEAM-3633
>                 URL: https://issues.apache.org/jira/browse/BEAM-3633
>             Project: Beam
>          Issue Type: Improvement
>          Components: dsl-sql
>            Reporter: Anton Kedin
>            Priority: P3
>
> We still use Calcite's SqlTypeName as type of BeamSqlExpression and few other places. This leaks implementation details, and complicates logic, we now have to keep two-way mapping between Beam coders and Calcite's type names.
> Feels like we can noticeably simplify the type conversion logic in few places by updating BeamSqlExpression and similar classes to use Beam's SqlTypeCoders instead of SqlTypeName.
> Good place to start is from usages of CalciteUtils.toCalciteType(Coder).
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)