[ 
https://issues.apache.org/jira/browse/CALCITE-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rui Wang updated CALCITE-3339:
------------------------------
    Description: 
For query:

SELECT * 
FROM TABLE(TUMBLE_TVF(
        TABLE ORDERS,
        DESCRIPTOR(ROWTIME), 
        INTERVAL '10' MINUTE))

TABLE ORDERS is converted to SqlPrefixOperator, but DESCRIPTOR(ROWTIME) has no 
mapping in SqlStdOperatorTable. 

There are two options:
1. There is a SqlColumnListConstructor which serves the same(similar) purpose 
to specific a list of column. 
2. We create a new operator for DESCRIPTOR.

Reuse existing code is always good so we can start from option one and see if 
it works.



  was:
For query:

SELECT * 
FROM TABLE(TUMBLE_TVF(
        \tTABLE ORDERS,
        \tDESCRIPTOR(ROWTIME), 
        \tINTERVAL '10' MINUTE))

TABLE ORDERS is converted to SqlPrefixOperator, but DESCRIPTOR(ROWTIME) has no 
mapping in SqlStdOperatorTable. 

There are two options:
1. There is a SqlColumnListConstructor which serves the same(similar) purpose 
to specific a list of column. 
2. We create a new operator for DESCRIPTOR.

Reuse existing code is always good so we can start from option one and see if 
it works.




> DESCRIPTOR as a SQL operator in SqlStdOperatorTable
> ---------------------------------------------------
>
>                 Key: CALCITE-3339
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3339
>             Project: Calcite
>          Issue Type: Sub-task
>            Reporter: Rui Wang
>            Assignee: Rui Wang
>            Priority: Major
>
> For query:
> SELECT * 
> FROM TABLE(TUMBLE_TVF(
>         TABLE ORDERS,
>         DESCRIPTOR(ROWTIME), 
>         INTERVAL '10' MINUTE))
> TABLE ORDERS is converted to SqlPrefixOperator, but DESCRIPTOR(ROWTIME) has 
> no mapping in SqlStdOperatorTable. 
> There are two options:
> 1. There is a SqlColumnListConstructor which serves the same(similar) purpose 
> to specific a list of column. 
> 2. We create a new operator for DESCRIPTOR.
> Reuse existing code is always good so we can start from option one and see if 
> it works.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to