Fix CustomSQL test syntax #511
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
rdsharma26
approved these changes
Oct 20, 2023
eycho-am
added a commit
that referenced
this pull request
Oct 20, 2023
javierdlrm
pushed a commit
to javierdlrm/deequ
that referenced
this pull request
Oct 31, 2023
rdsharma26
pushed a commit
that referenced
this pull request
Nov 1, 2023
rdsharma26
pushed a commit
that referenced
this pull request
Apr 16, 2024
rdsharma26
pushed a commit
that referenced
this pull request
Apr 16, 2024
rdsharma26
pushed a commit
that referenced
this pull request
Apr 16, 2024
rdsharma26
pushed a commit
that referenced
this pull request
Apr 17, 2024
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.
Issue #, if available:
Description of changes:
CustomSQL Analyzer test was failing with Spark 3.3.0 with the error:
org.scalatest.exceptions.TestFailedException: "Column 'foo' does not exist. Did you mean one of the following? [primary.Country, primary.Address Line 1, primary.Address Line 2, primary.Address Line 3]; line 1 pos 7;while other versions (3.1.0, 3.4.0) fails with:
"cannot resolve 'foo' given input columns: [primary.Address Line 1, primary.Address Line 2, primary.Address Line 3, primary.Country]; line 1 pos 7;The test was checking that `foo` was in the exception, but for Spark 3.3.0 the error message showed 'foo' instead.
Modifying the test to pass for all versions
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.