[ https://issues.apache.org/jira/browse/FLINK-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16299912#comment-16299912 ]
ASF GitHub Bot commented on FLINK-7909: --------------------------------------- Github user GJL commented on a diff in the pull request: https://github.com/apache/flink/pull/4896#discussion_r158259995 --- Diff: flink-examples/flink-examples-streaming/src/main/java/org/apache/flink/streaming/examples/windowing/TopSpeedWindowing.java --- @@ -55,6 +55,7 @@ public static void main(String[] args) throws Exception { final StreamExecutionEnvironment env = StreamExecutionEnvironment.getExecutionEnvironment(); env.setStreamTimeCharacteristic(TimeCharacteristic.EventTime); env.getConfig().setGlobalJobParameters(params); + env.setParallelism(1); --- End diff -- Is this strictly needed? It's not a Unit or ITCase and the example seems to work without this line. > Unify cluster creation for test bases > ------------------------------------- > > Key: FLINK-7909 > URL: https://issues.apache.org/jira/browse/FLINK-7909 > Project: Flink > Issue Type: Improvement > Components: Tests > Affects Versions: 1.4.0 > Reporter: Till Rohrmann > Assignee: Till Rohrmann > > Flink contains different test bases, e.g. {{AbstractTestBase}}, > {{MultipleProgramsTestBase}}, {{JavaProgramTestBase}} and the > {{StreamingMultipleProgramsTestBase}}. Some of them start resources > ({{FlinkMiniCluster}}) automatically, while others expose a start method. > Some test bases set the {{ExecutionEnvironment}} while others use the > {{FlinkMiniCluster}} directly. In order to make things more maintainable I > propose to unify these test bases a bit and introduce an {{ExternalResource}} > which encapsulates the resource start up and shut down. -- This message was sent by Atlassian JIRA (v6.4.14#64029)