You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Fabian Hueske (JIRA)" <ji...@apache.org> on 2016/12/07 10:25:58 UTC
[jira] [Created] (FLINK-5268) Split TableProgramsTestBase into
TableProgramsCollectionTestBase and TableProgramsClusterTestBase
Fabian Hueske created FLINK-5268:
------------------------------------
Summary: Split TableProgramsTestBase into TableProgramsCollectionTestBase and TableProgramsClusterTestBase
Key: FLINK-5268
URL: https://issues.apache.org/jira/browse/FLINK-5268
Project: Flink
Issue Type: Sub-task
Components: Table API & SQL
Affects Versions: 1.2.0
Reporter: Fabian Hueske
Priority: Minor
Currently the {{TableProgramsTestBase}} allows to run tests on a collection environment and a MiniCluster by setting a testing parameter. This was done to cover different execution path. However, testing on a MiniCluster is quite expensive and should only be done in rare cases.
I propose to split the {{TableProgramsTestBase}} into
* {{TableProgramsCollectionTestBase}} and
* {{TableProgramsClusterTestBase}}
to have the separation of both execution backends more clear.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)