RedisTimeSeries/RedisTimeSeries#722

The create API is missing some options from the official documentation, namely CHUNK_SIZE and ON_DUPLICATE.

Hi,
I cannot select the db, how would it be possible?

Another issue for use in production in my case, the constructors provided with the library does not allow passing a username for connecting to a Redis 6 instance whose connection is made with a username/password couple and not only a password.

I think it's more a question than an issue but it seems there is something that could be at least documented in the library documentation.

When you use range or mrange, the type for from and to parameters is long. My question is how to use the special characters - and + to respectively to express the minimum possible timestamp and the maximum possible timestamp.

I guess using 0 and a very large number should work the same but I thought it was worth creating an issue to at least improve the documentation.

RedisTimeSeries/RedisTimeSeries#143

This client library does not support initializing a client from a connection string or URI. For instance, in an app I am working on, I receive a Redis connection string as input. Due to the lack of support for such input in the client library, I have to parse the String by myself or change the way connection data are passed.

All libraries I know support passing a connection String to initialize a connection to a database. Adding support should be quite easy since the underlying Jedis library that is used supports the use case. If you agree to fix this issue, the main issue is whether you prefer to support a String, a URI, or both as input.

Few functions mrange and mrevrange takes in primitive type long rather than Long, as a result when the user passes null the value becomes 0 due to the primitive nature.

Ref RedisTimeSeries/RedisTimeSeries#267

As of RedisTimeseries >= 1.4 You can now add samples to a time series where the time of the sample is older than the newest sample in the series. Bundled with that, we now have a policy that will define handling of duplicate samples, and that needs to be supported on the client via the arguments [DUPLICATE_POLICY policy] on TS.CREATE and via [ON_DUPLICATE policy] on TS.ADD. The following are the possible policies:

• BLOCK - an error will occur for any out of order sample
• FIRST - ignore the new value
• LAST - override with latest value
• MIN - only override if the value is lower than the existing value
• MAX - only override if the value is higher than the existing value

Further reference: documentation link

TS.DEL

Delete data points for a given timeseries and interval range in the form of start and end delete timestamps.

The given timestamp interval is closed (inclusive), meaning start and end data points will also be deleted.

TS.DEL key fromTimestamp toTimestamp

• key - Key name for timeseries

• fromTimestamp - Start timestamp for the range deletion.
• toTimestamp - End timestamp for the range deletion.

Complexity

TS.DEL complexity is O(n).

n = Number of data points that are in the requested range

Delete range of data points example

TS.DEL temperature:2:32 1548149180000 1548149183000

1.2.1 and even 1.3.0-snapshot don't support alter functions. When is the date to release a version to support the functions?

This test is occasionally failing for me when running locally, seems flaky:

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running com.redislabs.redistimeseries.RedisTimeSeriesTest
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Tests run: 12, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.495 sec <<< FAILURE! - in com.redislabs.redistimeseries.RedisTimeSeriesTest
testIncDec(com.redislabs.redistimeseries.RedisTimeSeriesTest)  Time elapsed: 0.019 sec  <<< ERROR!
redis.clients.jedis.exceptions.JedisDataException: TSDB: for incrby/decrby, timestamp should be newer than the lastest one
	at com.redislabs.redistimeseries.RedisTimeSeriesTest.testIncDec(RedisTimeSeriesTest.java:322)


Results :

Tests in error:
  RedisTimeSeriesTest.testIncDec:322 » JedisData TSDB: for incrby/decrby, timest...

Tests run: 12, Failures: 0, Errors: 1, Skipped: 0

Hey currently JRedisTimeseries doesn't have support for choosing a Redis Database.

I get that since you can create a RedisTimeseries Object by passing a Jedis Pool, and you can only select a database index after using getResource() from the JedisPool, you might not be able to add a index from using that constructor. But is it possible to add an attribute to this class for selecting a database index?

I am using redis version 6.0.1 running via docker (docker run -p 6379:6379 -it --rm redislabs/redistimeseries)

I am trying to get an daily sum aggregate of values on a given key via:

rts.range(key, LocalDateTime.now().minusDays(1).toInstant(ZoneOffset.ofHours(2)).toEpochMilli(),LocalDateTime.now().toInstant(ZoneOffset.ofHours(2)).toEpochMilli(), Aggregation.SUM, 863400000);

The result is an array having 2 values. This is different from running the same TS.RANGE command directly via redis which will produce only a single data value.

Below screenshot shows values in intelij

result in redisinsight

