You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Danny Chen (Jira)" <ji...@apache.org> on 2019/12/06 01:11:00 UTC
[jira] [Resolved] (CALCITE-3550) Make SqlTypeAssignmentRules
conversion mapping pluggable
[ https://issues.apache.org/jira/browse/CALCITE-3550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Danny Chen resolved CALCITE-3550.
---------------------------------
Assignee: Danny Chen
Resolution: Fixed
Fixed in [ccdc169|https://github.com/apache/calcite/commit/ccdc169080a7f68066c317db67729b7df81662f6] !
> Make SqlTypeAssignmentRules conversion mapping pluggable
> --------------------------------------------------------
>
> Key: CALCITE-3550
> URL: https://issues.apache.org/jira/browse/CALCITE-3550
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.21.0
> Reporter: Danny Chen
> Assignee: Danny Chen
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.22.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In CALCITE-2302, we introduce implicit type coercion for Calcite builtin conversion behaviors, we also expand the conversion matrix to support more type conversion compared to the old matrix [1], that means, we implement a conversion matrix of our Calcite style.
> As a library of other sql engines, i think we should make the conversion matrix pluggable, so that each engine can customize if the conversion is valid from a type to another.
> We have made the TypeCoercion pluggable/customizable, so if this matrix is also pluggable, then, the whole conversion behavior can be customized.
> That would give the type conversion of Calcite a pretty good flexibility.
> [1] https://docs.google.com/spreadsheets/d/1GhleX5h5W8-kJKh7NMJ4vtoE78pwfaZRJl88ULX_MgU/edit?usp=sharing
--
This message was sent by Atlassian Jira
(v8.3.4#803005)