SNOW-1868288 log level to debug in chunk rowcount logging #2127
+6
−2
Conversation
This file contains 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
sfc-gh-dszmolka
added
the
DO_NOT_PORT_CHANGES_TO_SP
sfc-gh-mkeller
deleted the
SNOW-1868288-info-to-debug-in-first-chunk-logging
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Please answer these questions before submitting your pull requests. Thanks!
What GitHub issue is this PR addressing? Make sure that there is an accompanying issue to your PR.
SNOW-1868288
Fill out the following pre-review checklist:
Please describe how your code solves the related issue.
Apparently for some workflows (SNOW-1868288: Downgrade cursor.py log level from info to debug #2126), the INFO level of current logging is excessive. Aiming to set it to DEBUG - if needed for troubleshooting, one usually uses verbose loglevels anyways.
(Optional) PR for stored-proc connector: