[
https://issues.apache.org/jira/browse/HAWQ-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15211626#comment-15211626
]
ASF GitHub Bot commented on HAWQ-591:
-------------------------------------
GitHub user ictmalili opened a pull request:
https://github.com/apache/incubator-hawq/pull/509
HAWQ-591. Explain analyze doesn't enter function cdbexplain_recvExecS…
…tats after QD finding QE error
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ictmalili/incubator-hawq HAWQ-591
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-hawq/pull/509.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #509
----
commit 99aed92cc6b54a317e27dbcb800d6c99d472fa18
Author: Lili Ma <ictmal...@gmail.com>
Date: 2016-03-25T09:08:24Z
HAWQ-591. Explain analyze doesn't enter function cdbexplain_recvExecStats
after QD finding QE error
----
> Explain analyze should not gather QE execution detail when QE runtime error
> has been caught by QD
> -------------------------------------------------------------------------------------------------
>
> Key: HAWQ-591
> URL: https://issues.apache.org/jira/browse/HAWQ-591
> Project: Apache HAWQ
> Issue Type: Bug
> Components: Dispatcher
> Reporter: Lili Ma
> Assignee: Lei Chang
>
> In function cdbexplain_recvExecStats, it will gather QE runtime statistics,
> and will elog ERROR under some cases. But when QE gets error or is killed,
> the error information will be caught by dispatcher, and the error under
> explain analyze will be marked as 'NOTICE' instead of 'DEBUG', if we enter
> into function cdbexplain_recvExecStats, the elog error will cover and shield
> the actual information from QE.
> So if dispatcher has caught QE error, we should not enter
> cdbexplain_recvExecStats.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
