[IMPALA-8857] test_kudu_col_not_null_changed may fail because client reads older timestamp

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: Impala 3.3.0
• Fix Version/s: Impala 4.0.0
• Component/s: Infrastructure
• Labels: flaky
• Epic Color: ghx-label-3
• Assignee: Thomas Tauber-Marshall
• Reporter: Tim Armstrong
• Created: 13/Aug/19 00:17
• Updated: 09/Apr/20 16:53
• Resolved: 09/Apr/20 16:53

Description

uery_test/test_kudu.py:242: in test_kudu_col_not_null_changed
    assert len(cursor.fetchall()) == 100
E   assert 61 == 100
E    +  where 61 = len([(0, None), (2, None), (4, None), (11, None), (12, None), (19, None), ...])
E    +    where [(0, None), (2, None), (4, None), (11, None), (12, None), (19, None), ...] = <bound method HiveServer2Cursor.fetchall of <impala.hiveserver2.HiveServer2Cursor object at 0x7fe82c051550>>()
E    +      where <bound method HiveServer2Cursor.fetchall of <impala.hiveserver2.HiveServer2Cursor object at 0x7fe82c051550>> = <impala.hiveserver2.HiveServer2Cursor object at 0x7fe82c051550>.fetchall

I believe this is a flaky tests, since there's no attempt to pass the timestamp from the kudu client that did the insert to the impala client that's doing the reading.