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

ASF subversion and git services commented on IMPALA-9365:
---------------------------------------------------------

Commit e863bac074f70b9d063cd7e53e46b3065b99edcb in impala's branch 
refs/heads/master from Zoltan Borok-Nagy
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=e863bac ]

IMPALA-9617: Skip tests that use Hive on non-HDFS filesystems

Some tests are flaky due to timeouts in Hive queries on non-HDFS
filesystems. Until IMPALA-9365 is resolved we only run these tests
when the target filesystem is HDFS.

Change-Id: I50fe92801e6e0f0ad8e169ec91ca4a8530088b7f
Reviewed-on: http://gerrit.cloudera.org:8080/15736
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> Run hive-server2, YARN etc on non-HDFS test envs
> ------------------------------------------------
>
>                 Key: IMPALA-9365
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9365
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Infrastructure
>            Reporter: Tim Armstrong
>            Priority: Major
>
> We don't start yarn unless HDFS is also running - 
> https://github.com/apache/impala/blob/master/testdata/cluster/admin#L70. 
> We also don't start various other services, including hive server 2 
> https://github.com/apache/impala/blob/master/testdata/bin/run-all.sh#L79 .
> This has been a persistent pain point for testing, because we can't load data 
> and can't run many tests against those filesystems (see all the SkipIfS3 , 
> etc annotations). Even worse, it can result in hard-to-debug failure modes 
> like IMPALA-9345.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to