You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "sunjincheng (JIRA)" <ji...@apache.org> on 2017/06/01 14:33:04 UTC
[jira] [Assigned] (FLINK-5272) Refactor the stream Scala-expression
Table API tests
[ https://issues.apache.org/jira/browse/FLINK-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
sunjincheng reassigned FLINK-5272:
----------------------------------
Assignee: sunjincheng
> Refactor the stream Scala-expression Table API tests
> ----------------------------------------------------
>
> Key: FLINK-5272
> URL: https://issues.apache.org/jira/browse/FLINK-5272
> Project: Flink
> Issue Type: Sub-task
> Components: Table API & SQL
> Affects Versions: 1.2.0
> Reporter: Fabian Hueske
> Assignee: sunjincheng
>
> Most tests of the streaming Scala Table API tests are full-blown integration tests which are rather expensive to execute.
> Most of tests should be converted into unit tests that validate the resulting execution plan (consisting of {{DataStreamRel}} nodes) based on the {{TableTestBase}} class.
> In addition we need a few integration tests that check the translation from the optimized {{DataStreamRel}} plan to a DataStream program. These tests should be implemented by extending the {{StreamingMultipleProgramsTestBase}} and be located in few classes to avoid repeated instantiations of the FLink MiniCluster.
> These tests must cover the translation process of each {{DataStreamRel}} operator.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)