You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Laszlo Bodor (JIRA)" <ji...@apache.org> on 2018/03/10 00:08:00 UTC

[jira] [Updated] (HIVE-18560) qtests: QTestUtil refactor/split - QOutProcessor

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

Laszlo Bodor updated HIVE-18560:
--------------------------------
    Summary: qtests: QTestUtil refactor/split - QOutProcessor  (was: qtests: QTestUtil refactor/split)

> qtests: QTestUtil refactor/split - QOutProcessor
> ------------------------------------------------
>
>                 Key: HIVE-18560
>                 URL: https://issues.apache.org/jira/browse/HIVE-18560
>             Project: Hive
>          Issue Type: Task
>            Reporter: Laszlo Bodor
>            Assignee: Laszlo Bodor
>            Priority: Major
>         Attachments: HIVE-18560.01.patch
>
>
> QTestUtil needs some refactoring, as it has become a large, hard-to-maintain, hard-to-test class with a bunch of responsibilities:
>  * running qtests
>  * parsing/evaluating results
>  * masking/processing results
> First, I would extract a processing class from it (e.g. QOutProcessor or something like that), which should be capable of being tested easily, and contains all the logic what's needed to make the final q.out results from the original q.out file. 
> This processing class shall remain untouched in case the testing infrastructure (QTestUtil) is replaced or changed in some ways.



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