-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
1
-
🟦 Shard Catalog
-
None
-
None
-
None
-
None
-
None
-
None
The createCollection() method is high level utility encapsulating a few preliminary steps (parameter validation, timeseries namespace handling and lock acquisition), followed by the proper invocation to the local catalog's homonymous function for dispatching the creation.
While the local catalog's createCollection can already accept and apply a fromMigrate setting (which is explicitly passed in as a dedicated parameter), the utility method has no way to specify it: this is problematic for operations that want to hide the creation of temporary collections from change stream readers (like convertToCapped).
The objective of this ticket is to close such a gap: while one option could be the addition of a dedicated fromMigrate parameter to the utility method signature, a more expensive alternative (which would guarantee consistency with similar DDLs, see renameCollection) would imply the definition of a fromMigrate field within the CollectionOptions struct.