[SERVER-83912] Re-parsing queryStats key when reading queryStats.Status fails on merge_to_referenced_collection.js Created: 05/Dec/23  Updated: 15/Dec/23  Resolved: 15/Dec/23

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

Type: Bug Priority: Major - P3
Reporter: Mariano Shaar Assignee: Alyssa Clark
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-85096 TRACKING: M3 Correctness Tickets Closed
Related
is related to SERVER-75596 Stress $queryStats read path for aggr... Closed
Assigned Teams:
Query Integration
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

This is yet another one in the series of re-parsing failures. This one came up on the query patch for both all feature flags and classic engine all feature flags when testing SERVER-75596. This happened only on the query_stats_mongos_aggregation_passthrough suite in this evergreen patch.

Was not able to re-parse queryStats key when reading queryStats.Status NamespaceNotFound: database merge_to_referenced_coll not found Hash: 10246678213668657820 Query Shape: { cmdNs: { db: \"merge_to_referenced_coll\", coll: \"test\" }, command: \"aggregate\", pipeline: [ { $facet: { y: [ { $lookup: { from: \"TARGET\", as: \"y\", let: {}, pipeline: [] } } ] } }, { $merge: { into: { db: \"merge_to_referenced_coll\", coll: \"TARGET\" }, on: \"_id\", whenMatched: \"merge\", whenNotMatched: \"insert\" } } ] }

 This is the assertion that's failing.



 Comments   
Comment by Githook User [ 15/Dec/23 ]

Author:

{'name': 'Alyssa Clark', 'email': 'alyssa.clark@mongodb.com', 'username': 'awagenmaker'}

Message: SERVER-83912 Skip facet validation requiring catalog when parsing for query stats

GitOrigin-RevId: a4a2450ea411d177b038fd68255052fc655fc79e
Branch: master
https://github.com/mongodb/mongo/commit/e79d3b6928bd9e578af42b2f279cf99a425852c3

Generated at Thu Feb 08 06:53:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.