[
https://issues.apache.org/jira/browse/CALCITE-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16979515#comment-16979515
]
Rui Wang commented on CALCITE-3339:
-----------------------------------
I replied to the thread in dev@ but still copy that response to this JIRA to
make [~julianhyde] can continue discussion on his preferred way. I monitor both
email and JIRA so I am ok with either way to continue our discussion.
Copied response from the email:
{code:java}
I didn't find such discussion in the SQL standard (maybe I have missed
something).
My current thought is not to convert "rowtime" to upper-case is the best:
1. for those not column name case-sensitive database, it works.
2. for those case-sensitive database, assume users are aware of their sources
that are case-sensitive, I think their intention to use descriptor will
consider that factor. Converting column names to upper-case causes confusion.
-Rui
{code}
> 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
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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.4#803005)
