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

fix: change log level since this is a known case #13029

Merged
merged 1 commit into from
May 24, 2024

Conversation

trevorwhitney
Copy link
Collaborator

What this PR does / why we need it:

Change the level of a log message. This can happen when spanning multiple schemas and should not be logged as an error.

Which issue(s) this PR fixes:
Fixes #10771

this can happen when spanning multiple schemas and should not be logged
as an error.
@trevorwhitney trevorwhitney merged commit ca030a5 into main May 24, 2024
60 checks passed
@trevorwhitney trevorwhitney deleted the change-query-size-limit-err-level branch May 24, 2024 07:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

"Query does not fit in a single sharding configuration" after changing schema to TSDB
2 participants