Include access_role value in genomic sequencing ETL
#330
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
An `access_role` column was recently added to the `sample`, `sequencing_read_set`, `genomic_sequence`, and `consensus_genome` tables of the `warehouse` schema to allow data with restricted access to be included in these tables. These changes include `access_role` in the appropriate class definitions, and updates ETLs to propagate the `access_role` value from a `sample` record to the related sequencing records. The sample record will continue server as the primary `access_role` value, but must also be stored in each table that uses row level security.
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.
An
access_rolecolumn was recently added to thesample,sequencing_read_set,genomic_sequence, andconsensus_genometables of thewarehouseschema to allow data with restricted access to be included in these tables. These changes includeaccess_rolein the appropriate class definitions, and updates ETLs to propagate theaccess_rolevalue from asamplerecord to the related sequencing records.The sample record will continue server as the primary
access_rolevalue, but must also be stored in each table that uses row level security.