Ixscan plans on unique indexes needlessly call next() on storage cursor

XMLWordPrintableJSON

    • Query Execution
    • Fully Compatible
    • 154
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When we make an index scan SBE plan with point bounds, we end up calling next() in the storage layer more than once, even though a unique index guarantees that there can only be one key. We should consider optimizing this.

              Assignee:
              Zixuan Zhuang
              Reporter:
              Ian Boros
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: