We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Both of the following BQ insert jobs in datapipeline_dc_tags.py strip the "customer_purchase" destination tables of their policy tags:
cloud-foundation-fabric/blueprints/data-solutions/data-platform-foundations/demo/datapipeline_dc_tags.py
Line 262 in c918cfc
Line 293 in c918cfc
This occurs because the writeDisposition is set to "WRITE_TRUNCATE" which as the docs state:
This should be fixed because removing policy tags exposes sensitive data and removes the column-level security that policy tags enable.
The text was updated successfully, but these errors were encountered:
datapipeline_dc_tags_flex.py would require the same fix
Sorry, something went wrong.
@lcaggio @iht can you take a look?
In my tests, changing writeDisposition to WRITE_APPEND resolved the issue. I can submit PR fix tomorrow
WRITE_APPEND
There is BigQuery feature request for that. I agree that changing writeDisposition is a way forward for now.
writeDisposition
Successfully merging a pull request may close this issue.
Both of the following BQ insert jobs in datapipeline_dc_tags.py strip the "customer_purchase" destination tables of their policy tags:
cloud-foundation-fabric/blueprints/data-solutions/data-platform-foundations/demo/datapipeline_dc_tags.py
Line 262 in c918cfc
cloud-foundation-fabric/blueprints/data-solutions/data-platform-foundations/demo/datapipeline_dc_tags.py
Line 293 in c918cfc
This occurs because the writeDisposition is set to "WRITE_TRUNCATE" which as the docs state:
This should be fixed because removing policy tags exposes sensitive data and removes the column-level security that policy tags enable.
The text was updated successfully, but these errors were encountered: