[
https://issues.apache.org/jira/browse/IMPALA-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pooja Nilangekar updated IMPALA-7246:
-------------------------------------
Description:
The failure observed in IMPALA-6960 occurred again while testing
[https://gerrit.cloudera.org/c/10704/]
The query is different, however the cause of failure is the same. In this case,
the profile for Instance e7462de57ef6fd00:25f810c300000005
(host=ip-172-31-28-156:22000) is empty. The query returned the expected
results, but the runtime profile wasn't updated.
I have attached the failure logs.
was:
The failure observer in IMPALA-6960 occurred again while testing
[https://gerrit.cloudera.org/c/10704/]
The query is different however, the cause of failure is the same. In this case,
the profile for Instance e7462de57ef6fd00:25f810c300000005
(host=ip-172-31-28-156:22000) is empty. The query returned the expected results
however, the runtime profile wasn't updated.
I have attached the failure logs.
> TestMtDopParquet.test_parquet_filtering is flaky
> ------------------------------------------------
>
> Key: IMPALA-7246
> URL: https://issues.apache.org/jira/browse/IMPALA-7246
> Project: IMPALA
> Issue Type: Bug
> Reporter: Pooja Nilangekar
> Priority: Major
> Attachments: TEST-impala-parallel.log, TEST-impala-parallel.xml
>
>
> The failure observed in IMPALA-6960 occurred again while testing
> [https://gerrit.cloudera.org/c/10704/]
> The query is different, however the cause of failure is the same. In this
> case, the profile for Instance e7462de57ef6fd00:25f810c300000005
> (host=ip-172-31-28-156:22000) is empty. The query returned the expected
> results, but the runtime profile wasn't updated.
> I have attached the failure logs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
