influxdb/src/query: Send uints as unsigned integers on the line protocol (u
suffix instead of i
)
#113
+4
−3
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.
Description
Currently, we serialize
u8
/u16
/u32
/u64
fields as signed integers in the line protocol (e.g.82i
). This changes them to send as unsigned integers (e.g.82u
)It might make sense for this be opt-in behavior, or at the very least a breaking change as far as semver is concerned (e.g. v0.6.0); unsigned integer support wasn't merged into influxdb until 1.4.0, so users with sufficiently old versions of influxdb could have a bad experience.
Quick note - I did run clippy and it fails on a few things, but nothing I changed. I can include fixes if desired, but I didn't want to tack on unrelated changes that might be considered out of scope - let me know!
Checklist
cargo fmt --all
cargo clippy --manifest-path influxdb/Cargo.toml --all-targets --no-default-features --features use-serde,derive,reqwest-client -- -D warnings
cargo clippy --manifest-path influxdb/Cargo.toml --all-targets --no-default-features --features use-serde,derive,hyper-client -- -D warnings
cargo readme -r influxdb -t ../README.tpl > README.md