You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "Lili Ma (JIRA)" <ji...@apache.org> on 2016/03/29 04:01:25 UTC

[jira] [Resolved] (HAWQ-591) Explain analyze should not gather QE execution detail when QE runtime error has been caught by QD

     [ https://issues.apache.org/jira/browse/HAWQ-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lili Ma resolved HAWQ-591.
--------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0

> 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: Lili Ma
>             Fix For: 2.0.0
>
>
> 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)