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/07/14 21:25:00 UTC
[jira] [Closed] (FLINK-5271) Refactor the batch SQL tests
[ https://issues.apache.org/jira/browse/FLINK-5271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
sunjincheng closed FLINK-5271.
------------------------------
Resolution: Duplicate
FLINK-6617 already done.
> Refactor the batch SQL tests
> ----------------------------
>
> Key: FLINK-5271
> URL: https://issues.apache.org/jira/browse/FLINK-5271
> Project: Flink
> Issue Type: Sub-task
> Components: Table API & SQL
> Affects Versions: 1.2.0
> Reporter: Fabian Hueske
> Assignee: sunjincheng
>
> Most tests of the batch SQL tests are full-blown integration tests which are rather expensive to execute.
> All tests should be converted into unit tests that validate the resulting execution plan (consisting of {{DataSetRel}} nodes) based on the {{TableTestBase}} class.
> Since the translation from {{DataSetRel}} nodes to the DataSet programs is covered by the batch Table API tests (see FLINK-5270), we do not need additional integration tests that validate the result of an execution (except for the case where a certain DataSetRel node cannot be constructed via the Table API.).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)