[
https://issues.apache.org/jira/browse/CALCITE-7819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mihai Budiu resolved CALCITE-7819.
----------------------------------
Fix Version/s: 1.43.0
Assignee: DongShengHe
Resolution: Fixed
Fixed in
[https://github.com/apache/calcite/commit/36c4df140a7bcd30e67c8569b73f467e72a75381]
Thank you for the reviews [~vlsi] [~zzwqqq] [~krooswu]
> RelMdTableReferences returns null for TableFunctionScan with relational inputs
> ------------------------------------------------------------------------------
>
> Key: CALCITE-7819
> URL: https://issues.apache.org/jira/browse/CALCITE-7819
> Project: Calcite
> Issue Type: Bug
> Reporter: DongShengHe
> Assignee: DongShengHe
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.43.0
>
>
> RelMetadataQuery#getTableReferences returns null when the relational
> plan contains a TableFunctionScan, even when the TableFunctionScan has
> a relational input containing a TableScan.
> For example, the TUMBLE window table function produces:
>
> {code:java}
> LogicalProject
> LogicalTableFunctionScan
> LogicalProject
> LogicalTableScan(table=[[hr, employee]]){code}
>
> Calling:
> mq.getTableReferences(root)
> returns null because RelMdTableReferences does not provide an overload
> for TableFunctionScan and falls back to the RelNode catch-all handler.
> Expected result:
> {code:java}
> [hr, employee].#0 {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)