DIG-2080: find analysis date in vcf files#388
Merged
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
2 participants
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.
Add ability to look for a date in a vcf file. This is included as part of the /verify endpoint as well; if a vcf file does not have a date, it will return
Falsefor /verify.When a variantfile's headers are indexed, the analysis_date will be saved in the variantfile table. This date is then saved as part of the metadata in the AnalysisDrsObject.
For previously-ingested files, an admin can run
docker exec -it candigv2_htsget_1 python htsget_server/analysis_date.pyon their instance to update any existing AnalysisDrsObjects. This script actually uses a different optimized query to find all dates in already-ingested headers.Testing is in CanDIG/CanDIGv2#1240