Uploaded image for project: 'Teiid Designer'
  1. Teiid Designer
  2. TEIIDDES-767

Staging tables performance appears to be sub-par - should allow for key/index information

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Won't Do
    • Major
    • No Future
    • 7.0
    • Modeling
    • None

    Description

      Defect Tracker #20207: While working on the E2E Staging Tables Test Script, Mark Donnelly noticed the performance was fairly even between docs using staging tables and docs not using staging tables. I did further research and found the queries ran faster without staging tables. The email thread is attached (zipped in case the Trakka doesn't like it).

      The Model Project Set is also attached. The VDB's lone binding is defined.

      Attachments

        Issue Links

          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) TEIID-2338 staging table performance

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              Unassigned Unassigned
              rhn-engineering-shawkins Steven Hawkins
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: