[
https://issues.apache.org/jira/browse/FLINK-23136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17382861#comment-17382861
]
Eduardo Winpenny Tejedor commented on FLINK-23136:
--------------------------------------------------
This one seems pretty straightforward, I could take it if it's available
> 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
>
> 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)
