You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Konstantin Knauf (Jira)" <ji...@apache.org> on 2021/07/29 07:38:14 UTC

[jira] [Updated] (FLINK-2579) StreamExecutionEnvironment & ExecutionEnvironment do not share interface but have a lot in common

     [ https://issues.apache.org/jira/browse/FLINK-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Knauf updated FLINK-2579:
------------------------------------
      Labels:   (was: auto-closed)
    Priority: Not a Priority  (was: Minor)

> StreamExecutionEnvironment & ExecutionEnvironment do not share interface but have a lot in common
> -------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-2579
>                 URL: https://issues.apache.org/jira/browse/FLINK-2579
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / DataSet, API / DataStream
>            Reporter: Arnaud Linz
>            Priority: Not a Priority
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Both classes org.apache.flink.streaming.api.environment.StreamExecutionEnvironment and org.apache.flink.api.java.ExecutionEnvironment have a lot in common (same methods for kryo registration, fromCollection, etc) but are not related by a java contract.
> That leads to annoying differences, for instance : StreamExecutionEnvironment.setParallelism() returns 'this' where as ExecutionEnvironment.setParallelism() has not return value.
> They have specificities, but maybe they should both implement a common Interface to make sure that the common signatures are coherent?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)