[teiid-issues] [JBoss JIRA] (TEIID-2043) Dedug query plans can be too large

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-2043.
-----------------------------------

    Resolution: Done


Updated the plannode logic to only show the full properties when a potential modification has been made.  also converted most debug plan additional statements to annotations so that they are more easily readable.  In most circumstances then we'll recommend SHOWPLAN ON and inspection of the annotations/processor plan, rather than SHOWPLAN DEBUG.
                
> Dedug query plans can be too large 
> -----------------------------------
>
>                 Key: TEIID-2043
>                 URL: https://issues.jboss.org/browse/TEIID-2043
>             Project: Teiid
>          Issue Type: Quality Risk
>          Components: Query Engine
>    Affects Versions: 7.0
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 8.1
>
>
> As seen in TEIID-2041 debug logs can grow much too large.  The two main culprits are full pre-planning of all subqueries and the amount of information shown on each node for each rule.  To address the former we should instead only plan project node subqueries after the initial run of RuleAssignOutputElements, since typically not all columns will be used.  For the latter we should consider putting a modified marker on a plannode that will get cleared after a toString to truncate the values shown for a node (in some cases we make modifications to objects held on the node, so it's not quite that simple).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira