more userfriendly error

Author: Dieterbe

api/dataprocessor.go

@@ -682,7 +682,7 @@ func newRequestContext(ctx context.Context, req *models.Req, consolidator consol
 	// we can argue both ways, but the other thing is that if we apply the logic above, we end up with:
 	// from := 1
 	// to := 1
-	// which is a query not accepted by AggMetric, Ccache or store. (from must < to)
+	// which is a query not accepted by AggMetric, Ccache or store. (from must be less than to)
 	// the only way we can get acceptable queries is for from to be 1 and to to remain 36 (or become 60 or 61)
 	// such a fetch request would include the requested point
 	// but we know Fix() will later create the output according to these rules:

mdata/aggmetric.go

@@ -16,7 +16,7 @@ import (
 	"gopkg.in/raintank/schema.v1"
 )
 
-var ErrInvalidRange = errors.New("AggMetric: invalid range. from must < to")
+var ErrInvalidRange = errors.New("AggMetric: invalid range: from must be less than to")
 var ErrNilChunk = errors.New("AggMetric: unexpected nil chunk")
 
 // AggMetric takes in new values, updates the in-memory data and streams the points to aggregators

mdata/cache/ccache.go

@@ -20,7 +20,7 @@ import (
 var (
 	maxSize         uint64
 	searchFwdBug    = stats.NewCounter32("recovered_errors.cache.metric.searchForwardBug")
-	ErrInvalidRange = errors.New("CCache: invalid range. from must < to")
+	ErrInvalidRange = errors.New("CCache: invalid range: from must be less than to")
 )
 
 func init() {

store/cassandra/store_cassandra.go

@@ -34,7 +34,7 @@ const Table_name_format = `metric_%d`
 
 var (
 	errChunkTooSmall = errors.New("unpossibly small chunk in cassandra")
-	errInvalidRange  = errors.New("CassandraStore: invalid range. from must < to")
+	errInvalidRange  = errors.New("CassandraStore: invalid range: from must be less than to")
 	errReadQueueFull = errors.New("the read queue is full")
 	errReadTooOld    = errors.New("the read is too old")
 	errTableNotFound = errors.New("table for given TTL not found")