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

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

Commit 69376fa4aa9aabd28c7347ef2a42b7b340ad85be in impala's branch 
refs/heads/master from Michael Smith
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=69376fa4a ]

IMPALA-14160: Update to CDP build with HDFS-13615

Updates to a newer CDP build that includes HDFS-13615, which fixes
Ozone so it correctly reports when files are encrypted with
listStatusIterator, fixing TestTupleCacheCluster.test_runtime_filters.

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


> TestTupleCacheCluster.test_runtime_filters fails on Ozone
> ---------------------------------------------------------
>
>                 Key: IMPALA-14160
>                 URL: https://issues.apache.org/jira/browse/IMPALA-14160
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>    Affects Versions: Impala 5.0.0
>            Reporter: Joe McDonnell
>            Assignee: Michael Smith
>            Priority: Blocker
>             Fix For: Impala 5.0.0
>
>
> On certain versions of Ozone, TestTupleCacheCluster.test_runtime_filters 
> fails with:
> {noformat}
> custom_cluster/test_tuple_cache.py:501: in test_runtime_filters
>     assertCounters(rerun_two_files_result.runtime_profile, 1, 0, 0, 
> num_matches=8)
> custom_cluster/test_tuple_cache.py:75: in assertCounters
>     assertCounter(profile, NUM_HITS, num_hits, num_matches)
> custom_cluster/test_tuple_cache.py:71: in assertCounter
>     assert len([v for v in values if v == val]) in num_matches, values
> E   AssertionError: [0, 0, 0, 1, 1, 0, ...]
> E   assert 2 in [8]
> E    +  where 2 = len([1, 1]){noformat}
> This is running "invalidate metadata" and expecting the cache keys not to 
> change. It seems to have been working until recently, so it is possible there 
> is some interaction with the version of Ozone.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to