Add schema validation before S3 loading #9
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.
Summary
Adds schema validation to the ETL pipeline that runs before loading data to S3. The validation checks that all rows match the expected schema:
If any row fails validation, a
SchemaValidationErrorexception is raised with details about all failing rows, preventing bad data from being uploaded to S3.Review & Testing Checklist for Human
is not Nonechecks, but pandas DataFrames useNaNwhich behaves differently. Test with actual data containing NULL values from the database to ensure validation doesn't incorrectly flag valid rows.docker-compose up -d postgresandpython main.pyto verify validation passes on valid data and correctly rejects invalid data.df.iterrows()which is slow for large DataFrames. If the dataset is large, this may need optimization using vectorized pandas operations.Notes