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

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

Commit a1407adf61cec9bdd2ebb5bb7a7ccbbf5d2edd41 in impala's branch 
refs/heads/master from [~twmarshall]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=a1407ad ]

IMPALA-7790: Skip some Kudu tests if use_hybrid_clock=false

Since IMPALA-6812, we've run many of our tests against Kudu at the
READ_AT_SNAPSHOT scan level, which ensures consistent results. This
scan level is only supported if Kudu is run with the flag
--use_hybrid_clock=true (which is the default).

This patch uses the Kudu master webui to detect when use_hybrid_clock
is false and skips these tests.

Follow up work will address allowing these tests to run regardless of
the value of the flag.

Testing:
- Ran a full exhaustive build with use_hybrid_clock=false set in the
  minicluster.

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


> Kudu tests fail when with use_hybrid_clock=false
> ------------------------------------------------
>
>                 Key: IMPALA-7790
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7790
>             Project: IMPALA
>          Issue Type: Bug
>            Reporter: Thomas Tauber-Marshall
>            Assignee: Thomas Tauber-Marshall
>            Priority: Major
>
> Since IMPALA-6812, we've run many of our tests against Kudu at the 
> READ_AT_SNAPSHOT scan level, which ensures consistent results. This scan 
> level is only supported if Kudu is run with the flag --use_hybrid_clock=true 
> (which is the default).
> This hasn't generally been a problem in the past, as we've primarily run 
> Impala's functional tests against the minicluster, where Kudu is configured 
> correctly, but there's been some effort around running these tests against 
> real clusters, in which case --use_hybrid_clock=false may be set.
> We should at a minimum recognize this situation and skip the tests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to