These APIs require a measurement, permitting an additional optimization
to reduce the search space against the TSM index. Specifically, the
search key prefix is extended from `org+bucket` to
`org+bucket,\x00=<measurement>`
* MeasurementNames
* MeasurementTagKeys
* MeasurementTagValues
* Adds an api to the models package for efficiently parsing the
measurement tag (\x00) from a normalized series key
* feat(sampledata): Add readableRetention to buckets remove ruleString
* feat(sampledata): Add new demodata bucket type and card
* feat(sampledata): Fix buckets in test
* feat(sampledata): Return empty array if demodata bucket fetching errors
* feat(sampledata): Do cleanup
* feat(sampledata): Make components more readable
The root cause is that the Unsigned data type has no representation
in the valueType function in the cache and falls back to the default
case of 0.
0 is also a sentinel value in the entry#add function that will
result in skipping the value type check.
It therefore is possible that unsigned values followed by some other
data type is stored in the cache.
It is suspected that the write may be rejected before reaching the
cache, and therefore may not occur in practice. Specifically, the
series file stores the data types on a per-series basis and would
reject the write.
This commit turns the value types into explicit constants and
ensures all existing block types are represented. In addition,
it adds a mapping function to convert these to a known Block type,
which will be used by the `MeasurementFields` schema request to
determine the type of a series in the cache.
At the moment, the default session length only gets set to the default
when no service config is specified. So if a service config is used and
it does not set a value for the session length, then the session length
will be zero.
This modifies the creation of the kv service so that it will set the
default session length if the session length is set to zero (the default
value) instead of only doing it when no service config is specified.
fields that are often re-updated but rarely change value were moved out of react state
and into internal component state. changing these values won't force re-renders.
The prometheus project doesn't adhere to the module suffix so any
attempt to use it as a library fails with go 1.13 or greater. The
workaround is to `go get` a specific commit revision that corresponds to
a tag and let go figure out a pseudo-version for it.
In this case, I updated the revision to the one pointed at by `v2.9.2`
since that is what the current `go.mod` file pointed at. I also updated
the go version to 1.13 inside of `go.mod` to be the same as influxdb.
See https://github.com/prometheus/prometheus/issues/6048 for details.
Yiqun (Ethan) Zhang
Jonathan A. Sternberg
Ariel Salem
Alex Boatwright
Vlasta Hajek
George
Gianluca Arbezzano
Pavel Zavora
Johnny Steenbergen
Stuart Carnie
Brandon Farmer
Gavin Cabbage
Lorenzo Affetti
Deniz Kusefoglu
Jakub Bednář
Alirie Gray
Bucky Schwarz
kelwang
Kelvin Wang