index intersection needs to track memory usage and abort if it's too high

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.6.0-rc1
    • Affects Version/s: None
    • Component/s: Querying
    • None
    • Fully Compatible
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Should do this in a fashion similar to how sort does it. Unclear if we want to use the incorrect accounting that sort currently uses or the 'real' accounting that is much leaner. Either way, we should do something.

      All of the logic to fall back on an indexed sort should be generalized to fall back on a non-blocking plan.

            Assignee:
            Benety Goh
            Reporter:
            hari.khalsa@10gen.com
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: