feat: copy core schema jsons in s3 and keep in sync with docdb #57
Conversation
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
…en processing s3 prefixes
helen-m-lin
changed the title
helen-m-lin
changed the title
jtyoung84
approved these changes
May 31, 2024
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.
closes #55
Utils:
copy_then_overwrite_core_json_files: Copies core jsons to /original_metadata, then update all top level jsons with new metadata.nd.json.sync_core_json_files: Syncs top level jsons with fields from metadata.nd.json. Use md5hash for checking updates.AindPopulateMetadataJsonJob:
copy_then_overwrite_core_json_filesAindIndexBucketJob:
_process_docdb_record: on docdb updates, callsync_core_json_files, orcopy_then_overwrite_core_json_filesif /original_metadata doesn't already exist._process_prefix: If adding new metadata.nd.json to docdb, callcopy_then_overwrite_core_json_files