[
https://issues.apache.org/jira/browse/FLINK-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14716315#comment-14716315
]
Stephan Ewen commented on FLINK-2579:
-------------------------------------
Interesting point. Some configuration methods can be put into a common
contract, to be uniform, that is true.
One thought we had was that we can do some things better in the streaming API
where we learned from the shortcomings of the batch API. So I would like to
make them uniform where it makes sense, but keep a bit of liberty to make
things better in the streaming API (which we cannot change in the batch API due
to compatibility)
Do you have a set of methods in mind that you thing should be made uniform (in
addition to parallelism and kryo registration)?
> 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: Core
> Reporter: Arnaud Linz
> Priority: Minor
> 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
(v6.3.4#6332)
