[
https://issues.apache.org/jira/browse/IMPALA-8857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Tauber-Marshall updated IMPALA-8857:
-------------------------------------------
Target Version: (was: Impala 3.4.0)
> test_kudu_col_not_null_changed may fail because client reads older timestamp
> ----------------------------------------------------------------------------
>
> Key: IMPALA-8857
> URL: https://issues.apache.org/jira/browse/IMPALA-8857
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: Impala 3.3.0
> Reporter: Tim Armstrong
> Assignee: Thomas Tauber-Marshall
> Priority: Critical
> Labels: flaky
>
> {noformat}
> 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
> {noformat}
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
