-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
ALL
-
-
Sharding NYC 2023-02-06, Sharding NYC 2023-02-20, Sharding NYC 2023-03-06, Sharding NYC 2023-03-20, Sharding NYC 2023-04-03, Sharding NYC 2023-04-17, Sharding NYC 2023-05-01, Sharding NYC 2023-05-15, Sharding NYC 2023-05-29, Sharding NYC 2023-06-12, Sharding NYC 2023-06-26, Sharding NYC 2023-07-10, Sharding NYC 2023-07-24
-
(copied to CRM)
-
3
If an update to a document's shard key value changes the shard that owns the document, the update transparently spawns a transaction to delete the document and insert it on its new owning shard with the update modifications. This transaction will use the current value of the document as the query for the transactional delete, and this will fail if the document contains a "$" prefixed field that isn't a valid query operator, e.g. $date. Confusingly for users this will not fail if the update does not require spawning a transaction.