Details
-
Task
-
Resolution: Done
-
Major - P3
-
None
-
None
Description
Documentation Request Summary:
listCollections output now includes a UUID to uniquely identify a collection.
Engineering Ticket Description:
It would be very helpful for clients, like replication or sharding, to track collection via a unique id which doesn't change during a rename or restarts. The "id" should be the same across replicas in a set or shards in a sharded cluster. Note: There is already an _id in sharding metadata for a collection but that is not exposed.
Here is an example of output from listCollections with an "id":
> db.runCommand("listCollections")
|
{
|
"collections" : [
|
{
|
"id" : NumberLong("70368744177664"),
|
"name" : "system.indexes",
|
"options" : {}
|
}
|
],
|
"ok" : 1
|
}
|
Attachments
Issue Links
- documents
-
SERVER-15359 Provide "id" of collection
-
- Closed
-
- is duplicated by
-
DOCS-9480 Docs for SERVER-26513: listCollections output should include _id index spec as idIndex
-
- Closed
-