Verify that non key columns exist in each dataset #517
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
- The non existence of non key columns was resulting in a Spark SQL exception, instead of a graceful "ComparisonFailed" return value. - In a future PR, will consolidate all the column validation logic into one single place.
mentekid
approved these changes
Oct 27, 2023
rdsharma26
added a commit
that referenced
this pull request
Oct 27, 2023
* Verify that non key columns exist in each dataset - The non existence of non key columns was resulting in a Spark SQL exception, instead of a graceful "ComparisonFailed" return value. - In a future PR, will consolidate all the column validation logic into one single place. * Fix failing build due to formatting issues.
javierdlrm
pushed a commit
to javierdlrm/deequ
that referenced
this pull request
Oct 31, 2023
* Verify that non key columns exist in each dataset - The non existence of non key columns was resulting in a Spark SQL exception, instead of a graceful "ComparisonFailed" return value. - In a future PR, will consolidate all the column validation logic into one single place. * Fix failing build due to formatting issues.
rdsharma26
added a commit
that referenced
this pull request
Nov 1, 2023
* Verify that non key columns exist in each dataset - The non existence of non key columns was resulting in a Spark SQL exception, instead of a graceful "ComparisonFailed" return value. - In a future PR, will consolidate all the column validation logic into one single place. * Fix failing build due to formatting issues.
rdsharma26
added a commit
that referenced
this pull request
Apr 16, 2024
* Verify that non key columns exist in each dataset - The non existence of non key columns was resulting in a Spark SQL exception, instead of a graceful "ComparisonFailed" return value. - In a future PR, will consolidate all the column validation logic into one single place. * Fix failing build due to formatting issues.
rdsharma26
added a commit
that referenced
this pull request
Apr 16, 2024
* Verify that non key columns exist in each dataset - The non existence of non key columns was resulting in a Spark SQL exception, instead of a graceful "ComparisonFailed" return value. - In a future PR, will consolidate all the column validation logic into one single place. * Fix failing build due to formatting issues.
rdsharma26
added a commit
that referenced
this pull request
Apr 16, 2024
* Verify that non key columns exist in each dataset - The non existence of non key columns was resulting in a Spark SQL exception, instead of a graceful "ComparisonFailed" return value. - In a future PR, will consolidate all the column validation logic into one single place. * Fix failing build due to formatting issues.
rdsharma26
added a commit
that referenced
this pull request
Apr 17, 2024
* Verify that non key columns exist in each dataset - The non existence of non key columns was resulting in a Spark SQL exception, instead of a graceful "ComparisonFailed" return value. - In a future PR, will consolidate all the column validation logic into one single place. * Fix failing build due to formatting issues.
This pull request was closed.
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.
Description of changes:
Issue #, if available: N/A
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.