You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/12/21 20:53:46 UTC

[jira] [Commented] (TRAFODION-1714) ULOG debugging tool does not capture query plan until after execution

    [ https://issues.apache.org/jira/browse/TRAFODION-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066995#comment-15066995 ] 

ASF GitHub Bot commented on TRAFODION-1714:
-------------------------------------------

GitHub user DaveBirdsall opened a pull request:

    https://github.com/apache/incubator-trafodion/pull/238

    [TRAFODION-1714] Sample table population plan now printed before exec…

    …ution

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/DaveBirdsall/incubator-trafodion Trafodion1714

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-trafodion/pull/238.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 #238
    
----
commit 8a2085f2dfbf8fc6673bd7fb48099faeae3dd484
Author: Dave Birdsall <db...@apache.org>
Date:   2015-12-21T19:49:35Z

    [TRAFODION-1714] Sample table population plan now printed before execution

----


> ULOG debugging tool does not capture query plan until after execution
> ---------------------------------------------------------------------
>
>                 Key: TRAFODION-1714
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-1714
>             Project: Apache Trafodion
>          Issue Type: Bug
>          Components: sql-cmp
>    Affects Versions: 2.0-incubating, 1.3-incubating
>         Environment: All
>            Reporter: David Wayne Birdsall
>            Assignee: David Wayne Birdsall
>
> ULOG is a diagnostic feature that we use when debugging problems with the UPDATE STATISTICS utility. It logs various information about the code paths and decisions taken by the utility during the course of its execution. One useful thing it does is to dump the query plans of any queries that it executes. Unfortunately, for the Sample Table load query, the plan isn't dumped until after execution completes. This is a problem because sometimes (due to other issues) that load query doesn't complete. So the query plan doesn't get logged in this case, forcing us to use other diagnostic methods to obtain this information. We would improve the ability to support Trafodion by dumping the query plans before execution.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)