[
https://issues.apache.org/jira/browse/BEAM-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17131754#comment-17131754
]
Beam JIRA Bot commented on BEAM-3633:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> [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: P2
> Labels: stale-P2
>
> 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)
