Fix spanner telemetry #1156
Merged
Fix spanner telemetry #1156
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
fixes the error: failed to decode column 0, destination *int64 cannot support NULL SQL values
ecordell
force-pushed
the
spannertelemetry
branch
from
41ef7f3
to
8a08776
Compare
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.
Noticed an error in the spicedb-operator test logs against spanner:
{"level":"warn","error":"unable to query DB stats: unable to decode row count: spanner: code = \"InvalidArgument\", desc = \"failed to decode column 0, destination *int64 cannot support NULL SQL values\"","time":"2023-01-09T20:21:37Z","message":"unable to initialize telemetry collector"}