[
https://issues.apache.org/jira/browse/CALCITE-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17937322#comment-17937322
]
XiangYang commented on CALCITE-5279:
------------------------------------
Hi [~julianhyde] , I'm interesting in this issue and the related
https://issues.apache.org/jira/browse/CALCITE-4471.
Because not only one SqlDialect has this problem, StarrocksSqlDialect also
doesn't support the asymmetric keyword, I wonder the fix method which implement
in each SqlDialect may cause duplicated codes. and the fix method of pr
[https://github.com/apache/calcite/pull/2328/] maybe better?
I notice you mentioned " rewrite by creating a {{SqlCall}} that does not have
{{{}ASYMMETRIC{}}}" which I can't understand, can you explain it inmore detail?
thanks.
> Firebolt does not support BETWEEN ASYMMETRIC
> --------------------------------------------
>
> Key: CALCITE-5279
> URL: https://issues.apache.org/jira/browse/CALCITE-5279
> Project: Calcite
> Issue Type: Bug
> Affects Versions: 1.31.0, 1.32.0
> Reporter: Aymeric Dispa
> Assignee: Aymeric Dispa
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The Asymmetric keyword is not supported by Firebolt.
> The dialect must be changed so that the keyword that is not supported is
> simply not included in the query
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
