Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[mongo] skip explain administrative aggregation pipeline #18844

Merged
merged 3 commits into from
Oct 28, 2024

Conversation

lu-zhengda
Copy link
Contributor

What does this PR do?

This PR skips explain plan collection for mongo administrative aggregation pipeline, including $collStats, $currentOp, $indexStats and $sample.

Motivation

Additional Notes

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Changelog entries must be created for modifications to shipped code
  • Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
  • If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

Copy link

codecov bot commented Oct 15, 2024

Codecov Report

Attention: Patch coverage is 91.66667% with 1 line in your changes missing coverage. Please review.

Project coverage is 87.87%. Comparing base (8d5b9cd) to head (02530ac).
Report is 53 commits behind head on master.

Additional details and impacted files
Flag Coverage Δ
activemq ?
ignite ?
mongo 93.26% <91.66%> (-0.25%) ⬇️
presto ?

Flags with carried forward coverage won't be shown. Click here to find out more.

@lu-zhengda lu-zhengda changed the title [mongo] skip explain administrative ggregation pipeline [mongo] skip explain administrative aggregation pipeline Oct 15, 2024
@lu-zhengda lu-zhengda added this pull request to the merge queue Oct 28, 2024
Merged via the queue into master with commit dad9502 Oct 28, 2024
42 of 43 checks passed
@lu-zhengda lu-zhengda deleted the zhengda.lu/mongo-explain branch October 28, 2024 14:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants