[
https://issues.apache.org/jira/browse/HIVE-16146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928369#comment-15928369
]
Peter Vary commented on HIVE-16146:
-----------------------------------
Here is my thoughts after some digging: Even though we might be able to create
better filtering than the current one in QTestUtil, the main goal could be to
generate the same output from the same query scripts. So if we decide to move a
few tests from the CLI Driver to the BeeLine driver then we should be able to
do it without changing the golden files.
The CLI output contains 3 types of data:
- Query results - columns separated by a single '\t' character
- PREHOOK logs
- POSTHOOK logs
I have yet to find anything else, but there might be something which I missed :)
> 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
>
> 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)
