[
https://issues.apache.org/jira/browse/HIVE-16146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Haindrich updated HIVE-16146:
------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
pushed to master. Thank you [~pvary] for taking care of this; the beeline
outputs are starting to look much more natural.
I'm not sure how can we avoid "bending" the production code because of test
related features...I'm still trying to come up with some idea for this...do you
have any tought? ...since you have seen a lot of it lately :)
> If possible find a better way to filter the TestBeeLineDriver output
> --------------------------------------------------------------------
>
> Key: HIVE-16146
> URL: https://issues.apache.org/jira/browse/HIVE-16146
> Project: Hive
> Issue Type: Improvement
> Components: Testing Infrastructure
> Affects Versions: 2.2.0
> Reporter: Peter Vary
> Assignee: Peter Vary
> Attachments: HIVE-16146.02.patch, HIVE-16146.03.patch,
> HIVE-16146.04.patch, HIVE-16146.05.patch, HIVE-16146.06.patch,
> HIVE-16146.patch
>
>
> Currently we apply a blacklist to filter the output of the BeeLine Qtest runs.
> It might be a good idea to go thorough of the possibilities and find a better
> way, if possible.
> I think our main goal could be for the TestBeeLineDriver test output to match
> the TestCliDriver output of the came query file. Or if it is not possible,
> then at least a similar one
> CC: [~vihangk1]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
