[SERVER-64416] Have view creation return the same error as collection creation Created: 10/Mar/22 Updated: 29/Oct/23 Resolved: 30/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.1, 6.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Wenbin Zhu | Assignee: | Yujin Kang Park |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||||||
| Backport Requested: |
v6.0
|
||||||||||||||||||||
| Sprint: | Execution Team 2022-05-16, Execution Team 2022-05-30, Execution Team 2022-06-13 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Currently creating a view would returns an error code 17399 instead of `NamespaceExists` error in case of namespace collision. Since view creation and collection creation use the same API, returning different errors would be confusing to users and they could easily miss catching this error in their code. so we should have view creation return the same error as collection creation to make them consistent. This ticket can also investigate if we return inconsistent errors in other cases in addition to namespace collision.
|
| Comments |
| Comment by Githook User [ 25/Jul/22 ] |
|
Author: {'name': 'Yu Jin Kang Park', 'email': 'yujin.kang@mongodb.com', 'username': 'ykangpark'}Message: (cherry picked from commit 6bd5618937542267553791332394c571973740eb) |
| Comment by Githook User [ 27/May/22 ] |
|
Author: {'name': 'Yu Jin Kang Park', 'email': 'yujin.kang@mongodb.com', 'username': 'ykangpark'}Message: |
| Comment by Connie Chen [ 15/Mar/22 ] |
|
We still want to investigate if we return inconsistent errors in other cases in addition to namespace collision. We also want to look into whether this error can happen with sharding. |