Support all QSN stages in join cost model

ExportXMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Do
    • Priority: Trivial - P5
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently the join cost model only supports QSNs with the following stages: Fetch, CollScan and IxScan. As we expand the join optimization module to support more complex queries, we may find that we end up generating single table plan fragments with other operators like projections, index intersection, sort, etc.

      This ticket represents the work to properly incorporate these costs into the join cost model.

            Assignee:
            Unassigned
            Reporter:
            Ben Shteinfeld
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: