[SERVER-77419] Improve error message when a sharded lookup fails in a transaction Created: 24/May/23 Updated: 29/Oct/23 Resolved: 09/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Nicholas Zolnierz | Assignee: | Hana Pearlman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Query Optimization
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | QO 2023-05-29, QO 2023-06-12 | ||||
| Participants: | |||||
| Description |
|
The errmsg only indicates "<nss> cannot be sharded" but otherwise gives no indication as to why it cannot be sharded. Since we now support sharded lookup to some extent, it will be helpful to include the exact reason in the assertion. |
| Comments |
| Comment by Githook User [ 08/Jun/23 ] |
|
Author: {'name': 'Hana Pearlman', 'email': 'hana.pearlman@mongodb.com', 'username': 'HanaPearlman'}Message: |