How to configure a Validation Result store to postgresql

Archive
,
1

This article is for comments to: https://docs.greatexpectations.io/en/latest/guides/how_to_guides/configuring_metadata_stores/how_to_configure_a_validation_result_store_to_postgresql.html?highlight=results%20store

Please comment +1 if this How to is important to you.

1 Like
2

This how-to guide uses the class DatabaseStoreBackend as the store_backend for validation results.

It was tested only with Postgres. If you want to store your Validation Results in a different database, please test this class - it might work without any modifications. If modifications are required, contributing your changes back to the open source is more than welcome.

3

Please find the updated link , the earlier link is broken

1 Like
4

@milan Thank you for noticing! The link was out of date after some documentation refactoring. I fixed the URL.

1 Like
5

I was speaking with Ben on Slack and he mentioned I should post here about an enhancement we feel users may get some value from. Often times, schemas are used to segregate tables in postgres according to functional area - it would be nice to support specification of a schema for the database backend. I’ve submitted a PR to implement this behavior: https://github.com/great-expectations/great_expectations/pull/2058/commits

1 Like
6

@GTLangseth This sounds like an excellent suggestion to me. I’ll review the PR this week.