You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jark Wu (JIRA)" <ji...@apache.org> on 2019/07/23 06:46:00 UTC
[jira] [Resolved] (FLINK-13075) Project pushdown rule shouldn't
require the TableSource return a modified schema in blink planner
[ https://issues.apache.org/jira/browse/FLINK-13075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jark Wu resolved FLINK-13075.
-----------------------------
Resolution: Fixed
Fixed in 1.10.0: bd351943ff93d3eb1324820dc858d3e9883427e8
Fixed in 1.9.0: e1e62e3629a8b5055dbab70709b9790cda33fa30
> Project pushdown rule shouldn't require the TableSource return a modified schema in blink planner
> -------------------------------------------------------------------------------------------------
>
> Key: FLINK-13075
> URL: https://issues.apache.org/jira/browse/FLINK-13075
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Reporter: Jark Wu
> Assignee: Caizhi Weng
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.9.0, 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> As the javadoc of {{org.apache.flink.table.sources.ProjectableTableSource#projectFields}} said, the table schema of the TableSource copy must not be modified by this method. However, {{PushProjectIntoTableSourceScanRule}} in blink planner requires the returning a table source with the modified table schema. This conflict with the javadoc and result in the TableSource works for flink planner can't work for blink planner.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)