You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Paul Rogers (JIRA)" <ji...@apache.org> on 2019/03/01 17:52:00 UTC

[jira] [Resolved] (IMPALA-7821) Split up test functions in ExprRewriteRulesTest for easier debugging

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

Paul Rogers resolved IMPALA-7821.
---------------------------------
    Resolution: Won't Fix

No longer a priority.

> Split up test functions in ExprRewriteRulesTest for easier debugging
> --------------------------------------------------------------------
>
>                 Key: IMPALA-7821
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7821
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Frontend
>    Affects Versions: Impala 3.0
>            Reporter: Paul Rogers
>            Assignee: Paul Rogers
>            Priority: Minor
>
> Impala provides a single test class {{ExprRewriteRulesTest}} for all rewrite rules. Each rule class has an associated test function. Some rules are complex, and the result test functions are quite large.
> When doing work to modify a particular conditional rewrite, it became clear that debugging would be much easier if each detailed rewrite had its own test rather than using one huge test function. This ticket asks to break up the big function. (JUnit does not care about small vs. large functions.)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)