-
Notifications
You must be signed in to change notification settings - Fork 217
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upload Ingestion Server's TSV files to AWS S3 (skip tags) #4529
Merged
Merged
Changes from 6 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
d37cd3d
Save files of cleaned data to temporary directory and remove extra si…
krysal ab41551
Recreate temporary directory before cleaning
krysal 4dd8e2c
Add stocksnap to TLS_CACHE
krysal b4172e4
Fix test
krysal 97a721a
Upload files to AWS S3 (without tags)
krysal 884f740
Add default values to AWS variables in env.template
krysal 0b9914c
Merge branch 'main' into feat/ing_server_s3_upload_2
krysal eb79075
Add explanatory comment for skipped non-existing files
krysal File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add a comment with the explanation you shared in the other PR for why this is an expected and good condition (not an error)? Otherwise, it's definitely not clear.
Although, I'm actually still not clear.
I understand tags won't have a file. That's fine, but then can we explicitly skip it in the list of files we are looking at? That would be much clearer for that case and implicitly document that we know the tags file does not exist.
However: I don't understand the bit about how these files will over time no longer exist. Why would that happen? Once we've applied the fix upstream, is there a point where the data refresh would have "half fixed" data, and some of the cleaning would stop? That's fine, but I just wanted to clarify, because again it's not clear based on this code, but the condition is a starkly significant one with no explanation, but apparently matters quite a bit (with many implementation details behind the reason for it).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The cleaning steps will remain for a time, let's say two or one data refresh process, until we're confident that nothing is left pending in that ETL. The cleaning won't stop midway by itself, so we'd need to catch these cases when the files aren't produced anymore.
Thanks for raising the flag here. It was clear to me, but now I see I was assuming many things. I added a comment that hopes to add more context to it.