[
https://issues.apache.org/jira/browse/CALCITE-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16979533#comment-16979533
]
Julian Hyde commented on CALCITE-3339:
--------------------------------------
I've given it a little more thought. We can't possibly know the lexical
convention of the back-end (e.g. whether it uses back-tick or brackets to quote
identifiers) and so we can't replicate the behavior of the back-end parser.
Therefore the identifier should be in the lexical convention of the rest of the
enclosing SQL statement. And that includes the case-sensitivity of unquoted
identifiers.
That said, it doesn't matter very much. In v1 we should just do what is easiest
(with the fewest lines of code). We can revise later.
> 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)
