[SERVER-74826] Errors CommandOnShardedViewNotSupportedOnMongod on sharded view Created: 14/Mar/23 Updated: 11/May/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 6.0.2, 6.0.3, 6.0.4, 4.4.21 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | mocxat mocxat | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Optimization
|
||||||||
| Participants: | |||||||||
| Description |
|
Hello.
when using .find() or .findOne() in a view that union sharded collections. The data in the collections is accessible through the view, but what does this error mean? And what to do with it? My configuration: Sharded cluster in 3 shard (2 node + 1 arbiter in each) / debian 11(bullseye)
|
| Comments |
| Comment by Edwin Zhou [ 04/May/23 ] |
|
Hi taxmailtest@gmail.com, thank you for your report, patience, and reproduction of this issue! I've been able to successfully reproduce this error code on a single node sharded cluster. We do have improvements to handle this error on our backlog in SERVER-42282. However, I agree that it is unusual for the find command to return the "CommandOnShardedViewNotSupportedOnMongod" error when the command appears to work and is being run from a mongos. I will pass this on to the query team to further investigate this issue. Kind regards, |