-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Sharding EMEA 2023-10-02, Sharding EMEA 2023-10-16
-
135
The 'temp' property of collections is a replica-set level concept – it is not sharding-aware. As we prepare to support $out to collections tracked on the sharding catalog (unsplittable collections in the contest of PM-3229, and sharded collections later on PM-1931), $out can no longer use on 'temp: true' on sharded clusters. Instead, on shard servers, $out will write down the temporary collections it uses to a collection, and these will be garbage-collected on step-up.
- causes
-
SERVER-82810 dropAggTempCollections should accept NamespaceNotFound errors due to the db having been dropped
- Closed
- is depended on by
-
SERVER-79661 Make "internalRenameIfOptionsAndIndexesMatch" command sharding-aware
- Closed