Differentiate execution plan checker messages #2295
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It can be difficult to identify the exact issue that makes an execution plan invalid, especially with complex rules with inlined relations, for example. This change differentiates messages for different cases of invalid execution plans, which makes it a bit easier for a user to identify the issue.
Codecov Report
@@ Coverage Diff @@
## master #2295 +/- ##
==========================================
+ Coverage 77.41% 77.47% +0.05%
==========================================
Files 461 461
Lines 28996 29002 +6
==========================================
+ Hits 22447 22468 +21
+ Misses 6549 6534 -15
|
b-scholz
approved these changes
Jul 26, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It can be difficult to identify the exact issue that makes an execution
plan invalid, especially with complex rules with inlined relations, for
example.
This change differentiates messages for different cases of invalid
execution plans, which makes it a bit easier for a user to identify the
issue.