You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Thomas Tauber-Marshall (JIRA)" <ji...@apache.org> on 2018/10/30 22:44:00 UTC
[jira] [Created] (IMPALA-7790) Kudu tests fail when with
use_hybrid_clock=false
Thomas Tauber-Marshall created IMPALA-7790:
----------------------------------------------
Summary: 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
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: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org