[ 
https://issues.apache.org/jira/browse/HIVE-26584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612422#comment-17612422
 ] 

John Sherman commented on HIVE-26584:
-------------------------------------

After reading the tests in deeper detail, I've modified the posted patch and 
modified both compressed_skip_header_footer_aggr.q and 
empty_skip_header_footer_aggr.q to:
1) Changed all the EXTERNAL TABLEs to normal managed tables
2) Added DROPs to the test for the created tables (so the underlying data gets 
removed normally)
3) Removed the dfs commands that created directories and copied the test data
4) Added LOAD DATA commands to populate the tables with the test data
5) I also gave the tables unique names between the tests (I find it easier to 
have unique names for debugging).

I find this approach less error prone and less confusing (LOAD DATA is more 
idiomatic). I saw nothing inherent to the test cases that required external 
tables.

> compressed_skip_header_footer_aggr.q is flaky
> ---------------------------------------------
>
>                 Key: HIVE-26584
>                 URL: https://issues.apache.org/jira/browse/HIVE-26584
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>    Affects Versions: 4.0.0-alpha-2
>            Reporter: John Sherman
>            Assignee: John Sherman
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> One of my PRs compressed_skip_header_footer_aggr.q  was failing with 
> unexpected diff. Such as:
> {code:java}
>  TestMiniLlapLocalCliDriver.testCliDriver:62 Client Execution succeeded but 
> contained differences (error code = 1) after executing 
> compressed_skip_header_footer_aggr.q
> 69,71c69,70
> < 1 2019-12-31
> < 2 2018-12-31
> < 3 2017-12-31
> ---
> > 2 2019-12-31
> > 3 2019-12-31
> 89d87
> < NULL  NULL
> 91c89
> < 2 2018-12-31
> ---
> > 2 2019-12-31
> 100c98
> < 1
> ---
> > 2
> 109c107
> < 1 2019-12-31
> ---
> > 2 2019-12-31
> 127,128c125,126
> < 1 2019-12-31
> < 3 2017-12-31
> ---
> > 2 2019-12-31
> > 3 2019-12-31
> 146a145
> > 2 2019-12-31
> 155c154
> < 1
> ---
> > 2 {code}
> Investigating it, it did not seem to fail when executed locally. Since I 
> suspected test interference I searched for the tablenames/directories used 
> and discovered empty_skip_header_footer_aggr.q which uses the same table 
> names AND external directories.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to