Uploaded image for project: 'Teiid'
  1. Teiid
  2. TEIID-2043

Dedug query plans can be too large

    XMLWordPrintable

    Details

    • Type: Quality Risk
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 7.0
    • Fix Version/s: 8.1
    • Component/s: Query Engine
    • Labels:
      None

      Description

      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).

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                shawkins Steven Hawkins
                Reporter:
                shawkins Steven Hawkins
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: