materialize-snowflake: add additional table/schema logging#4256
Merged
danielnelson merged 1 commit intomainfrom Apr 16, 2026
Merged
materialize-snowflake: add additional table/schema logging#4256danielnelson merged 1 commit intomainfrom
danielnelson merged 1 commit intomainfrom
Conversation
danielnelson
force-pushed
the
dbn/materialize-snowflake-context-logger
branch
from
dfa1daa to
ef98f0a
Compare
On materializations with many bindings, it can be hard to tell which log message apply to which resource. This adds the table and schema to most snowpipe streaming log messages. By adding the logger to the context we get scope based logging without the need to expand the parameters list to each function.
danielnelson
force-pushed
the
dbn/materialize-snowflake-context-logger
branch
from
ef98f0a to
01d926a
Compare
jacobmarble
approved these changes
Apr 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On materializations with many bindings, it can be hard to tell which log message apply to which resource. This adds the table and schema to most snowpipe streaming log messages.
By adding the logger to the context we get scope based logging without the need to expand the parameters list to each function.
Workflow steps:
No changes
Documentation links affected:
None
Notes for reviewers:
(anything that might help someone review this PR)