Guard against undesired extensions stage behavior

XMLWordPrintableJSON

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

      One thread spun out of SERVER-123271 was what sort of extensions user behavior should we implement guards against, if any. For example, one implicit constraint is the following:

      • If mergeSortPattern is populated on the DPL then each document returned from getNext() should have $sortKey metadata populated. If this constraint is broken, then an internal, somewhat convoluted, error will surface to the extensions user
      • Other scenarios to consider...?

            Assignee:
            Unassigned
            Reporter:
            Adithi Raghavan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: