🐛 Fix pipeline order in mount_base_pipeline #168
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes the pipeline stage ordering in the
mount_base_pipelinefunction whenpopulate=True. The reference stage was being placed after sort, skip, and limit stages, which could lead to incorrect query results.Changes
reference_stageto execute beforesort_stage,skip_stage, andlimit_stagein the pipelineWhy this matters
The previous order could cause issues when: