Feature/spark expectation enhancements#123 #125
Closed
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.
Add Column for Column-Level Visibility in Data Quality Framework Result Table
Description
Schema Evolution with AutoMerge:
Enabled Delta Lake's spark.databricks.delta.schema.autoMerge.enabled configuration to allow schema evolution during write operations.
Modified the data quality framework to include the affected_column_name field dynamically if not already present.
ENHANCEMENT
Motivation and Context
Increased Transparency: Builds trust by providing clear visibility into how data quality rules are applied and which columns are impacted.
Operational Efficiency: Reduces manual intervention and effort required to diagnose data issues, optimizing resource utilization.
How Has This Been Tested?
Ensure backward compatibility is maintained for legacy workflows making sure that exusting pipelines donot break
Screenshots (if appropriate):
Types of changes
Checklist: