[jira] [Comment Edited] (CALCITE-3339) DESCRIPTOR as a SQL operator in SqlStdOperatorTable

["Rui Wang (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CALCITE-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927988#comment-16927988 ] 

Rui Wang edited comment on CALCITE-3339 at 9/11/19 9:00 PM:
------------------------------------------------------------

I also believe [~kenn] has some knowledge on DESCRIPTOR.


From something written by Kenneth somewhere before, DESCRIPTOR is from SQL2016 standard ISO/IEC TR 19075-7:2017(E) on polymorphic table functions.

I will also try to read it to understand the exact definition.  


was (Author: amaliujia):
I also believe [~kenn] has some knowledge on DESCRIPTOR(which I heard is from SQL standard).


From something written by Kenneth somewhere before, DESCRIPTOR is from SQL2016 standard ISO/IEC TR 19075-7:2017(E) on polymorphic table functions.

I will also try to read it to understand the exact definition.  

> 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)