[IMPALA-7790] Kudu tests fail when with use_hybrid_clock=false

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Impala 3.2.0
• Epic Color: ghx-label-5
• Assignee: Thomas Tauber-Marshall
• Reporter: Thomas Tauber-Marshall
• Created: 30/Oct/18 22:43
• Updated: 04/Dec/18 22:27
• Resolved: 04/Dec/18 22:27

Description

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.