[SERVER-33435] Remove the collstats command Created: 21/Feb/18  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Kyle Suarez Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-24496 Merge collStats output with $collStat... Closed
Related
is related to SERVER-44891 collStats will fail if resulting BSON... Closed
Assigned Teams:
Query Execution
Participants:

 Description   

After SERVER-24496, I believe we gave the $collStats aggregation source a strict superset of the functionality of the weird collStats command. It would be nice to remove this command, since

  • it doesn't handle views, unlike $collStats
  • it's weird that there's two things with the same name in the server
  • not having it would mean we wouldn't have to upkeep it; see SERVER-33434


 Comments   
Comment by Ian Whalen (Inactive) [ 02/Mar/18 ]

deferring thinking about this past 4.0, so kyle.suarez please talk to the DS teams about needing to continue to handle this in 4.0.

Comment by Kyle Suarez [ 22/Feb/18 ]

Either, though I think there might be some weird things that could fall out if we were to replace its internal implementation with running an aggregation:

  • returns a cursor, instead of the current behavior, which I believe is a single document
  • may be some weird response formats depending on if the namespace exists or not (e.g. aggregations on mongos on unknown namespaces have different results than if you were to issue it directly against a mongod)
Comment by Asya Kamsky [ 22/Feb/18 ]

Do you mean remove the command entirely or replace its internal implementation with running $collStats agg stage?

Comment by Kyle Suarez [ 21/Feb/18 ]

Threw this on the Query Team since I dunno who else to give it to. It does seem like a by-product of the $collStats work, though.

Generated at Thu Feb 08 04:33:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.