Make "prefer shorter indexes" code take presence of index bounds into account

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We have code here that assigns a higher cost to longer indexes even if the fields in those indexes carry bounds (which means they're actually doing work that save us from evaluating within the residual predicate). We should experiment with only assigning that incremental field cost if the field has no bounds.

        1. cbr_persisted_sample_compound_index (1).js
          7 kB

            Assignee:
            Unassigned
            Reporter:
            Militsa Sotirova
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: