[
https://issues.apache.org/jira/browse/CALCITE-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mihai Budiu resolved CALCITE-4918.
----------------------------------
Fix Version/s: 1.39.0
Resolution: Fixed
Fixed in
https://github.com/apache/calcite/commit/87485a90737ded1f7324870e761b94d78a41b5e0
Thank you to the reviewers [~nobigo],[~julianhyde][~caicancai], and to the
people who participated in the design.
More work needs to be done to take advantage of this feature, but the rest
should be easier.
> Add a VARIANT data type
> -----------------------
>
> Key: CALCITE-4918
> URL: https://issues.apache.org/jira/browse/CALCITE-4918
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Mihai Budiu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.39.0
>
>
> Add a VARIANT data type. It would be a tagged union, and allow values of
> multiple types to be stored, along with a type indicator so that the actual
> type of each value can be discerned.
> VARIANT is not in the SQL standard. I know of three databases that have a
> VARIANT type: MSSQL, Snowflake, Teradata. Calcite's VARIANT type will
> probably draw from all three; however, the goal is not full compliance with
> any of them, but useful functionality.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
