[
https://issues.apache.org/jira/browse/CALCITE-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16807387#comment-16807387
]
Julian Hyde commented on CALCITE-1581:
--------------------------------------
bq. However,It cannot pass the validation in SqlValidator.So I have to rewrite
it before the validation start.
Let's challenge that assumption. How hard would it be to modify the validator
so that it works correctly on the sugared syntax? I guess you would have to
modify the code that deduces the row type returned from a sub-query. Probably a
few other things, but not too many. And the validator would give better error
messages.
> UDTF like in hive
> -----------------
>
> Key: CALCITE-1581
> URL: https://issues.apache.org/jira/browse/CALCITE-1581
> Project: Calcite
> Issue Type: New Feature
> Reporter: Xiaoyong Deng
> Assignee: Sihua Zhou
> Priority: Major
> Labels: pull-request-available, udtf
> Fix For: 1.20.0
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> Support one row in and multi-column/multi-row out(one-to-many mapping), just
> like udtf in hive.
> The query would like this:
> {code}
> select
> func(c0, c1) as (f0, f1, f2)
> from table_name;
> {code}
> c0 and c1 are 'table_name' columns. f0, f1 and f2 are new generated columns.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
