[
https://issues.apache.org/jira/browse/HIVE-16146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15962251#comment-15962251
]
Zoltan Haindrich commented on HIVE-16146:
-----------------------------------------
I like the new way this is currently handled, and the outputs are much tidier
this way!
+1
[~pvary]: I've taken some time to collect a few ideas about qtests...
https://gist.github.com/kgyrtkirk/89931b7e420c4950b7b36cc8fc1cb6a2
I know that some of it is not entirely doable right now...and I'm probably not
entirely realistic in some points :)
...but anyway, I would be glad to hear what you think about it :)
> 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.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)
