Tim Armstrong has posted comments on this change. ( http://gerrit.cloudera.org:8080/12022 )
Change subject: IMPALA-5474: Adding a trivial subquery turns error into warning ...................................................................... Patch Set 2: Yeah WARNING isn't a query state, it's just that the error log mechanism can be used to return warnings that don't fail the query. It should be valid to call fetch on any query. Since https://issues.apache.org/jira/browse/IMPALA-5903 was fixed every query type has some kind of result set (even if it's just a status message). impala-shell tries to be a bit more clever and report DML results and similar in a special way, but other clients just fetch the result set. If you look at ImpalaServer::FetchInternal() if called once the query is in the EXCEPTION state it will end up raising the query status as a BeeswaxException. -- To view, visit http://gerrit.cloudera.org:8080/12022 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-Project: Impala-ASF Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: Ibedb11dd3d50bcdb21d508f7d21691925491946e Gerrit-Change-Number: 12022 Gerrit-PatchSet: 2 Gerrit-Owner: Yongjun Zhang <yjzhan...@apache.org> Gerrit-Reviewer: Impala Public Jenkins <impala-public-jenk...@cloudera.com> Gerrit-Reviewer: Joe McDonnell <joemcdonn...@cloudera.com> Gerrit-Reviewer: Paul Rogers <par0...@yahoo.com> Gerrit-Reviewer: Tim Armstrong <tarmstr...@cloudera.com> Gerrit-Reviewer: Yongjun Zhang <yjzhan...@apache.org> Gerrit-Comment-Date: Wed, 05 Dec 2018 01:43:44 +0000 Gerrit-HasComments: No