Unify Point
's and InfluxDBMapper
's POJO saving logic
#979
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.
Currently, there are two duplicate and somewhat divergent versions of this logic:
Point
doesn't check that values conform to field types and doesn't constrain allowed value typesInfluxDBMapper
uses atime
field rather than@TimeColumn
This change unifies the logic and takes the stricter path, which means that it may break existing code that relies on the current lenient logic.