Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Won't Do
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Query Execution
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

consider doing something like ~~SERVER-88441~~ but for find, distinct, count, ect

depends on

SERVER-88441 mongos does not appropriately emulate mongod when db does not exist in aggregation commands

Closed

is depended on by

SERVER-82107 Make find command behave the same in replicaset and sharded cluster when db does not exists

Closed

SERVER-87281 find command against non-existent collection with invalid $where on replica set fails with JSInterpreterFailure but the same command sharded cluster does not.

Closed

related to

SERVER-90434 remove TODOs and accept some divergent behavior on non-existant dbs

Closed

Assignee:: Unassigned
Reporter:: Mickey Winters
Participants:: Mickey Winters
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Mar 22 2024 06:21:15 PM UTC
Updated:: May 10 2024 07:54:15 PM UTC
Resolved:: May 10 2024 07:54:02 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates