Info

Create a shard collection with key that isn't _id. $merge writes will send things to the DLQ with: { _id: ObjectId("651d8464f0b07ba2ac0ce8a3"), _stream_meta: { timestamp: ISODate("2023-10-04T15:27:32.278Z") } , errInfo: { reason: 'Failed to process an input document in the current batch in MergeOperator with error: Failed to target upsert by query :: could not extract exact shard key: generic server error' } }

Top User Comments

xgen-internal-githook commented on Thu, 4 Jan 2024 05:59:40 +0000: Author: {'name': 'Sandeep Dhoot', 'email': 'sandeep.dhoot@mongodb.com', 'username': 'sandeepgd'} Message: SERVER-81862: Remove streams_auth test suite. GitOrigin-RevId: ff6e453f7b78deb1b38c8ed17ea83ee44e1429c5 Branch: master https://github.com/mongodb/mongo/commit/937c16dac516fe5c0f08daa823096e55501ee169 JIRAUSER1272673 commented on Wed, 6 Dec 2023 22:03:00 +0000: yoonsoo.kim@mongodb.com Yeah, this is done. Closing it now. Thanks! JIRAUSER1258488 commented on Wed, 6 Dec 2023 21:34:15 +0000: sandeep.dhoot@mongodb.com, is this supposed to be closed? I have a BF depending on this ticket and wanted to make sure that this is actually closed. xgen-internal-githook commented on Wed, 29 Nov 2023 07:38:58 +0000: Author: {'name': 'Sandeep Dhoot', 'email': 'sandeep.dhoot@mongodb.com', 'username': 'sandeepgd'} Message: SERVER-81862: [streams] Make content-based routing work for sharded collections. Branch: master https://github.com/mongodb/mongo/commit/c465e20138b275940a2e8c1c09fd010fe697b819 JIRAUSER1272673 commented on Sat, 7 Oct 2023 04:51:23 +0000: Still need to figure out a proper fix for this. But possibly the error goes away if we specify the shard key in $merge.on. Confirming this. It also seems like server team recently worked on making this work even when the shard key is not specified in the incoming write. But it seems more efficient to always specify shard key for sharded collections.

Steps to Reproduce