[ https://issues.apache.org/jira/browse/CALCITE-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16936315#comment-16936315 ]
Julian Hyde commented on CALCITE-3340: -------------------------------------- Built-in operators -- especially those referenced by the parser -- are not looked up by name. For instance, the parser creates a call to SqlStdOperatorTable.SUBSTRING, not a call to SqlIdentifier("SUBSTRING") that is later resolved by the validator. Do they need to have the same SqlKind value? It's worth questioning that assumption. > Make TUMBLE be accepted as an operand for "FROM TABLE()" in validator > --------------------------------------------------------------------- > > Key: CALCITE-3340 > URL: https://issues.apache.org/jira/browse/CALCITE-3340 > Project: Calcite > Issue Type: Sub-task > Reporter: Rui Wang > Assignee: Rui Wang > Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > The goal of this JIRA is to generate a logical plan for the following query: > {code:java} > SELECT * > FROM TABLE(TUMBLE( > TABLE ORDERS, > INTERVAL '10' MINUTE)) > {code} > This SQL query does not have DESCRIPTOR included, which is being tracked and > discussed by CALCITE-3339. > I expect we should generate a logical plan from this query that is similar to > the following: > {code:java} > LogicalProject(ROWTIME=[$0], ID=[$1], PRODUCT=[$2], UNITS=[$3], wstart=[$4], > wend=[$5]) > LogicalTableFunctionScan(invocation=[TUMBLE($3, 60000:INTERVAL MINUTE)], > rowType=[RecordType(TIMESTAMP(0) ROWTIME, INTEGER ID, VARCHAR(10) PRODUCT, > INTEGER UNITS, TIMESTAMP(0) wstart, TIMESTAMP(0) wend)]) > LogicalProject(ROWTIME=[$0], ID=[$1], PRODUCT=[$2], UNITS=[$3]) > LogicalTableScan(table=[[ORINOCO, ORDERS]]) > {code} -- This message was sent by Atlassian Jira (v8.3.4#803005)