Skip to content
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

Quarantine data in silver layer #104

Open
sanketkaleda opened this issue Oct 15, 2024 · 2 comments
Open

Quarantine data in silver layer #104

sanketkaleda opened this issue Oct 15, 2024 · 2 comments
Labels
enhancement New feature or request
Milestone

Comments

@sanketkaleda
Copy link

Normally we have a requirement of applying data quality rules from bronze to silver layer, so we would need to qurantine data in silver layer, currently its not supported to add quaratine feature in silver layer. will it be available soon ?

@ravi-databricks
Copy link
Contributor

Usually bronze is entry point where customers do quarantine data and send back to source. We can introduce quarantine feature in silver too. It might be for v0.0.10 release since v.0.0.9 release is finalized

@ravi-databricks ravi-databricks added the enhancement New feature or request label Oct 15, 2024
@ravi-databricks ravi-databricks added this to the v0.0.10 milestone Oct 15, 2024
@sanketkaleda
Copy link
Author

Thanks for accepting it as an enhancement for v0.0.10. In our case, we need to keep bronze layer without applying any data quality rule and send the quality data in silver and quarantine the bad data in silver only. The purpose of quarantine is not to send the data back to source but to have detailed data quality monitoring of rows are rejected. handshake with source system will still be manual and done by respective data product owner.

If we quarantine the data in bronze layer itself then we will loose the idea of keeping As-Is source data in bronze.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants