You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Timo Walther (JIRA)" <ji...@apache.org> on 2017/01/17 12:51:26 UTC
[jira] [Resolved] (FLINK-5268) Split TableProgramsTestBase into
TableProgramsCollectionTestBase and TableProgramsClusterTestBase
[ https://issues.apache.org/jira/browse/FLINK-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timo Walther resolved FLINK-5268.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.3.0
Fixed in 1.3.0: dba7d7da9b81fce21c13093634118a863a2e2bcc
> 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
> Fix For: 1.3.0
>
>
> 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)