influxdb/coordinator
Jonathan A. Sternberg 9f26eb7630
Drop NaN values when writing back points
When an NaN value was computed, it would be written back incorrectly as
a string type instead of being omitted. This happened very rarely in the
case that `stddev()` of a single value was computed and only when it was
being done on a new shard.

This correctly drops the value. The reason this wasn't correctly dropped
previously is because NaN values are represented as a `(*float64)(nil)`
which does not equal `nil` so the writeback system thought it was a
non-nil point, but the writer encoded it as a string.

In addition to the above, this also fixes the point writer to report the
number of points actually written rather than the number of points
desired to be written. Previously, if there was an error writing a point
for some reason, the point would be silently dropped, but still recorded
as a point that had been written. Now it reports the number of points
that were written and omits the ones that were dropped.
2018-12-06 10:55:46 -06:00
..
config.go Separate the query engine into a separate package 2017-08-16 13:38:43 -05:00
config_test.go Remove old cluster config options 2016-05-11 12:59:30 -06:00
meta_client.go Merge branch 'master' into ah-truncate-shards 2017-11-28 17:25:31 -07:00
meta_client_test.go Ensure go fmt passes on 1.10/11 2018-08-21 17:39:42 +01:00
points_writer.go TSM: TSMReader.Close blocks until reads complete 2018-04-30 13:46:03 -07:00
points_writer_internal_test.go Fixes issue with point hitting wrong shard 2016-10-19 21:06:29 +01:00
points_writer_test.go Simplify loops 2018-08-05 15:16:33 +01:00
shard_mapper.go Support WHERE time clause in SHOW TAG VALUES 2017-11-06 19:15:01 +00:00
shard_mapper_test.go Support WHERE time clause in SHOW TAG VALUES 2017-11-06 19:15:01 +00:00
statement_executor.go Drop NaN values when writing back points 2018-12-06 10:55:46 -06:00
statement_executor_test.go Drop NaN values when writing back points 2018-12-06 10:55:46 -06:00