Sample repo having : JRedisTimeSeriesUserDepositTest class replicating issue above .

https://github.com/borgrodrick/JRedisTimeSeries.git

RedisTimeSeries/RedisTimeSeries#801

Detailed TS.RANGE args with the new ALIGN feature

TS.RANGE key fromTimestamp toTimestamp [FILTER_BY_TS TS1 TS2 ..] [FILTER_BY_VALUE min max] [COUNT count] [ALIGN value] [AGGREGATION aggregationType timeBucket]
TS.REVRANGE key fromTimestamp toTimestamp [FILTER_BY_TS TS1 TS2 ..] [FILTER_BY_VALUE min max] [COUNT count] [ALIGN value] [AGGREGATION aggregationType timeBucket]

Detail of ALIGN docs

• ALIGN - Time bucket alignment control for AGGREGATION. This will control the time bucket timestamps by changing the reference timestamp on which a bucket is defined.
  Possible values:

  • start or -: The reference timestamp will be the query start interval time (fromTimestamp).
  • end or +: The reference timestamp will be the signed remainder of query end interval time by the AGGREGATION time bucket (toTimestamp % timeBucket).
  • A specific timestamp: align the reference timestamp to a specific time.

  Note: when not provided alignment is set to 0.

Sample behaviour:

( first ingestion )

127.0.0.1:6379> ts.add serie1 1 10.0
(integer) 1
127.0.0.1:6379> ts.add serie1 3 5.0
(integer) 3
127.0.0.1:6379> ts.add serie1 11 10.0
(integer) 11
127.0.0.1:6379> ts.add serie1 21 11.0
(integer) 21

Old behaviour and the default behaviour when no ALIGN is specified ( aligned to 0 ):

127.0.0.1:6379> ts.range serie1 1 30 AGGREGATION COUNT 10
1) 1) (integer) 0
   2) 2
2) 1) (integer) 10
   2) 1
3) 1) (integer) 20
   2) 1

Align to the query start interval time (fromTimestamp)

127.0.0.1:6379> ts.range serie1 1 30 ALIGN start AGGREGATION COUNT 10
1) 1) (integer) 1
   2) 2
2) 1) (integer) 11
   2) 1
3) 1) (integer) 21
   2) 1

Align to the query end interval time (toTimestamp). The reference timestamp will be the signed remainder of query end interval time by the AGGREGATION time bucket (toTimestamp % timeBucket).

127.0.0.1:6379> ts.range serie1 1 30 ALIGN end AGGREGATION COUNT 10
1) 1) (integer) 0
   2) 2
2) 1) (integer) 10
   2) 1
3) 1) (integer) 20
   2) 1

Align to a timestamp

127.0.0.1:6379> ts.range serie1 1 30 ALIGN 1 AGGREGATION COUNT 10
1) 1) (integer) 1
   2) 2
2) 1) (integer) 11
   2) 1
3) 1) (integer) 21
   2) 1

Duplicated issue because of internet connection instability... Please see: #79

Hi,
I cannot select the db, how would it be possible?

Expected argument extension to TS.MRANGE: GROUPBY <label> REDUCE <reducer>

TS.MRANGE 1451679382646 1451682982646 WITHLABELS 
AGGREGATION MAX 60000 
FILTER measurement=cpu 
      fieldname=usage_user 
      hostname=(host_9,host_3,host_5,host_1,host_7,host_2,host_8,host_4)
GROUPBY hostname REDUCE MAX

Documentation extension:

• GROUPBY - Aggregate results across different time series, grouped by the provided label name.
  For OSS clustered databases, RedisGears is required to be present.

  When combined with AGGREGATION the groupby/reduce is applied post aggregation stage.

  • label - label name to group series by.

  • reducer - Reducer type used to aggregate series that share the same label value. Available reducers: sum, min, max.

  • Note: The resulting series will contain 3 labels with the following label array structure:

    • <label>=<groupbyvalue> : containing the label name and label value.
    • __reducer__=<reducer> : containing the used reducer.
    • __source__=key1,key2,key3 : containing the source time series used to compute the grouped serie.

Example of the above features:

Query time series with metric=cpu, group them by metric_name reduce max

