You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Shuo Cheng (Jira)" <ji...@apache.org> on 2021/10/11 10:12:00 UTC
[jira] [Closed] (FLINK-23136) Make `addSource` method with specific
boundedness in `StreamExecutionEnvironment` public
[ https://issues.apache.org/jira/browse/FLINK-23136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shuo Cheng closed FLINK-23136.
------------------------------
Fix Version/s: 1.14.0
Resolution: Duplicate
> Make `addSource` method with specific boundedness in `StreamExecutionEnvironment` public
> ----------------------------------------------------------------------------------------
>
> Key: FLINK-23136
> URL: https://issues.apache.org/jira/browse/FLINK-23136
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration
> Reporter: Shuo Cheng
> Priority: Major
> Fix For: 1.14.0
>
>
> Currently, when we add a source function by calling `addSource(sourceFunction, name, typeinfo)` of `StreamExecutionEnvironment` , the source is set to CONTINUOUS_UNBOUNDED by default (Flink-19392). However, for table api / sql job, the batch source is also created by calling the above `addSource` method, which is thus set to CONTINUOUS_UNBOUNDED and produces unexpected behavior. I think StreamExecutionEnvironment should expose an `addSource` method to allow users to pass a boundedness parameter.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)