[
https://issues.apache.org/jira/browse/CALCITE-6426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17854558#comment-17854558
]
Julian Hyde edited comment on CALCITE-6426 at 9/24/24 7:44 PM:
---------------------------------------------------------------
Fixed in
[1079bce|https://github.com/apache/calcite/commit/1079bcea97ce48973255e05ce600998edb1e7b4c].
Thanks for your contribution [~fanluoo] and Thanks for the review [~mbudiu]
[~caicancai] and [~eveywu] .
was (Author: nobigo):
Fixed in [db1e7b4c|http://example.com/]. Thanks for your contribution
[~fanluoo] and Thanks for the review [~mbudiu] [~caicancai] and [~eveywu] .
> Invalid unparse for INT and BIGINT in StarRocksDialect
> ------------------------------------------------------
>
> Key: CALCITE-6426
> URL: https://issues.apache.org/jira/browse/CALCITE-6426
> Project: Calcite
> Issue Type: Bug
> Affects Versions: 1.37.0
> Reporter: fanluo
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.38.0
>
> Attachments: image-2024-06-03-19-57-22-686.png
>
>
> When performing starrocks dialect conversion for cast (xxx as int) and cast
> (xxx as bigint), it defaults to using MySQL dialect，like this:
> !image-2024-06-03-19-57-22-686.png|width=839,height=123!
> while starlocks does not explicitly declare support for the signed data type.
> If conversion is performed according to the MySQL dialect by default, the
> execution result will exceed expectations when the data value exceeds the
> range [-2147483648,2147483647]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
