[SERVER-58382] Error handling for time-series updates and deletes on collections without a metaField Created: 08/Jul/21 Updated: 30/Jul/21 Resolved: 30/Jul/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.1.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kris Satya (Inactive) | Assignee: | Kris Satya (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Sprint: | Execution Team 2021-07-26, Execution Team 2021-08-09 | ||||
| Participants: | |||||
| Linked BF Score: | 148 | ||||
| Description |
|
Currently, updates and deletes on collections without a metaField don't correctly fail because the isTimeseriesMetadataOnlyQuery function checks to see if the query only contains the field "meta." A time-series collection without a metaField should not be able to query on the field "meta" and instead throw an error, but because of the behavior of isTimeseriesMetadataOnlyQuery described above, no error is thrown. |
| Comments |
| Comment by Githook User [ 23/Jul/21 ] |
|
Author: {'name': 'Kris Satya', 'email': 'kris.satya@mongodb.com', 'username': 'KoolCards'}Message: Revert " This reverts commit 945c55f1bc2c51aed5a9afeae47caeb4e50a9b97. |
| Comment by Githook User [ 23/Jul/21 ] |
|
Author: {'name': 'Kris Satya', 'email': 'kris.satya@mongodb.com', 'username': 'KoolCards'}Message: |