-
Type:
New Feature
-
Resolution: Fixed
-
Priority:
Minor - P4
-
Affects Version/s: None
-
Component/s: Change streams
-
None
-
Query Execution
-
Minor Change
-
v8.0, v7.0, v6.0
-
QE 2024-09-02, QE 2024-09-16, QE 2024-09-30
-
200
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
Currently `create` events offer no explicit indication of the type of the namespace that’s been created. Clients have to parse it heuristically:
- If there’s a collection UUID: type=collection.
- Otherwise, if viewOn is a system.buckets collection: type=timeseries.
- Otherwise, type=view.
This means clients have to know about all collection types. So were there to be some new collection type, the logic above would process it as a view. Moreover, a client that doesn’t want to care about time-series collections nonetheless has to filter them out explicitly.
It would seem better all around to add a “type” field to the event.
- causes
-
SERVER-97071 Ensure stability of resumeTokens across versions
-
- Closed
-
- is depended on by
-
TOOLS-3674 Investigate changes in SERVER-88142: Include collection type with `create` events.
-
- Waiting (Blocked)
-
- is related to
-
SERVER-97672 Move nsType field in create and similar events into operationDescription field
-
- Needs Scheduling
-