Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Won't Do
Priority: Major - P3
Fix Version/s: Server_Docs_20231030
Affects Version/s: None
Component/s: manual, Server
Labels:
- collector-298ba4e7
- docs-triage
Environment:

Hide

*Location*: https://docs.mongodb.com/manual/reference/database-profiler/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36
*Referrer*: https://www.google.com.au/
*Screen Resolution*: 1440 x 900

Show
*Location*: https://docs.mongodb.com/manual/reference/database-profiler/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 *Referrer*: https://www.google.com.au/ *Screen Resolution*: 1440 x 900

The system.profile.op section lists distinct and count as possible values. However, the actual output from MongoDB 2.6 up to MongoDB 3.4 shows:

> db.system.profile.find()
{
  "op": "command",
  "ns": "test.test",
  "command": {
    "distinct": "test",
    "key": "a",
    "query": {
    ...

which shows that distinct is a command op, and not an op in its own right. This is also the case with count.

The current op list seems to be changed in ~~DOCS-7700~~. Can this list be verified to be correct?