Create test showcasing bug with enums and index scans #3735
+236
−0
Conversation
This file contains hidden or 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
This adds a test case to showcase the problem with FoundationDB#3734. It modifies `enum.yamsql` with a new test case analogous to the one in the issue. There are two new queries that are planned with an index scan over an index on an enum valued field, and both of them fail with the same `NullPointerException` that is alluded to in the bug report.
…hat they fail" This reverts commit c8dfdd9.
📊 Metrics Diff Analysis ReportSummary
ℹ️ About this analysisThis automated analysis compares query planner metrics between the base branch and this PR. It categorizes changes into:
The last category in particular may indicate planner regressions that should be investigated. New QueriesCount of new queries by file:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 adds a test case to showcase the problem with #3734. It modifies
enum.yamsqlwith a new test case analogous to the one in the issue. There are two new queries that are planned with an index scan over an index on an enum valued field, and both of them fail with the sameNullPointerExceptionthat is alluded to in the bug report.