-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Query Execution
-
Fully Compatible
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Running
buildscripts/resmoke.py run --suites=query_golden_classic --mongodSetParameters "{featureFlagSbeEqLookupUnwind: true, internalEnableJoinOptimization: true}" jstests/query_golden/logs_spilling_md.js
produces a different output because the $lookup-$unwind statement in the
HashLookupUnwind section is processed by the HybridHashJoin stage rather than by the LookupHashTable, and the former is ignoring the low
internalQuerySlotBasedExecutionHashLookupApproxMemoryUseInBytesBeforeSpill value that causes spilling.
Trying to force spilling also when Join Optimization is active, by setting these parameters
setServerParameter("internalQuerySlotBasedExecutionHashJoinApproxMemoryUseInBytesBeforeSpill", 1); setServerParameter("internalRandomJoinReorderDefaultToHashJoin", true); setServerParameter("internalJoinReorderMode", "random");
causes an invariant in
if (partitionSize > _memLimit) { if (_recursionLevel == kMaxRecursionDepth) { // TODO SERVER-115389 Fall back to block nested loop join to guarantee completion. MONGO_UNIMPLEMENTED; }
- depends on
-
SERVER-115389 Implement Block Nested Loop Join as fallback from extreme key skew
-
- Closed
-
- duplicates
-
SERVER-119254 Update expected output of $lookup-unwind spilling golden test
-
- Closed
-
- is related to
-
SERVER-115389 Implement Block Nested Loop Join as fallback from extreme key skew
-
- Closed
-
-
SERVER-119254 Update expected output of $lookup-unwind spilling golden test
-
- Closed
-