Connector Improvement: Redshift connector dependency on System tables
Answered
Hi,
Currently redshift connector has a hard dependency on having access to below systems tables.
PG_CLASS, PG_NAMESPACE, PG_DATABASE, STV_TBL_PERM
But when we tried to set up this connector to extract data from redshift database under greenhouse application, Greenhouse support does not grant access to these system tables. Can we have this dependency removed in fivetran redshift connector.
Regards,
Srikar
OneTrust
-
Official comment
Hi Sirkar and Michael,
Because Redshift doesn’t expose an easy way to log updates, we had to retire our connector. The good news is that with the new Connector SDK, you can now use your knowledge of the data model to track updates directly. If you’d like to explore this approach, here’s a Redshift-specific example to get you started:
https://github.com/fivetran/fivetran_connector_sdk/tree/main/examples/source_examples/redshift
Best,
-
We also face this issue, where STV_TBL_PERM is a hard requirement for the connector, but this table is only visible to Redshift Superuser, and good security practices do not allow granting Superuser access to a service account for a SaaS data sync product, no matter how well secured it is. We have proposed some alternate solutions, but they all require development work from the Fivetran side. Looking forward to having this issue resolved!
Please sign in to leave a comment.
Comments
2 comments