DATATEAM-626 validation against DB - #30
Open
qiongL910 wants to merge 24 commits into
Open
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
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 pull request introduces a new Prefect workflow for validating submission files against a graph database. The main changes include implementing a validation flow that checks submission files for consistency with the database, supporting both files with and without UUIDs. Additionally, a new Prefect deployment is configured for this validation workflow.
New Prefect validation workflow:
workflows/prefect/validate_submission_against_db.py: Implements a Prefect flow (validate_submission_against_db) that validates submission TSV files against the database, handles UUID insertion if needed, downloads model files, connects to Neo4j, runs validation, and uploads results to S3.prefect.yaml: Adds a deployment configuration for the new validation workflow, including S3 file handling and dependency installation steps.