[
https://issues.apache.org/jira/browse/IMPALA-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht resolved IMPALA-5853.
-------------------------------
Resolution: Fixed
Fix Version/s: (was: Product Backlog)
Impala 2.11.0
commit 593ec25736bffdea11ffceb645a27f27d2eb73f5
Author: Dan Hecht <[email protected]>
Date: Mon Aug 28 15:25:03 2017 -0700
IMPALA-5853: fix GetResultSetMetadata() error message for invalid query id
When given an invalid query id, most RPCs result with "Invalid query
id", but GetResultSetMetadata() response with "Unable to find session ID
for query handle". That's confusing; make it consistent with other
RPCs.
Change-Id: I51eecf353f9cecaf88cecc9392b08ac1b9326b66
Reviewed-on: http://gerrit.cloudera.org:8080/7863
Reviewed-by: Dan Hecht <[email protected]>
Tested-by: Impala Public Jenkins
> GetResultSetMetadata() invalid query id error message is confusing
> ------------------------------------------------------------------
>
> Key: IMPALA-5853
> URL: https://issues.apache.org/jira/browse/IMPALA-5853
> Project: IMPALA
> Issue Type: Bug
> Affects Versions: Impala 2.10.0
> Reporter: Dan Hecht
> Assignee: Dan Hecht
> Fix For: Impala 2.11.0
>
>
> If {{GetResultSetMetadata()}} is called with an invalid query id, the error
> message given is:
> {{Unable to find session ID for query handle:
> efcdab8967452301:3031323334353637}}. Instead, like other RPCs, it should say
> "Invalid query handle: efcdab8967452301:3031323334353637".
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
