[
https://issues.apache.org/jira/browse/IMPALA-6942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht resolved IMPALA-6942.
-------------------------------
Resolution: Fixed
Fix Version/s: Impala 3.1.0
commit 76f8ff4a1507c3a7f86eb58dbac191024b59890e
Author: Dan Hecht <[email protected]>
Date: Thu Jun 14 13:05:49 2018 -0700
IMPALA-6942: Reword error message to say "Failed" rather than "Cancelled"
In this case, the query is failing. It happens to use the cancellation
path to cleanup, but from a user's perspective this is a query failure
not a cancellation. Reword the message to reflect that.
Change-Id: I4d8e755aef196e5c25205094af9c8486eb899344
Reviewed-on: http://gerrit.cloudera.org:8080/10717
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> "Cancelled due to unreachable impalad(s)" error message is misleading
> ---------------------------------------------------------------------
>
> Key: IMPALA-6942
> URL: https://issues.apache.org/jira/browse/IMPALA-6942
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 3.0
> Reporter: Dan Hecht
> Assignee: Dan Hecht
> Priority: Major
> Fix For: Impala 3.1.0
>
>
> The error message "Cancelled due to unreachable impalad(s)" would be better
> as "Failed due to unreachable impalad(s)" since the query has failed. The
> code happens to trigger cancellation via the same path as client
> cancellation, but this is really a query failure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
