[
https://issues.apache.org/jira/browse/CALCITE-6820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925351#comment-17925351
]
Caican Cai edited comment on CALCITE-6820 at 2/9/25 8:40 AM:
-------------------------------------------------------------
[~xuzifu666] Thank you for raising this question
>From my point of view, I reject this jira case.
In the early days, Calcite had already adapted to Presto, and perhaps there was
not much difference between Presto and Trino at that time.
Although these are two different communities, I understand that the syntax of
Presto and Trino is still the same. Can you give an example to show that Presto
and Trino are different in terms of SQL structure? If it's just some function
type differences, I understand that it is not necessary
was (Author: JIRAUSER302115):
[~xuzifu666] Thank you for raising this question
>From my point of view, I reject this jira case.
In the early days, Calcite had already adapted to Presto, and perhaps there was
not much difference between Presto and Trino at that time.
Although these are two different communities, I understand that the syntax of
Presto and Trino is still the same. Can you give an example to show that Presto
and Trino are different in terms of SQL structure? If it is some functions, I
understand that it is not necessary
> Trino dialect implementation
> ----------------------------
>
> Key: CALCITE-6820
> URL: https://issues.apache.org/jira/browse/CALCITE-6820
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.38.0
> Reporter: Yu Xu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.39.0
>
>
> Currently calcite not support dialect sql for trino, need to support it.
> trino sql: https://prestodb.io/docs/current/release/release-0.142.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
