hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Vary (JIRA)" <>
Subject [jira] [Commented] (HIVE-16146) If possible find a better way to filter the TestBeeLineDriver output
Date Wed, 08 Mar 2017 15:12:37 GMT


Peter Vary commented on HIVE-16146:

I can imagine 2 different approach:
- Blacklist - Keeping every line, but removing the blacklisted ones
- Whitelist - Keeping only specific lines

I prefer the blacklist solution, because the other approach could hide unintended changes

I think we might find a better logging level to use for the qtests. Currently we using the
following settings:
- verbose - print debug messages, stack traces in case of an exception
- shownestederrs - print the nested exception - not dependent on verbose :)
- showwarnings - needs verbose on - prints out any warnings that exist for the current connection.

We might produce the same results as the TestCliDriver qtest if we use the silent mode. I
have to check that.

> If possible find a better way to filter the TestBeeLineDriver output
> --------------------------------------------------------------------
>                 Key: HIVE-16146
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Testing Infrastructure
>    Affects Versions: 2.2.0
>            Reporter: Peter Vary
>            Assignee: Peter Vary
> 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
> 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

View raw message