UN-2476 [FEAT] Enhanced file deduplication in ETL/Task pipelines to ensure files with identical content but different names or folders are all processed#1369
Merged
chandrasekharan-zipstack merged 2 commits intoJun 18, 2025
Merged
Conversation
chandrasekharan-zipstack
approved these changes
Jun 18, 2025
chandrasekharan-zipstack
left a comment
Contributor
There was a problem hiding this comment.
LGTM - however try to address the minor comments
Contributor
|
|
vishnuszipstack
approved these changes
Jun 18, 2025
pk-zipstack
pushed a commit
that referenced
this pull request
Aug 20, 2025
…nsure all unique files are processed (#1369) * logic change for deduplication from contenthash to file * Removed unused flag; added comments for future reference
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
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.



What
ETL/Taskpipelines only).file_historyschema to store file path, adds unique constraints for combinations of hash/provider UUID and file path.workflow_file_execution.Why
file_historyfor legacy/older records, resulting in potential duplicate processing and poor deduplication.How
file_historyusing both content hash/provider UUID and file path.file_historywithout file path, and then attempts to backfill the file path fromworkflow_file_execution.file_pathcolumn tofile_history.Can this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)
Database Migrations
file_pathtofile_history.Env Config
Relevant Docs
Related Issues or PRs
Dependencies Versions
Notes on Testing
Screenshots
Checklist
I have read and understood the Contribution Guidelines.