[SERVER-60171] Investigate test failure in documentKey when match expression optimization is disabled on full cluster Created: 23/Sep/21  Updated: 06/Dec/22  Resolved: 23/Sep/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Rishab Joshi (Inactive) Assignee: Backlog - Query Execution
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query Execution
Operating System: ALL
Participants:

 Description   

When match expression optimization is disabled on whole cluster by adding the code:
 

FixtureHelpers.runCommandOnEachPrimary({ db:db.getSiblingDB("admin"), cmdObj: {configureFailPoint:"disableMatchExpressionOptimization", mode:"alwaysOn"} });

 
 

A failure is seen in the following line where returned document at oplog seems to be 1 but expected is 2.

https://github.com/mongodb/mongo/blob/92738c5fa0e8169299e5393e88159b8cbb9559ca/jstests/change_streams/oplog_rewrite/change_stream_match_pushdown_documentKey_rewrite.js#L149



 Comments   
Comment by Rishab Joshi (Inactive) [ 23/Sep/21 ]

Fixed as part of SERVER-59421

Generated at Thu Feb 08 05:49:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.