-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Optimization
While investigating BF-35556, I realized that we allow empty sortBy for $top/$topN/$bottom/$bottomN. But $top/$topN/$bottom/$bottomN accumulator specification says that sortBy is required. I can hardly imagine that such accumulator produces meaningful results for customers since results would not be deterministic.
SERVER-96458 has an example in comments.
Is it just an oversight or are there use cases?
If it's just an oversight, can we forbid empty sortBy?
- is related to
-
SERVER-96458 Don't apply distinct scan optimization when $top(N)/$bottom(N)'s output is constant and sortBy is empty
-
- Closed
-