[SERVER-51729] Confusing run-on error message in update shard targeting Created: 19/Oct/20 Updated: 29/Oct/23 Resolved: 03/Nov/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Trivial - P5 |
| Reporter: | Andy Schwerin | Assignee: | Jason Zhang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2020-11-02, Sharding 2020-11-16 |
| Participants: |
| Description |
|
The error message when a user issues a query that cannot be targeted to a specific shard but is not an _id update is hard to understand. |
| Comments |
| Comment by Githook User [ 03/Nov/20 ] |
|
Author: {'name': 'Jason Zhang', 'email': 'jason.zhang@mongodb.com', 'username': 'jz1242'}Message: |