Description
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.
Attachments
Attachments
Issue Links
- is related to
-
HIVE-18061 q.outs: be more selective with masking hdfs paths
-
- Closed
-