You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Paul Rogers (JIRA)" <ji...@apache.org> on 2017/03/14 22:13:42 UTC

[jira] [Updated] (DRILL-5325) Implement sub-operator unit tests for managed external sort

     [ https://issues.apache.org/jira/browse/DRILL-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Rogers updated DRILL-5325:
-------------------------------
    Summary: Implement sub-operator unit tests for managed external sort  (was: Implement sub-opertor unit tests for managed external sort)

> Implement sub-operator unit tests for managed external sort
> -----------------------------------------------------------
>
>                 Key: DRILL-5325
>                 URL: https://issues.apache.org/jira/browse/DRILL-5325
>             Project: Apache Drill
>          Issue Type: Sub-task
>          Components: Tools, Build & Test
>    Affects Versions: 1.11.0
>            Reporter: Paul Rogers
>            Assignee: Paul Rogers
>             Fix For: 1.11.0
>
>
> Validate the proposed sub-operator test framework, by creating low-level unit tests for the managed version of the external sort.
> The external sort has a small number of existing tests, but those tests are quite superficial; the "managed sort" project found many bugs. The managed sort itself was tested with ad-hoc system-level tests created using the new "cluster fixture" framework. But, again, such tests could not reach deep inside the sort code to exercise very specific conditions.
> As a result, we spent far too much time using QA functional tests to identify specific code issues.
> Using the sub-opeator unit test framework, we can instead test each bit of functionality at the unit test level.
> If doing so works, and is practical, it can serve as a model for other operator testing projects.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)