Add feature to define datatype for InfluxDB fields #8
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
|
This might actually fix #6 , maybe? |
|
@blavka is this of interest to you? |
blavka
reviewed
Oct 3, 2019
added 2 commits
October 17, 2019 15:11
|
@blavka sorry from our side for the delay, but now we added a second config file |
blavka
approved these changes
Jan 31, 2020
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.
Hi again :)
We ran into an issue, where the InfluxDB creates a field based on the first value received, if you try to e.g. write
value=1. the field will be created as int. If your datatype then changes, e.g. to1.1, InlfuxDB cannot accept it anymore.That's why it is helpful to be able to specify the datatype right from the beginning, which is what we implemented in this PR. The config is still backwards compatible.
Also, we changed the config.yml file a little bit to reflect the latest changes and document the features (database per point, base64 decoding, HTTP push, explicit datatype per field), so that they're not so "hidden" ;)