127.0.0.1:6379> TS.ADD ts1 1 90 labels metric cpu metric_name system
(integer) 1
127.0.0.1:6379> TS.ADD ts1 2 45
(integer) 2
127.0.0.1:6379> TS.ADD ts2 2 99 labels metric cpu metric_name user
(integer) 2
127.0.0.1:6379> TS.MRANGE - + WITHLABELS FILTER metric=cpu GROUPBY metric_name REDUCE max
1) 1) "metric_name=system"
   2) 1) 1) "metric_name"
         2) "system"
      2) 1) "__reducer__"
         2) "max"
      3) 1) "__source__"
         2) "ts1"
   3) 1) 1) (integer) 1
         2) 90
      2) 1) (integer) 2
         2) 45
2) 1) "metric_name=user"
   2) 1) 1) "metric_name"
         2) "user"
      2) 1) "__reducer__"
         2) "max"
      3) 1) "__source__"
         2) "ts2"
   3) 1) 1) (integer) 2
         2) 99

I'm using spring data redis with the Jedis client, and I would like to be able to provide a connection from that pool to RedisTimeSeries class. I couldn't find a way to do that because getConnection is currently private.

Changes to TS.MRANGE / MREVRANGE

SELECTED_LABELS allows to request only a subset of the key-value pair labels of a serie.
An important note is that SELECTED_LABELS and WITHLABELS are mutualy exclusive.

TS.MRANGE fromTimestamp toTimestamp
          [FILTER_BY_TS TS1 TS2 ..]
          [FILTER_BY_VALUE min max]
          [COUNT count]
          [WITHLABELS | SELECTED_LABELS label1 ..]
          [AGGREGATION aggregationType timeBucket]
          FILTER filter..
          [GROUPBY <label> REDUCE <reducer>]

TS.MREVRANGE fromTimestamp toTimestamp
          [FILTER_BY_TS TS1 TS2 ..]
          [FILTER_BY_VALUE min max]
          [COUNT count]
          [WITHLABELS | SELECTED_LABELS label1 ..]
          [AGGREGATION aggregationType timeBucket]
          FILTER filter..
          [GROUPBY <label> REDUCE <reducer>]

More detailed args specs:

* WITHLABELS - Include in the reply the label-value pairs that represent metadata labels of the time series. If `WITHLABELS` or `SELECTED_LABELS` are not set, by default, an empty Array will be replied on the labels array position.
* SELECTED_LABELS - Include in the reply a subset of the label-value pairs that represent metadata labels of the time series. This is usefull when you have a large number of labels per serie but are only interested in the value of some of the labels. If `WITHLABELS` or `SELECTED_LABELS` are not set, by default, an empty Array will be replied on the labels array position.

Example:

Query time series with metric=cpu, but only reply the team label

127.0.0.1:6379> TS.ADD ts1 1 90 labels metric cpu metric_name system team NY
(integer) 1
127.0.0.1:6379> TS.ADD ts1 2 45
(integer) 2
127.0.0.1:6379> TS.ADD ts2 2 99 labels metric cpu metric_name user team SF
(integer) 2
127.0.0.1:6379> TS.MRANGE - + SELECTED_LABELS team FILTER metric=cpu
1) 1) "ts1"
   2) 1) 1) "team"
         2) "NY"
   3) 1) 1) (integer) 1
         2) 90
      2) 1) (integer) 2
         2) 45
2) 1) "ts2"
   2) 1) 1) "team"
         2) "SF"
   3) 1) 1) (integer) 2
         2) 99

Since RedisTimeSeries 1.4 we've added the ability to back-fill time series, with different duplicate policies.

However, we still see several issues being raised on the core repo/client repo that point to users no being aware of it. Example: RedisTimeSeries/redistimeseries-py#86

We should address this by adding examples and further notes about duplicate policy.
You can check our docs about duplicate policy here: https://oss.redislabs.com/redistimeseries/configuration/#duplicate_policy.

Sample Readme of python client with an example of the expected outcome of this documentation/examples task:
https://github.com/RedisTimeSeries/redistimeseries-py#further-notes-on-back-filling-time-series

Using the library, I cannot find a way to close the internal connection(s) properly (e.g. a close or shutdown method). That's quite a real issue for use in production.

I can find the TS.INCRBY/TS.DECRBY command with key value and TIMESTAMP. Is there a option to add these along with LABELS ?

As per the documentation https://oss.redislabs.com/redistimeseries/commands/ am looking for below command.

TS.INCRBY key value [TIMESTAMP timestamp] [LABELS label value..] .

Hi, I would like to know if Redis Pipelining will be supported in the future. This would be great for reducing network costs 👍

Will there be cluster mode support in the future? And if so, when will it be approximately?

Hi,

Is REDIS cluster connection supported using this library ?