You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Lefty Leverenz (JIRA)" <ji...@apache.org> on 2017/09/06 23:03:00 UTC
[jira] [Commented] (HIVE-16146) If possible find a better way to
filter the TestBeeLineDriver output
[ https://issues.apache.org/jira/browse/HIVE-16146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156168#comment-16156168 ]
Lefty Leverenz commented on HIVE-16146:
---------------------------------------
HIVE-17382 renames the configs (no doc needed, internal use only):
* hive.in.test.short.logs -> hive.testing.short.logs
* hive.in.test.remove.logs -> hive.testing.remove.logs
> 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.4.14#64029)