influxdb/services/graphite/errors.go

package graphite

import "fmt"

// An UnsupportedValueError is returned when a parsed value is not
// supported.
type UnsupportedValueError struct {
	Field string
	Value float64
}

func (err *UnsupportedValueError) Error() string {
	return fmt.Sprintf(`field "%s" value: "%v" is unsupported`, err.Field, err.Value)
}
Allow NaN as a valid value on the graphite service The canonical graphite implementation will read and discard NaN values instead of throwing an error when reading on the line receiver protocol. Since this is the default behavior for graphite, InfluxDB should have the same behavior for compatibility. Previously, a NaN value would result in an error printed to the console. When you have a large number of NaN values being sent every minute, this results in the log file filling with useless messages. 2015-11-19 19:50:10 +00:00			`package graphite`

			`import "fmt"`

Fix typo from a rename 2016-02-08 11:01:01 +00:00			`// An UnsupportedValueError is returned when a parsed value is not`
			`// supported.`
			`type UnsupportedValueError struct {`
Allow NaN as a valid value on the graphite service The canonical graphite implementation will read and discard NaN values instead of throwing an error when reading on the line receiver protocol. Since this is the default behavior for graphite, InfluxDB should have the same behavior for compatibility. Previously, a NaN value would result in an error printed to the console. When you have a large number of NaN values being sent every minute, this results in the log file filling with useless messages. 2015-11-19 19:50:10 +00:00			`Field string`
			`Value float64`
			`}`

Fix typo from a rename 2016-02-08 11:01:01 +00:00			`func (err *UnsupportedValueError) Error() string {`
Allow NaN as a valid value on the graphite service The canonical graphite implementation will read and discard NaN values instead of throwing an error when reading on the line receiver protocol. Since this is the default behavior for graphite, InfluxDB should have the same behavior for compatibility. Previously, a NaN value would result in an error printed to the console. When you have a large number of NaN values being sent every minute, this results in the log file filling with useless messages. 2015-11-19 19:50:10 +00:00			return fmt.Sprintf(`field "%s" value: "%v" is unsupported`, err.Field, err.Value)
			`}`