fix: Fixing microsecond precision constant for v1 (#49) #47
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
vlastahajek
changed the title
vlastahajek
force-pushed
the
fix/precision_param
branch
from
236d79d to
75e2bc3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Although write protocol is the same for both InflluxDB v1 and v2, there is an incompatibility in precision constant for microseconds used in the write URL,
ufor v1 vs.usfor v2.Unfortunately, due to the InfluxDB v1 issue #17622, the wrong precision constant is not reported back.
This fix creates a workaround for that. Fixes #49