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

[Feature] Reduce warnings with singular restrict_direct_pg_catalog_access message #915

Closed
3 tasks done
FridayPush opened this issue Sep 20, 2024 · 0 comments · Fixed by dbt-labs/dbt-common#197 or #916
Closed
3 tasks done
Assignees
Labels
behavior_flags enhancement New feature or request

Comments

@FridayPush
Copy link

Is this your first time submitting a feature request?

  • I have read the expectations for open source contributors
  • I have searched the existing issues, and I could not find an existing issue for this feature
  • I am requesting a straightforward extension of existing dbt-redshift functionality, rather than a Big Idea better suited to a discussion

Describe the feature

I have many hundreds of warnings for restrict_direct_pg_catalog_access behavior changes and it makes it impossible to see the warnings I care about related to tests and freshness/etc. Can the warning behavior be adjusted to reduce the messages to once per job run, rather than once per model materialization.

Describe alternatives you've considered

A single warning at the Top of a dbt run, perhaps when the compile step happens or the internal calls to determine if the tables already exist or not is performed.

Who will this benefit?

Administrators of job runs that need to action on Warnings.

Are you interested in contributing this feature?

I'm not able to

Anything else?

No response

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