Fix line protocol parsing equals in measurements and NaN values #3790
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 #3539 partially. NaN cannot be queried though and needs to be handled by the query engine differently.
|
+1 |
jwilder
added a commit
that referenced
this pull request
Aug 21, 2015
Fix line protocol parsing equals in measurements and NaN values
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.
Fixes a regression where measurement names with
=would fail to parse. Also fixes a bug whereNaNcould no be parsed if a timestamp was not also included in the line. TheNaNchange only fixes the parsing. There is still an issue querying forNaNvalues though.Fixes #3539