[SERVER-84589] Error when directly dropping a sharded time-series buckets collection is misleading. Created: 05/Jan/24  Updated: 02/Feb/24  Resolved: 02/Feb/24

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 8.0.0-rc0

Type: Bug Priority: Minor - P4
Reporter: Felipe Gasper Assignee: Haley Connelly
Resolution: Fixed Votes: 0
Labels: storex-ranked
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by SERVER-80929 Drop of sharded system.buckets yields... Closed
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.3, v7.0, v6.0
Sprint: Execution Team 2024-02-05
Participants:

 Description   

There is an error in the server code:

drop collection of a sharded time-series collection is not supported

… that seems to happen only when trying to drop a sharded buckets collection directly.

The error’s wording, though, makes it look like the server can’t drop sharded time-series collections at all, even via public API. That isn’t the case.

The error should instead refer specifically to the buckets. It should also guide the user to how to solve the problem. Maybe something like:

sharded time-series buckets collections cannot be dropped directly; drop the logical collection instead.



 Comments   
Comment by Githook User [ 02/Feb/24 ]

Author:

{'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}

Message: SERVER-84589 Update drop timeseries buckets collection error message (#18431)

GitOrigin-RevId: 09ed5a3568046863fc034463dfbd1a3fca074cd3
Branch: master
https://github.com/mongodb/mongo/commit/7a921397c78486c542d348ec4288438ef4d83978

Generated at Thu Feb 08 06:55:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.