[
https://issues.apache.org/jira/browse/CALCITE-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18024109#comment-18024109
]
Julian Hyde commented on CALCITE-7214:
--------------------------------------
The guideline is that if you propose a feature, you need to specify it. I don't
want to assume that Spark's TRY_CAST is identical to MSSQL's TRY_CAST just
because it has the same name. I want you to do the work. Once we have
discovered the differences, we can figure out whether we can live with them.
> Support TRY_CAST in spark dialect
> ---------------------------------
>
> Key: CALCITE-7214
> URL: https://issues.apache.org/jira/browse/CALCITE-7214
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.40.0
> Reporter: Rafael Acevedo
> Priority: Minor
>
> In Spark, try_cast is supported (refs:
> [[1|https://github.com/apache/spark/commit/3951e3371a83578a81474ed99fb50d59f27aac62]]
>
> [[2|https://github.com/apache/spark/blob/46ac78ea367cfa9a7acc04482770aaca33f5a575/sql/core/src/test/resources/sql-tests/inputs/try_cast.sql]]
> [3]) but it's not enabled in the spark dialect, only in MSSQL.
> Is there any reason why it's not enabled in the spark dialect? I can work on
> a PR if enabling it makes sense.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
