[SERVER-48052] Pipeline based update invariant failure Created: 08/May/20  Updated: 29/Oct/23  Resolved: 20/May/20

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: 4.5.1
Fix Version/s: 4.7.0

Type: Bug Priority: Major - P3
Reporter: Ian Boros Assignee: Ian Boros
Resolution: Fixed Votes: 0
Labels: qexec-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Query 2020-05-18, Query 2020-06-01
Participants:
Linked BF Score: 5

 Description   

We don't set the 'explain' flag on the ExpressionContext when creating a ParsedUpdate. This means that the DocumentSources used in a pipeline update are parsed with the explain flag set to false, even if the query is an explain. This causes the DocumentSource to be initialized incorrectly and triggers an invariant in getNext().



 Comments   
Comment by Ian Boros [ 12/May/20 ]

david.storch
The invariant which gets triggered does not exist in 4.4 or older, so we're good.

Comment by David Storch [ 12/May/20 ]

ian.boros, to confirm, this does not affect 4.4 or older branches?

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