[
https://issues.apache.org/jira/browse/FLINK-35905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17869485#comment-17869485
]
xuyang commented on FLINK-35905:
--------------------------------
A short answer: No.
What is the reason and background for you to customize the exec node? Take
FileSourceScanExec as an example, it is also just an ExecTableSourceScan with a
connector parameter of file.
> Flink physical operator replacement support
> -------------------------------------------
>
> Key: FLINK-35905
> URL: https://issues.apache.org/jira/browse/FLINK-35905
> Project: Flink
> Issue Type: Bug
> Components: API / Scala, Table SQL / API
> Affects Versions: 1.15.0
> Environment: Flink1.15 and so on
> Reporter: Wang Qilong
> Priority: Major
>
> I have been studying the FlinkSQL source code recently and have learned about
> the execution process of FlinkSQL, which has led to a question:
> Does Flinksql provide some SPI implementations that support custom physical
> operators, such as customizing a FileSourceScanExec in the execPhysicalPlan
> layer?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
