[SERVER-65115] INLJ cannot be used if collation of the index doesn't match the effective collation of $lookup Created: 31/Mar/22 Updated: 29/Oct/23 Resolved: 06/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Irina Yatsenko (Inactive) | Assignee: | Rui Liu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | QE 2022-04-04, QE 2022-04-18 |
| Participants: |
| Description |
|
The effective collation on $lookup can be set through various means (_internalCollation property on $lookup stage, collation property on the pipeline, collation of the local collection) and might not match the collation of the index of the foreign collection. In this case we should fall back to using NLJ/HJ algorithms. |
| Comments |
| Comment by Githook User [ 06/Apr/22 ] |
|
Author: {'name': 'Rui Liu', 'email': 'rui.liu@mongodb.com', 'username': 'lriuui0x0'}Message: |