You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "xzh_dz (Jira)" <ji...@apache.org> on 2020/11/18 08:03:00 UTC
[jira] [Commented] (CALCITE-4406) SqlTableRef OPERATOR should
create a SqlTableRef as the call
[ https://issues.apache.org/jira/browse/CALCITE-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17234346#comment-17234346 ]
xzh_dz commented on CALCITE-4406:
---------------------------------
[~danny0405]
I tried to test the unit case, but after accessing SqlShuttle, it is still a SqlTableRef.
!image-2020-11-18-16-01-55-504.png|width=399,height=231!
> SqlTableRef OPERATOR should create a SqlTableRef as the call
> ------------------------------------------------------------
>
> Key: CALCITE-4406
> URL: https://issues.apache.org/jira/browse/CALCITE-4406
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.26.0
> Reporter: Danny Chen
> Assignee: Danny Chen
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.27.0
>
> Attachments: image-2020-11-18-16-01-55-504.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{SqlTableRef}} OPERATOR should create a SqlTableRef as the call, so that after substitution of {{SqlShuttle}}, it is still a {{SqlTableRef}} instead of {{SqlBasicCall}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)