diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.0-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.0-release-notes.md index 1ed13e32d2..030efa627b 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.0-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.0-release-notes.md @@ -35,9 +35,9 @@ RedisBloom v2.0.3 requires: We are proud to announce that we doubled the number of probabilistic data structures that are generally available in RedisBloom. Full documentation is available on [redisbloom.io](https://redisbloom.io) - #[70](https://github.com/RedisBloom/RedisBloom/issues/70) Top-K - - [Commands]({{}}) + - [Commands](/content/develop/data-types/probabilistic/top-k.md) - [Algorithm](https://www.usenix.org/conference/atc18/presentation/gong) - #[65](https://github.com/RedisBloom/RedisBloom/issues/65) Count-min Sketch - - [Commands]({{}}) + - [Commands](/content/develop/data-types/probabilistic/count-min-sketch.md) - [Algorithm](https://en.wikipedia.org/wiki/Count%E2%80%93min_sketch) diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.2-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.2-release-notes.md index 04ad729457..eeda773af3 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.2-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.2-release-notes.md @@ -31,7 +31,7 @@ Details: - Bug fixes: - [#481](https://github.com/RedisBloom/RedisBloom/issues/481) CF crashes on expansion 0 - - [#478](https://github.com/RedisBloom/RedisBloom/pull/478) [`BF.INFO`]({{< relref "commands/bf.info" >}}) reports an inaccurate result about the memory footprint + - [#478](https://github.com/RedisBloom/RedisBloom/pull/478) [`BF.INFO`](/content/commands/bf.info.md) reports an inaccurate result about the memory footprint ## v2.2.17 (June 2022) @@ -43,10 +43,10 @@ Details: - Bug fixes: - - [#451](https://github.com/RedisBloom/RedisBloom/pull/451) [`TOPK.INCRBY`]({{< relref "commands/topk.incrby" >}}): fix calculation when old fingerprint count is reduced to 0 - - [#462](https://github.com/RedisBloom/RedisBloom/pull/462) [`CF.RESERVE`]({{< relref "commands/cf.reserve" >}}): fix potential crash on incorrect number of parameters - - [#434](https://github.com/RedisBloom/RedisBloom/pull/434) [`CF.INSERT`]({{< relref "commands/cf.insert" >}}): fix crash when capacity is negative - - [#450](https://github.com/RedisBloom/RedisBloom/pull/450) [`TOPK.INCRBY`]({{< relref "commands/topk.incrby" >}}): limit increment to 100,000 to prevent potential long freezes + - [#451](https://github.com/RedisBloom/RedisBloom/pull/451) [`TOPK.INCRBY`](/content/commands/topk.incrby.md): fix calculation when old fingerprint count is reduced to 0 + - [#462](https://github.com/RedisBloom/RedisBloom/pull/462) [`CF.RESERVE`](/content/commands/cf.reserve.md): fix potential crash on incorrect number of parameters + - [#434](https://github.com/RedisBloom/RedisBloom/pull/434) [`CF.INSERT`](/content/commands/cf.insert.md): fix crash when capacity is negative + - [#450](https://github.com/RedisBloom/RedisBloom/pull/450) [`TOPK.INCRBY`](/content/commands/topk.incrby.md): limit increment to 100,000 to prevent potential long freezes ## v2.2.15 (May 2022) @@ -83,7 +83,7 @@ Details: - Bug fixes: - - [#392](https://github.com/RedisBloom/RedisBloom/pull/392) Fixed a potential crash on Bloom filter expansion when loading from [AOF]({{< relref "/operate/oss_and_stack/management/persistence" >}}) + - [#392](https://github.com/RedisBloom/RedisBloom/pull/392) Fixed a potential crash on Bloom filter expansion when loading from [AOF](/content/operate/oss_and_stack/management/persistence.md) - [#404](https://github.com/RedisBloom/RedisBloom/pull/404) Fixed a potential crash on Cuckoo filter when calling `CF.LOADCHUNK` on a filter with `EXPANSION` greater than 1 ## v2.2.9 (November 2021) diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.4-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.4-release-notes.md index 14cfd3ed2f..38392b1010 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.4-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.4-release-notes.md @@ -134,11 +134,11 @@ Details: - Bug fixes: - - [#609](https://github.com/RedisBloom/RedisBloom/issues/609) [CF.INFO]({{< relref "commands/cf.info" >}}) - incorrect information for large filters + - [#609](https://github.com/RedisBloom/RedisBloom/issues/609) [CF.INFO](/content/commands/cf.info.md) - incorrect information for large filters - Improvements: - - [#389](https://github.com/RedisBloom/RedisBloom/issues/389) Introduce [BF.CARD]({{< relref "commands/bf.card" >}}) to retrieve the cardinality of a Bloom filter or 0 when such key does not exist + - [#389](https://github.com/RedisBloom/RedisBloom/issues/389) Introduce [BF.CARD](/content/commands/bf.card.md) to retrieve the cardinality of a Bloom filter or 0 when such key does not exist ## v2.4 GA (v2.4.3) (November 2022) @@ -166,15 +166,15 @@ Using t-digest is simple and straightforward: `TDIGEST.CREATE key [COMPRESSION compression]` initializes a new t-digest sketch (and errors if the key already exists). The `COMPRESSION` argument is used to specify the tradeoff between accuracy and memory consumption. The default is 100. Higher values mean more accuracy. - `TDIGEST.ADD key value...` adds new observations (floating-point values) to the sketch. You can repeat calling [TDIGEST.ADD]({{< relref "commands/tdigest.add" >}}) whenever new observations are available. + `TDIGEST.ADD key value...` adds new observations (floating-point values) to the sketch. You can repeat calling [TDIGEST.ADD](/content/commands/tdigest.add.md) whenever new observations are available. * **Estimating fractions or ranks by values** Use `TDIGEST.CDF key value...` to retrieve, for each input **value**, an estimation of the **fraction** of (observations **smaller** than the given value + half the observations equal to the given value). - `TDIGEST.RANK key value...` is similar to [TDIGEST.CDF]({{< relref "commands/tdigest.cdf" >}}), but used for estimating the number of observations instead of the fraction of observations. More accurately it returns, for each input **value**, an estimation of the **number** of (observations **smaller** than a given value + half the observations equal to the given value). + `TDIGEST.RANK key value...` is similar to [TDIGEST.CDF](/content/commands/tdigest.cdf.md), but used for estimating the number of observations instead of the fraction of observations. More accurately it returns, for each input **value**, an estimation of the **number** of (observations **smaller** than a given value + half the observations equal to the given value). - And lastly, `TDIGEST.REVRANK key value...` is similar to [TDIGEST.RANK]({{< relref "commands/tdigest.rank" >}}), but returns, for each input **value**, an estimation of the **number** of (observations **larger** than a given value + half the observations equal to the given value). + And lastly, `TDIGEST.REVRANK key value...` is similar to [TDIGEST.RANK](/content/commands/tdigest.rank.md), but returns, for each input **value**, an estimation of the **number** of (observations **larger** than a given value + half the observations equal to the given value). * **Estimating values by fractions or ranks** diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.6-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.6-release-notes.md index 0edb57b989..63be45ba80 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.6-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.6-release-notes.md @@ -148,8 +148,7 @@ Improvements: - [#664](https://github.com/RedisBloom/RedisBloom/pull/664) `TOPK.ADD`, `TOPK.INCRBY`, and `TOPK.LIST` reply with blob string instead of simple string. -{{}} -- The version inside Redis will be 2.6.3 in semantic versioning. Since the version of a module in Redis is numeric, we could not add a GA flag. - -- Minimal Redis version: 7.2 -{{}} +> [!NOTE] +> - The version inside Redis will be 2.6.3 in semantic versioning. Since the version of a module in Redis is numeric, we could not add a GA flag. +> +> - Minimal Redis version: 7.2 diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.8-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.8-release-notes.md index ba62f22267..88b283a58e 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.8-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.8-release-notes.md @@ -81,7 +81,6 @@ RedisBloom 2.8 introduces improvements and bug fixes. - [#773](https://github.com/RedisBloom/RedisBloom/pull/773) `CMS.MERGE`: reply with an error on overflow and underflow (MOD-6962) - [#720](https://github.com/RedisBloom/RedisBloom/pull/720) `BF` crashes on high error rate (MOD-6268) -{{< note >}} -- The version inside Redis will be 2.8.2 in semantic versioning. Since the version of a module in Redis is numeric, we could not add a GA flag. -- Minimal Redis version: 7.4 -{{}} +> [!NOTE] +> - The version inside Redis will be 2.8.2 in semantic versioning. Since the version of a module in Redis is numeric, we could not add a GA flag. +> - Minimal Redis version: 7.4 diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisce/redisos-8.0-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisce/redisos-8.0-release-notes.md index 7a3514de46..eab59b68bc 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisce/redisos-8.0-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisce/redisos-8.0-release-notes.md @@ -138,15 +138,15 @@ Stand alone RediSearch, RedisJSON, RedisTimeSeries, and RedisBloom modules are n - (9) Vector set [preview], a data structure designed for vector similarity search, inspired by sorted set. - These nine components are included in all binary distributions. - - See the [build instructions]({{< relref "/operate/oss_and_stack/install/build-stack" >}}) for information about building from source code. + - See the [build instructions](/content/operate/oss_and_stack/install/build-stack/_index.md) for information about building from source code. - New configuration file: `redis-full.conf`, loads Redis with all components, and contains new configuration parameters for Redis Search and the new data structures. - - New ACL categories: `@search`, `@json`, `@timeseries`, `@bloom`, `@cuckoo`, `@cms`, `@topk`, and `@tdigest` commands are also included in the existing ACL categories such as `@read` and `@write`. See [below]({{< relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisce/redisos-8.0-release-notes/#potentially-breaking-changes-to-acls" >}}) for information about potentially breaking changes. + - New ACL categories: `@search`, `@json`, `@timeseries`, `@bloom`, `@cuckoo`, `@cms`, `@topk`, and `@tdigest` commands are also included in the existing ACL categories such as `@read` and `@write`. See [below](/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisce/redisos-8.0-release-notes.md#potentially-breaking-changes-to-acls) for information about potentially breaking changes. - More than 30 performance and resource utilization improvements. - A new I/O threading implementation, which enables throughput increase on multi-core environments (set with the `io-threads` configuration parameter). - An improved replication mechanism that is more performant and robust. -- New hash commands: [HGETDEL]({{< relref "/commands/hgetdel/" >}}), [HGETEX]({{< relref "/commands/hgetex" >}}), and [HSETEX]({{< relref "/commands/hsetex/" >}}) +- New hash commands: [HGETDEL](/content/commands/hgetdel.md), [HGETEX](/content/commands/hgetex.md), and [HSETEX](/content/commands/hsetex.md) For more details, see the release notes for the [8.0-M01](https://github.com/redis/redis/releases/tag/8.0-m01), [8.0-M02](https://github.com/redis/redis/releases/tag/8.0-m02), [8.0-M03](https://github.com/redis/redis/releases/tag/8.0-m03), [8.0-M04](https://github.com/redis/redis/releases/tag/8.0-m04), and [8.0-RC1](https://github.com/redis/redis/releases/tag/8.0-rc1) releases of Redis Open Source. diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisce/redisos-8.10-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisce/redisos-8.10-release-notes.md index f557fafdab..39c478a10c 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisce/redisos-8.10-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisce/redisos-8.10-release-notes.md @@ -132,7 +132,7 @@ Redis 8.10 introduces new features and performance improvements. - `FAIL` — reject timed-out queries. With `search-workers > 0` (the default), the timeout is enforced preemptively - `RETURN` (default) — return best-effort partial results, without enforcing strictness during post-processing - `RETURN_STRICT` (new) — return best-effort partial results while enforcing the timeout through the post-processing (result) pipeline. Available when `search-workers > 0` - - Queries executed on the main thread (i.e., when `search-workers` is 0) are capped by [`search-_max-foreground-timeout-limit`]({{< relref "/develop/ai/search-and-query/administration/configuration#search-_max-foreground-timeout-limit" >}}) (default `60000` ms). + - Queries executed on the main thread (i.e., when `search-workers` is 0) are capped by [`search-_max-foreground-timeout-limit`](/content/develop/ai/search-and-query/administration/configuration.md#search-_max-foreground-timeout-limit) (default `60000` ms). - [#J1602](https://github.com/RedisJSON/RedisJSON/pull/1602), [#J1603](https://github.com/RedisJSON/RedisJSON/pull/1603), [#J1604](https://github.com/RedisJSON/RedisJSON/pull/1604), [#J1607](https://github.com/RedisJSON/RedisJSON/pull/1607), [#J1618](https://github.com/RedisJSON/RedisJSON/pull/1618) JSONPath extensions (MOD-16274, MOD-16275): - Projection expressions at the top level of a JSONPath query - `==` and `!=` can now compare any literal, including array and object literals diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-1.4-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-1.4-release-notes.md index 3c838a86ac..3e3bf3f656 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-1.4-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-1.4-release-notes.md @@ -382,7 +382,7 @@ redis-server --loadmodule ./redisearch.so GC_POLICY FORK ### Runtime configuration -RediSearch's [configuration]({{}}) is applied via arguments passed to the module at load time. This release introduces the new `FT.CONFIG` command that allows to retrieve the current configuration as well as change it during runtime. +RediSearch's [configuration](/content/develop/ai/search-and-query/administration/configuration.md) is applied via arguments passed to the module at load time. This release introduces the new `FT.CONFIG` command that allows to retrieve the current configuration as well as change it during runtime. ### Unlimited autocomplete results @@ -418,11 +418,11 @@ The `FT.ALTER` command has been introduced, and provides the ability to add new ### Query spelling correction -Query spelling correction, a.k.a "did you mean", is now provided via the `FT.SPELLCHECK` command. It enables generating suggestions for search terms that could be misspelled. For more details see [Query Spelling Correction]({{}}). +Query spelling correction, a.k.a "did you mean", is now provided via the `FT.SPELLCHECK` command. It enables generating suggestions for search terms that could be misspelled. For more details see [Query Spelling Correction](/content/develop/ai/search-and-query/advanced-concepts/spellcheck.md). ### Phonetic matching -Phonetic matching, a.k.a "Jon or John?", is now supported via the `PHONETIC` text field attribute. The terms in such fields are also indexed by their phonetic equivalents, and search results include these by default. For more details see [Phonetic Matching]({{}}). +Phonetic matching, a.k.a "Jon or John?", is now supported via the `PHONETIC` text field attribute. The terms in such fields are also indexed by their phonetic equivalents, and search results include these by default. For more details see [Phonetic Matching](/content/develop/ai/search-and-query/advanced-concepts/phonetic_matching.md). ### More fuzziness in search diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-1.6-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-1.6-release-notes.md index 35443de6e6..ccaf75ea62 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-1.6-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-1.6-release-notes.md @@ -168,7 +168,7 @@ Headlines: - Several performance improvements increasing full-text search queries up to 60% and aggregation queries up to 73%. - Support for aliasing of indices. -- Low-level API in C (and [Rust bindings](https://github.com/RediSearch/redisearch-api-rs)) to make RediSearch embeddable in other Redis modules. [RedisGraph]({{< relref "/operate/oss_and_stack/stack-with-enterprise/deprecated-features/graph" >}}) is the first GA consumer. +- Low-level API in C (and [Rust bindings](https://github.com/RediSearch/redisearch-api-rs)) to make RediSearch embeddable in other Redis modules. [RedisGraph](/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/graph/_index.md) is the first GA consumer. - Forked process Garbage Collection (FORK GC) allows for stable read latencies. Full details: diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.0-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.0-release-notes.md index d817c35a65..8b2c45f768 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.0-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.0-release-notes.md @@ -148,9 +148,9 @@ Details: - Minor additions: - #[1696](https://github.com/redisearch/redisearch/issues/1696) The maximum number of results produced by `FT.AGGREGATE` is now configurable: `MAXAGGREGATERESULTS`. - - #[1708](https://github.com/redisearch/redisearch/issues/1708) [Stemming]({{}}) updated with support of new languages: Basque, Catalan, Greek, Indonesian, Irish, Lithuanian, Nepali. + - #[1708](https://github.com/redisearch/redisearch/issues/1708) [Stemming](/content/develop/ai/search-and-query/advanced-concepts/stemming.md) updated with support of new languages: Basque, Catalan, Greek, Indonesian, Irish, Lithuanian, Nepali. - Minor bugfixes: - - #[1668](https://github.com/redisearch/redisearch/issues/1668) Fixes support of stop words in [tag fields]({{}}). Solves also the following related issues: #[166](https://github.com/redisearch/redisearch/issues/166), #[984](https://github.com/redisearch/redisearch/issues/984), #[1237](https://github.com/redisearch/redisearch/issues/1237), #[1294](https://github.com/redisearch/redisearch/issues/1294). + - #[1668](https://github.com/redisearch/redisearch/issues/1668) Fixes support of stop words in [tag fields](/content/develop/ai/search-and-query/advanced-concepts/tags.md). Solves also the following related issues: #[166](https://github.com/redisearch/redisearch/issues/166), #[984](https://github.com/redisearch/redisearch/issues/984), #[1237](https://github.com/redisearch/redisearch/issues/1237), #[1294](https://github.com/redisearch/redisearch/issues/1294). - #[1689](https://github.com/redisearch/redisearch/issues/1689) Consistency fix and performance improvement when using `FT.SUGGET` with [RSCoordinator](https://github.com/RediSearch/RSCoordinator). - #[1774](https://github.com/redisearch/redisearch/issues/1774) `MINPREFIX` and `MAXFILTEREXPANSION` configuration options can be changed at runtime. - #[1745](https://github.com/redisearch/redisearch/issues/1745) Enforce 0 value for `REDUCER COUNT`. @@ -253,7 +253,7 @@ You can read more details in [the RediSearch 2.0 announcement blog post](https:/ - [#1384](https://github.com/RediSearch/RediSearch/pull/1384): `FT.DROPINDEX`, which by default does not delete documents underlying the index (see deprecated `FT.DROP`). - [#1385](https://github.com/RediSearch/RediSearch/pull/1385): Add index definition to `FT.INFO` response. - [#1097](https://github.com/RediSearch/RediSearch/pull/1097): Add Hindi snowball stemmer. -- The `FT._LIST` command returns a list of all available indices. Note that this is a temporary command, as indicated by the `_` in the name, so it's not documented. We're working on a [`SCAN`]({{< relref "/commands/scan" >}}-like command for databases with many indexes. +- The `FT._LIST` command returns a list of all available indices. Note that this is a temporary command, as indicated by the `_` in the name, so it's not documented. We're working on a [`SCAN`](/commands/scan)-like command for databases with many indexes. - The RediSearch version will appear in Redis as `20000`, which is equivalent to 2.0.0 in semantic versioning. Since the version of a module in Redis is numeric, we cannot explicitly add an GA flag. - RediSearch 2.x requires Redis 6.0 or later. @@ -268,7 +268,7 @@ and index name and a synonym group ID. This ID can be any ASCII string. - RediSearch will not index hashes whose fields do not match an existing index schema. You can see the number of hashes not indexed using `FT.INFO` - `hash_indexing_failures `. The requirement for adding support for partially indexing and blocking is captured here: [#1455](https://github.com/RediSearch/RediSearch/pull/1455). - Removed support for `NOSAVE`. - RDB loading will take longer due to the index not being persisted. -- Field names in the [query syntax]({{}}) are now case-sensitive. +- Field names in the [query syntax](/content/develop/ai/search-and-query/advanced-concepts/query_syntax.md) are now case-sensitive. - Deprecated commands: - `FT.DROP` (replaced by `FT.DROPINDEX`, which by default keeps the documents) - `FT.ADD` (mapped to `HSET` for backward compatibility) diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.10-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.10-release-notes.md index a07e5aa254..e12ee90bdb 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.10-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.10-release-notes.md @@ -337,9 +337,8 @@ Bug fixes (since 2.10.4): Improvements (since 2.10.4): - [#4865](https://github.com/RediSearch/RediSearch/pull/4865) - Add coverage for cleaning garbage entries when indexing missing fields (MOD-7415) -{{< note >}} -- The version inside Redis will be 2.10.5 in semantic versioning. Since the version of a module in Redis is numeric, we could not add a Release Candidate flag. -- Minimal Redis version: 7.4 -- If indexing and querying RedisJSON data structures, this version is best combined with RedisJSON 2.8 (v2.8.2 onwards) -- If one or more fields of a hash key expire after a query begins (using FT.SEARCH or FT.AGGREGATE), Redis does not account for these lazily expired fields. As a result, keys with expired fields may still be included in the query results, leading to potentially incorrect or inconsistent results. -{{< /note >}} +> [!NOTE] +> - The version inside Redis will be 2.10.5 in semantic versioning. Since the version of a module in Redis is numeric, we could not add a Release Candidate flag. +> - Minimal Redis version: 7.4 +> - If indexing and querying RedisJSON data structures, this version is best combined with RedisJSON 2.8 (v2.8.2 onwards) +> - If one or more fields of a hash key expire after a query begins (using FT.SEARCH or FT.AGGREGATE), Redis does not account for these lazily expired fields. As a result, keys with expired fields may still be included in the query results, leading to potentially incorrect or inconsistent results. diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.2-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.2-release-notes.md index 25cad648cb..bccffb4d7c 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.2-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.2-release-notes.md @@ -108,7 +108,7 @@ This is the General Availability release of RediSearch 2.2. #### Searching and indexing JSON documents -This release introduces the ability to [index, query, and full-text search JSON documents]({{}}) using JSONPath queries. +This release introduces the ability to [index, query, and full-text search JSON documents](/content/develop/ai/search-and-query/indexing/_index.md) using JSONPath queries. On the schema creation `FT.CREATE`, it is now possible to map a JSONPath query with a field. When a JSON document is indexed, the value extracted by the JSONPath query is indexed in the given field. @@ -123,9 +123,8 @@ That way, it is possible to understand which part of the query is taking most of With the support of JSON document indexing, it is now possible to map a JSONPath query to an alias. Therefore, it is possible to index the same value in different indexing attributes with different indexing strategies. -{{}} -As of RediSearch v2.2, index `fields` are now known as `attributes` in order to avoid confusion with hash fields. This change impacts the `FT.INFO` command's response, which might break clients. It is advised to upgrade your application to the latest supported Redis clients prior to upgrading to RediSearch 2.2. -{{}} +> [!NOTE] +> As of RediSearch v2.2, index `fields` are now known as `attributes` in order to avoid confusion with hash fields. This change impacts the `FT.INFO` command's response, which might break clients. It is advised to upgrade your application to the latest supported Redis clients prior to upgrading to RediSearch 2.2. ### Details diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.4-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.4-release-notes.md index 499bd49023..bdaef76dca 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.4-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.4-release-notes.md @@ -227,21 +227,21 @@ All VSS queries or any query using the `PARAMS` option must use Dialect version Hybrid queries are often used in modern ecommerce search applications featuring "visual" similarity plus metadata similarity. For example, you can use a single hybrid query to find products that are visually similar to a given image within a price range and/or geo-location. -- Use [`FT.CONFIG SET`]({{< relref "commands/ft.config-set" >}}) to set `DEFAULT_DIALECT` at the module level. By default, `DEFAULT_DIALECT` is set to 1. +- Use [`FT.CONFIG SET`](/content/commands/ft.config-set.md) to set `DEFAULT_DIALECT` at the module level. By default, `DEFAULT_DIALECT` is set to 1. - Override `DIALECT`: It is possible to override the module-level dialect for a specific command at runtime. You can specify the dialect when executing any of the following commands: - - [`FT.SEARCH`]({{< relref "commands/ft.search" >}}) + - [`FT.SEARCH`](/content/commands/ft.search.md) - - [`FT.AGGREGATE`]({{< relref "commands/ft.aggregate" >}}) + - [`FT.AGGREGATE`](/content/commands/ft.aggregate.md) - - [`FT.EXPLAIN`]({{< relref "commands/ft.explain" >}}) + - [`FT.EXPLAIN`](/content/commands/ft.explain.md) - - [`FT.EXPLAINCLI`]({{< relref "commands/ft.explaincli" >}}) + - [`FT.EXPLAINCLI`](/content/commands/ft.explaincli.md) - - [`FT.SPELLCHECK`]({{< relref "commands/ft.spellcheck" >}}) + - [`FT.SPELLCHECK`](/content/commands/ft.spellcheck.md) If you do not specify dialect when running any of these commands, they will use the default module-level dialect value. @@ -329,6 +329,5 @@ Another example that illustrates the differences in parser behavior is - With DIALECT 2, the parser interprets it as searching for either `hello world` OR `"goodbye" moon`. -{{}} -This is the first GA version of 2.4. The version inside Redis will be 2.4.3 in semantic versioning. Since the version of a module in Redis is numeric, we could not add a GA flag. -{{}} +> [!NOTE] +> This is the first GA version of 2.4. The version inside Redis will be 2.4.3 in semantic versioning. Since the version of a module in Redis is numeric, we could not add a GA flag. diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.6-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.6-release-notes.md index c896761c31..796b827488 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.6-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.6-release-notes.md @@ -407,7 +407,7 @@ This is the General Availability release of RediSearch 2.6. ### Highlights This new major version introduces the ability to search using **wildcard queries** for TEXT and TAG fields. This enables the frequently requested feature **suffix search** (`*vatore` and `ant?rez` are now supported). -In addition, the 2.6 release is all about **multi-value indexing and querying of attributes** for any attribute type ( [Text]({{< relref "/develop/ai/search-and-query/indexing/" >}}#index-json-arrays-as-text), [Tag]({{< relref "/develop/ai/search-and-query/indexing/" >}}#index-json-arrays-as-tag), [Numeric]({{< relref "/develop/ai/search-and-query/indexing/" >}}#index-json-arrays-as-numeric), [Geo]({{< relref "/develop/ai/search-and-query/indexing/" >}}#index-json-arrays-as-geo) and [Vector]({{< relref "/develop/ai/search-and-query/indexing/" >}}#index-json-arrays-as-vector)) defined by a [JSONPath]({{< relref "/develop/data-types/json/path" >}}) leading to an array or to multiple scalar values. +In addition, the 2.6 release is all about **multi-value indexing and querying of attributes** for any attribute type ( [Text](/content/develop/ai/search-and-query/indexing/_index.md#index-json-arrays-as-text), [Tag](/content/develop/ai/search-and-query/indexing/_index.md#index-json-arrays-as-tag), [Numeric](/content/develop/ai/search-and-query/indexing/_index.md#index-json-arrays-as-numeric), [Geo](/content/develop/ai/search-and-query/indexing/_index.md#index-json-arrays-as-geo) and [Vector](/content/develop/ai/search-and-query/indexing/_index.md#index-json-arrays-as-vector)) defined by a [JSONPath](/content/develop/data-types/json/path.md) leading to an array or to multiple scalar values. Lastly, this version adds support for indexing double-precision floating-point vectors and range queries from a given vector. ### What's new in 2.6 @@ -416,13 +416,13 @@ Lastly, this version adds support for indexing double-precision floating-point v - Improvements: - - [#2886](https://github.com/RediSearch/RediSearch/pull/2886) Support for [wildcard queries]({{< relref "/develop/ai/search-and-query/advanced-concepts/query_syntax" >}}#wildcard-matching) for TEXT and TAG fields, where + - [#2886](https://github.com/RediSearch/RediSearch/pull/2886) Support for [wildcard queries](/content/develop/ai/search-and-query/advanced-concepts/query_syntax.md#wildcard-matching) for TEXT and TAG fields, where - `?` matches any single character - `*` matches zero or more characters - use `'` and `\` for escaping, other special characters are ignored - [#2932](https://github.com/RediSearch/RediSearch/pull/2932) Optimized wildcard query support (i.e., suffix trie) - Multi-value indexing and querying - - [#2819](https://github.com/RediSearch/RediSearch/pull/2819), [#2947](https://github.com/RediSearch/RediSearch/pull/2947) Multi-value text search - perform full-text search on an [array of strings or on a JSONPath]({{< relref "/develop/ai/search-and-query/indexing/" >}}#index-json-arrays-as-tag) leading to multiple strings + - [#2819](https://github.com/RediSearch/RediSearch/pull/2819), [#2947](https://github.com/RediSearch/RediSearch/pull/2947) Multi-value text search - perform full-text search on an [array of strings or on a JSONPath](/content/develop/ai/search-and-query/indexing/_index.md#index-json-arrays-as-tag) leading to multiple strings - [#3131](https://github.com/RediSearch/RediSearch/pull/3131) Geo [#3118](https://github.com/RediSearch/RediSearch/pull/3118) Vector [#2985](https://github.com/RediSearch/RediSearch/pull/2985) Numeric [#3180](https://github.com/RediSearch/RediSearch/pull/3180) Tag - [#3060](https://github.com/RediSearch/RediSearch/pull/3060) Return JSON rather than scalars from multi-value attributes. This is enabled via Dialect 3 in order not to break existing applications. - Support indexing and querying of multi-value JSONPath attributes and/or arrays (requires JSON >2.4.1) @@ -440,10 +440,8 @@ Lastly, this version adds support for indexing double-precision floating-point v - [#3098](https://github.com/RediSearch/RediSearch/pull/3098) Wrong return value in Geo query - [#3230](https://github.com/RediSearch/RediSearch/issues/3230) Use the correct total number of matching records -{{}} -With this release, we stop supporting direct upgrades from RediSearch v1.4 and v1.6 that are End-of-Life. Such RDB files can still be upgraded to RediSearch 2.0 first. -{{}} +> [!NOTE] +> With this release, we stop supporting direct upgrades from RediSearch v1.4 and v1.6 that are End-of-Life. Such RDB files can still be upgraded to RediSearch 2.0 first. -{{}} -If indexing and querying RedisJSON data structures, this version is best combined with RedisJSON 2.4 GA (v2.4.1 onwards). -{{}} +> [!NOTE] +> If indexing and querying RedisJSON data structures, this version is best combined with RedisJSON 2.4 GA (v2.4.1 onwards). diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.8-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.8-release-notes.md index c88d52529c..6c9cf7dbe1 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.8-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.8-release-notes.md @@ -468,11 +468,11 @@ Features: - Introduce support for geo polygon shapes and queries: - - Adding `GEOSHAPE` [field type]({{< relref "commands/ft.create" >}}) to map polygons in the `SCHEMA` on `FT.CREATE` (MOD-4798) + - Adding `GEOSHAPE` [field type](/content/commands/ft.create.md) to map polygons in the `SCHEMA` on `FT.CREATE` (MOD-4798) - Support for polygons `POLYGON` and `POINT` using [WKT notation](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry), for example `POLYGON((lon1 lat1, lon2 lat2, ...))` - - Adjust the [query syntax]({{< relref "commands/ft.search#examples" >}}) on `FT.SEARCH` for polygons using the predicate `@geom:[OPERATOR $poly]` and defining polygon in WKT format as `PARAMS 2 poly "POLYGON((10 20, ...))"` using `DIALECT 3` + - Adjust the [query syntax](/content/commands/ft.search.md#examples) on `FT.SEARCH` for polygons using the predicate `@geom:[OPERATOR $poly]` and defining polygon in WKT format as `PARAMS 2 poly "POLYGON((10 20, ...))"` using `DIALECT 3` - Initially `WITHIN` and `CONTAINS` operators with `GEOSHAPES` for now @@ -508,10 +508,9 @@ Changed behavior: - [#3355](https://github.com/RediSearch/RediSearch/pull/3355), [#3635](https://github.com/RediSearch/RediSearch/pull/3635) Expired keys deleted from replica's index, returning an empty array instead of `nil` (MOD-4739) -{{}} -- The version inside Redis will be 2.8.4 in semantic versioning. Since the version of a module in Redis is numeric, we could not add a GA flag. - -- Minimal Redis version: 7.2 - -- If indexing and querying RedisJSON data structures, this version is best combined with RedisJSON 2.6 (v2.6.0 onwards). -{{}} +> [!NOTE] +> - The version inside Redis will be 2.8.4 in semantic versioning. Since the version of a module in Redis is numeric, we could not add a GA flag. +> +> - Minimal Redis version: 7.2 +> +> - If indexing and querying RedisJSON data structures, this version is best combined with RedisJSON 2.6 (v2.6.0 onwards). diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgears/redisgears-1.0-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgears/redisgears-1.0-release-notes.md index 0722188214..8d7772e7e6 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgears/redisgears-1.0-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgears/redisgears-1.0-release-notes.md @@ -230,7 +230,6 @@ This is the first general availability (GA) release of RedisGears (v1.0.0). - #[321](https://github.com/RedisGears/RedisGears/issues/321) Return error when unknown argument is given. -{{< note >}} -- The version inside Redis will be 10000 or 1.0.0 in semantic versioning. -- This version requires the Redis version to be 6.0 and above. -{{< /note >}} +> [!NOTE] +> - The version inside Redis will be 10000 or 1.0.0 in semantic versioning. +> - This version requires the Redis version to be 6.0 and above. diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgears/redisgears-1.2-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgears/redisgears-1.2-release-notes.md index a8f55b4389..2b4796310a 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgears/redisgears-1.2-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgears/redisgears-1.2-release-notes.md @@ -166,7 +166,7 @@ This is the General Availability release of RedisGears 1.2. RedisGears 1.2 comes with a new plugin mechanism that allows you to decide which languages you want to load into RedisGears. Currently, we support two languages: Python and Java (JVM languages). You can decide which language you want to use using the new `Plugin` configuration. -Full documentation for JVM support can be found on the [Redis documentation website]({{< relref "/operate/oss_and_stack/stack-with-enterprise/deprecated-features/gears-v1/jvm" >}}). +Full documentation for JVM support can be found on the [Redis documentation website](/content/operate/oss_and_stack/stack-with-enterprise/deprecated-features/gears-v1/jvm/_index.md). #### Python async await support @@ -227,8 +227,7 @@ Bug fixes (since 1.0.9): - [#697](https://github.com/RedisGears/RedisGears/pull/697) `hashtag()` function for Redis Enterprise - [#688](https://github.com/RedisGears/RedisGears/pull/688), [#545](https://github.com/RedisGears/RedisGears/issues/545) Check `REDISMODULE_CTX_FLAGS_DENY_BLOCKING` flag before blocking the client -{{}} -- This is the first GA version of 1.2. The version inside Redis is 1.2.2 in semantic versioning. Since the version of a module in Redis is numeric, we could not add a GA flag. - -- Minimum Redis version: 6.0.0 -{{}} +> [!NOTE] +> - This is the first GA version of 1.2. The version inside Redis is 1.2.2 in semantic versioning. Since the version of a module in Redis is numeric, we could not add a GA flag. +> +> - Minimum Redis version: 6.0.0 diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgraph/redisgraph-2.0-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgraph/redisgraph-2.0-release-notes.md index 2c8afbb60c..55f6bbf2c2 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgraph/redisgraph-2.0-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgraph/redisgraph-2.0-release-notes.md @@ -74,7 +74,7 @@ Details: - #[1226](https://github.com/RedisGraph/RedisGraph/pull/1226) Let RediSearch perform document deletion when replacing a document - Bug Fixes: - #[1223](https://github.com/RedisGraph/RedisGraph/pull/1223) Resolve race condition in accessing/updating attribute maps. - - #[1196](https://github.com/RedisGraph/RedisGraph/pull/1196) Enable RediSearch [Garbage Collection]({{}}) + - #[1196](https://github.com/RedisGraph/RedisGraph/pull/1196) Enable RediSearch [Garbage Collection](/content/develop/ai/search-and-query/administration/gc.md) ## v2.0.15 (25 June 2020) @@ -308,6 +308,5 @@ Full details: - #[607](https://github.com/RedisGraph/RedisGraph/issues/607) All ops NULL-set variables in their free routines (memory). - #[893](https://github.com/RedisGraph/RedisGraph/issues/893) Preserve the children array order when replacing operations. -{{< note >}} -The version inside Redis will be 20001 or 2.0.1 in semantic versioning. -{{< /note >}} \ No newline at end of file +> [!NOTE] +> The version inside Redis will be 20001 or 2.0.1 in semantic versioning. \ No newline at end of file diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgraph/redisgraph-2.2-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgraph/redisgraph-2.2-release-notes.md index 52fd3c5cb4..69e8718e14 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgraph/redisgraph-2.2-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgraph/redisgraph-2.2-release-notes.md @@ -181,7 +181,7 @@ Details: - Support for scaling reads - #[1054](https://github.com/RedisGraph/RedisGraph/pull/1054) - Drastic reduction of memory consumption during replication (and [Active-Passive]({{< relref "/operate/rs/databases/import-export/replica-of/create" >}})). Break down a large graph into several portions, each accommodating a virtual key and distribute those for reconstruction at the replica end, by doing so we reduce memory consumption on the replica's end. + Drastic reduction of memory consumption during replication (and [Active-Passive](/content/operate/rs/databases/import-export/replica-of/create.md)). Break down a large graph into several portions, each accommodating a virtual key and distribute those for reconstruction at the replica end, by doing so we reduce memory consumption on the replica's end. - `OPTIONAL MATCH` support Unlike MATCH, which requires for a pattern to exist, `OPTIONAL MATCH` continues processing when the optional pattern doesn't exist. We can easily compare `OPTIONAL MATCH` in Cypher to an outer join in SQL. It works just like a regular `MATCH` with the difference that if no matches are found, `OPTIONAL MATCH` will use a null for missing parts of the pattern. diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgraph/redisgraph-2.4-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgraph/redisgraph-2.4-release-notes.md index 6eb32fac4e..be8104e692 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgraph/redisgraph-2.4-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgraph/redisgraph-2.4-release-notes.md @@ -35,9 +35,8 @@ Details: - [#2102](https://github.com/RedisGraph/RedisGraph/pull/2102) New load-time configuration option `NODE_CREATION_BUFFER` - see [documentation](https://github.com/RedisGraph/RedisGraph/blob/master/docs/docs/configuration.md#node_creation_buffer) (MOD-2348) -{{}} -For Redis Enterprise users who want to upgrade to this patch, this version requires being on version 6.2.8 or later. -{{}} +> [!NOTE] +> For Redis Enterprise users who want to upgrade to this patch, this version requires being on version 6.2.8 or later. ## v2.4.13 (December 2021) @@ -72,7 +71,7 @@ Update urgency: `MODERATE` : Program an upgrade of the server, but it's not urge Details: - Bug fixes: - - #[1931](https://github.com/RedisGraph/RedisGraph/issues/1931) Fix race condition on calling [`BGSAVE`]({{< relref "/commands/bgsave" >}}) while flushing matrices + - #[1931](https://github.com/RedisGraph/RedisGraph/issues/1931) Fix race condition on calling [`BGSAVE`](/content/commands/bgsave.md) while flushing matrices - #[1898](https://github.com/RedisGraph/RedisGraph/issues/1898) Error when setting a property to an array containing an invalid type - #[1897](https://github.com/RedisGraph/RedisGraph/issues/1897) Aliases in `WITH...ORDER BY` must be valid references% @@ -200,6 +199,5 @@ Details: - Bugfixes (compared to RC1) - #[1618](https://github.com/redisgraph/redisgraph/issues/1618) Fix relationship types being omitted in traversals of 3 or more types. -{{< note >}} -This is the first GA version of 2.4. The version inside Redis will be 2.4.2 in semantic versioning. Since the version of a module in Redis is numeric, we could not add an GA flag. -{{< /note >}} +> [!NOTE] +> This is the first GA version of 2.4. The version inside Redis will be 2.4.2 in semantic versioning. Since the version of a module in Redis is numeric, we could not add an GA flag. diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgraph/redisgraph-2.8-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgraph/redisgraph-2.8-release-notes.md index 1fa10c019d..939f0df12a 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgraph/redisgraph-2.8-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisgraph/redisgraph-2.8-release-notes.md @@ -184,7 +184,7 @@ Details: - Features: - [#2403](https://github.com/RedisGraph/RedisGraph/pull/2403) Introduce `toFloat` function - - [#2365](https://github.com/RedisGraph/RedisGraph/issues/2365) Commands that don't execute on the main thread now also appear in [SLOWLOG]({{< relref "/commands/slowlog" >}}) + - [#2365](https://github.com/RedisGraph/RedisGraph/issues/2365) Commands that don't execute on the main thread now also appear in [SLOWLOG](/content/commands/slowlog.md) - Bug fixes: @@ -195,9 +195,8 @@ Details: - [#2407](https://github.com/RedisGraph/RedisGraph/issues/2407) Crash on double to string - [#2422](https://github.com/RedisGraph/RedisGraph/pull/2422) `toJSON` returned floating points cropped to 6 decimals -{{}} -New RDB version (v12). RDB files created with v2.8.14 or later are not backward compatible. -{{}} +> [!NOTE] +> New RDB version (v12). RDB files created with v2.8.14 or later are not backward compatible. ## v2.8.13 (May 2022) @@ -231,9 +230,8 @@ Details: - [#2298](https://github.com/RedisGraph/RedisGraph/issues/2298) Query returns wrong result: wrong value when fetching a string property from a map - [#2318](https://github.com/RedisGraph/RedisGraph/pull/2318) Memory leak -{{}} -Duplicate column names in a query are no longer valid. For example, the query `GRAPH.QUERY g "MATCH (e) RETURN e, e"` is not valid. If you need to return the same column twice, you can rewrite the query as `GRAPH.QUERY g "MATCH (e) RETURN e, e as e2"`. -{{}} +> [!NOTE] +> Duplicate column names in a query are no longer valid. For example, the query `GRAPH.QUERY g "MATCH (e) RETURN e, e"` is not valid. If you need to return the same column twice, you can rewrite the query as `GRAPH.QUERY g "MATCH (e) RETURN e, e as e2"`. ## v2.8.11 (March 2022) @@ -245,7 +243,7 @@ Details: - Bug fixes: - - [#2259](https://github.com/RedisGraph/RedisGraph/issues/2259), [#2258](https://github.com/RedisGraph/RedisGraph/pull/2258) Fix memory leak and potential crash on [RDB]({{< relref "/operate/oss_and_stack/management/persistence" >}}) saving + - [#2259](https://github.com/RedisGraph/RedisGraph/issues/2259), [#2258](https://github.com/RedisGraph/RedisGraph/pull/2258) Fix memory leak and potential crash on [RDB](/content/operate/oss_and_stack/management/persistence.md) saving ## v2.8.10 (March 2022) @@ -257,7 +255,7 @@ Details: - Features: - - [#2245](https://github.com/RedisGraph/RedisGraph/pull/2245) Support graphs [eviction]({{< relref "/develop/reference/eviction" >}}) + - [#2245](https://github.com/RedisGraph/RedisGraph/pull/2245) Support graphs [eviction](/content/develop/reference/eviction/index.md) - Bug fixes: @@ -271,7 +269,7 @@ Details: - Improvements: - - [#2235](https://github.com/RedisGraph/RedisGraph/pull/2235) Improved [RDB]({{< relref "/operate/oss_and_stack/management/persistence" >}}) loading performance + - [#2235](https://github.com/RedisGraph/RedisGraph/pull/2235) Improved [RDB](/content/operate/oss_and_stack/management/persistence.md) loading performance ## v2.8.9 (March 2022) @@ -311,11 +309,10 @@ RedisGraph 2.8 introduces multi-labeled nodes, indexes over relationship propert - Multi-labeled nodes - {{}} -The `labels` function's signature has changed. The function now returns a list of labels instead of a single label. -

-If you are using this function and upgrading to RedisGraph 2.8, a simple fix is to replace any call to `labels(x)` with `labels(x)[0]`. This returns the first label associated with node `x`. For uni-labeled nodes, the result in RedisGraph 2.8 is similar to the results of `labels(x)` in RedisGraph 2.4. - {{}} + > [!NOTE] + > The `labels` function's signature has changed. The function now returns a list of labels instead of a single label. + >

+ > If you are using this function and upgrading to RedisGraph 2.8, a simple fix is to replace any call to `labels(x)` with `labels(x)[0]`. This returns the first label associated with node `x`. For uni-labeled nodes, the result in RedisGraph 2.8 is similar to the results of `labels(x)` in RedisGraph 2.4. - Indexes over relationship properties - Enhanced full-text search diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.0-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.0-release-notes.md index 1b9c82d78c..00cf2d0c42 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.0-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.0-release-notes.md @@ -114,13 +114,13 @@ RedisJSON is a [high-performance JSON document store](https://redis.com/blog/red #### Indexing JSON documents -Using [RediSearch](https://redisearch.io), it is now possible to [index, query, and search JSON documents]({{}}), gaining full-text search capabilities and document retrieving based on their content. +Using [RediSearch](https://redisearch.io), it is now possible to [index, query, and search JSON documents](/content/develop/ai/search-and-query/indexing/_index.md), gaining full-text search capabilities and document retrieving based on their content. To do so, you must install both modules, `RedisJSON` and `RediSearch`, on the same database. #### Support of JSON Path -The commands [support JSONPath]({{}}) as specified in the [original specifications](https://goessner.net/articles/JsonPath). +The commands [support JSONPath](/content/develop/data-types/json/path.md) as specified in the [original specifications](https://goessner.net/articles/JsonPath). The legacy path syntax is still supported. diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.2-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.2-release-notes.md index cf239adfce..f726c7de8a 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.2-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.2-release-notes.md @@ -24,7 +24,7 @@ A preview of RedisJSON 2.2 is available for Free and Fixed subscription plans in ### Headlines -This release adds support for the JSON data structure as a CRDT (Conflict-free Replicated Data Type) when used with Redis Enterprise [Active-Active databases]({{< relref "/operate/oss_and_stack/stack-with-enterprise/json" >}}active-active/). +This release adds support for the JSON data structure as a CRDT (Conflict-free Replicated Data Type) when used with Redis Enterprise [Active-Active databases](/content/operate/oss_and_stack/stack-with-enterprise/json/active-active.md). Active-Active JSON requires Redis Enterprise Software v6.2.12. Contact your account manager or support to access the preview of RedisJSON 2.2. @@ -32,4 +32,4 @@ Active-Active JSON requires Redis Enterprise Software v6.2.12. Contact your acco - Enhancements: - - [#758](https://github.com/RedisJSON/RedisJSON/pull/758) Add support for [`COPY`]({{< relref "/commands/copy" >}}) + - [#758](https://github.com/RedisJSON/RedisJSON/pull/758) Add support for [`COPY`](/content/commands/copy.md) diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.4-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.4-release-notes.md index 8a81179c39..f376bb72e5 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.4-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.4-release-notes.md @@ -90,9 +90,8 @@ This is a maintenance release for RedisJSON 2.4. Update urgency: `MODERATE`: Program an upgrade of the server, but it's not urgent. -{{}} -Ubuntu 16.04 and RHEL 7 are no longer supported as of v2.4.8. -{{}} +> [!NOTE] +> Ubuntu 16.04 and RHEL 7 are no longer supported as of v2.4.8. Details: diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.6-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.6-release-notes.md index a255cd19cc..008a48ccd7 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.6-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.6-release-notes.md @@ -133,9 +133,8 @@ Update urgency: `LOW`: No need to upgrade unless there are new features you want Details: -{{}} -RHEL 7 is no longer supported as of v2.6.8. -{{}} +> [!NOTE] +> RHEL 7 is no longer supported as of v2.6.8. This is a version number alignment with RedisJSON for Redis Enterprise (with Active-Active support). @@ -172,7 +171,7 @@ RedisJSON 2.6 introduces support for RESP3 and new commands. ### What's new in 2.6 -- Introduce [`JSON.MERGE`]({{< relref "commands/json.merge" >}}) in compliance with [RFC 7396](https://datatracker.ietf.org/doc/html/rfc7396), supporting: +- Introduce [`JSON.MERGE`](/content/commands/json.merge.md) in compliance with [RFC 7396](https://datatracker.ietf.org/doc/html/rfc7396), supporting: - Creating new attributes on an existing JSON document @@ -182,7 +181,7 @@ RedisJSON 2.6 introduces support for RESP3 and new commands. - Array update - replacing an entire array with the new value -- Introduce [`JSON.MSET`]({{< relref "commands/json.mset" >}}), supporting atomic multiple sets for keys in the same hash slot +- Introduce [`JSON.MSET`](/content/commands/json.mset.md), supporting atomic multiple sets for keys in the same hash slot - New `FORMAT` argument in `JSON.ARRPOP` and `JSON.GET` to retrieve the results as JSON strings or RESP3 hierarchical structures (RESP3 only) @@ -190,8 +189,7 @@ RedisJSON 2.6 introduces support for RESP3 and new commands. - Legacy paths (paths that don't start with either `$.` or `$[` or equal to `$`), except those starting with `.`, are now deprecated -{{}} -- The version inside Redis will be 2.6.4 in semantic versioning. Since the version of a module in Redis is numeric, we could not add a GA flag. - -- Minimal Redis version: 7.2 -{{}} +> [!NOTE] +> - The version inside Redis will be 2.6.4 in semantic versioning. Since the version of a module in Redis is numeric, we could not add a GA flag. +> +> - Minimal Redis version: 7.2 diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.8-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.8-release-notes.md index 328259c909..d472f9e571 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.8-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.8-release-notes.md @@ -22,13 +22,12 @@ RedisJSON v2.8.19 requires: ## v2.8.19 (April 2026): -{{< note >}} -Starting with Redis 8 in Redis Open Source, the JSON data structure is integral to Redis. You don't need to install this module separately. - -We no longer release standalone versions of RedisJSON. - -See https://github.com/redis/redis. -{{< /note >}} +> [!NOTE] +> Starting with Redis 8 in Redis Open Source, the JSON data structure is integral to Redis. You don't need to install this module separately. +> +> We no longer release standalone versions of RedisJSON. +> +> See https://github.com/redis/redis. This is a maintenance release for RedisJSON 2.8. @@ -131,7 +130,6 @@ Details - [#1212](https://github.com/RedisJSON/RedisJSON/pull/1212) `JSON.MSET`- AOF commands are duplicated multiple times (MOD-7293) -{{< note >}} -- The version inside Redis will be 2.8.3 in semantic versioning. Since the version of a module in Redis is numeric, we could not add a GA flag. -- Minimal Redis version: 7.4 -{{< /note >}} +> [!NOTE] +> - The version inside Redis will be 2.8.3 in semantic versioning. Since the version of a module in Redis is numeric, we could not add a GA flag. +> - Minimal Redis version: 7.4 diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisstack/redisstack-7.4-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisstack/redisstack-7.4-release-notes.md index 0f3b311f4b..3e5e9a65c1 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisstack/redisstack-7.4-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisstack/redisstack-7.4-release-notes.md @@ -89,9 +89,8 @@ There are many additional improvements, including new command arguments, securit - Developers can now match `TAG` fields without needing to escape special characters, making the onboarding process and use of the query syntax simpler. - Geospatial search capabilities have been expanded with new `INTERSECT` and `DISJOINT` operators, and ergonomics have been improved by providing better reporting of the memory consumed by the index and exposing the Full-text scoring in the aggregation pipeline. -{{< warning >}} -If one or more fields of a hash key expire after a query begins (using FT.SEARCH or FT.AGGREGATE), Redis does not account for these lazily expired fields. As a result, keys with expired fields may still be included in the query results, leading to potentially incorrect or inconsistent results. -{{< /warning >}} +> [!WARNING] +> If one or more fields of a hash key expire after a query begins (using FT.SEARCH or FT.AGGREGATE), Redis does not account for these lazily expired fields. As a result, keys with expired fields may still be included in the query results, leading to potentially incorrect or inconsistent results. **Removal of triggers and functions** diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.0-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.0-release-notes.md index f1fa79055b..0699ad159f 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.0-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.0-release-notes.md @@ -58,7 +58,7 @@ This is the General Availability release of RedisTimeSeries! Read the [full sto ### Features -In RedisTimeSeries, we are introducing a new data type that uses chunks of memory of fixed size for time series samples, indexed by the same [Radix Tree implementation](https://github.com/antirez/rax) as Redis Streams. With Streams, you can create a [capped stream]({{< relref "/commands/xadd" >}}, effectively limiting the number of messages by count. In RedisTimeSeries, you can apply a retention policy in milliseconds. This is better for time series use cases, because they are typically interested in the data during a given time window, rather than a fixed number of samples. +In RedisTimeSeries, we are introducing a new data type that uses chunks of memory of fixed size for time series samples, indexed by the same [Radix Tree implementation](https://github.com/antirez/rax) as Redis Streams. With Streams, you can create a [capped stream](/commands/xadd), effectively limiting the number of messages by count. In RedisTimeSeries, you can apply a retention policy in milliseconds. This is better for time series use cases, because they are typically interested in the data during a given time window, rather than a fixed number of samples. #### Downsampling/compaction diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.10-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.10-release-notes.md index 7e8cb41c6f..937b15ddd7 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.10-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.10-release-notes.md @@ -155,8 +155,7 @@ Bug fixes (since 1.10-RC3): - [#1494](https://github.com/RedisTimeSeries/RedisTimeSeries/issues/1494) Potential crash when using an invalid argument value -{{}} -- The version inside Redis will be 1.10.4 in semantic versioning. Since the version of a module in Redis is numeric, we could not add a GA flag. - -- Minimal Redis version: 7.2 -{{}} +> [!NOTE] +> - The version inside Redis will be 1.10.4 in semantic versioning. Since the version of a module in Redis is numeric, we could not add a GA flag. +> +> - Minimal Redis version: 7.2 diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.12-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.12-release-notes.md index 935ea5a95a..ef32db197f 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.12-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.12-release-notes.md @@ -37,12 +37,11 @@ Details: ## v1.12.14 (May 2026) -{{< note >}} -Starting with Redis 8, the time series data structure is integral to Redis. You don't need to install this module separately. -This is not the latest release. -We no longer release new standalone versions of RedisTimeSeries; we only patch old versions. -See https://github.com/redis/redis -{{< /note >}} +> [!NOTE] +> Starting with Redis 8, the time series data structure is integral to Redis. You don't need to install this module separately. +> This is not the latest release. +> We no longer release new standalone versions of RedisTimeSeries; we only patch old versions. +> See https://github.com/redis/redis This is a maintenance release for RedisTimeSeries 1.12. @@ -134,7 +133,6 @@ RedisTimeSeries 1.12 adds a highly requested feature: insertion-filter for close - [#1607](https://github.com/RedisTimeSeries/RedisTimeSeries/pull/1607) Potential crash after deleting and recreating a source key of a compaction rule (MOD-7338) - [#1610](https://github.com/RedisTimeSeries/RedisTimeSeries/pull/1610) `COUNT` argument accepts non-positive values (MOD-5413) -{{< note >}} -- The version inside Redis will be 1.12.2 in semantic versioning. Since the version of a module in Redis is numeric, we could not add a GA flag. -- Minimal Redis version: 7.4 -{{< /note >}} +> [!NOTE] +> - The version inside Redis will be 1.12.2 in semantic versioning. Since the version of a module in Redis is numeric, we could not add a GA flag. +> - Minimal Redis version: 7.4 diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.2-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.2-release-notes.md index 4ef1b5d316..f97a1f4258 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.2-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.2-release-notes.md @@ -78,7 +78,7 @@ Headlines: - Compression added which can reduce memory up to 98% and improve read performance up to 50%. - Stable ingestion time independent of the number of the data points on a time-series. - Reviewed API with performance improvements and removed ambiguity. -- Extended [client support]({{}}) +- Extended [client support](/content/develop/data-types/timeseries/_index.md) (we will blog about this release soon including performance improvements results and the link here) @@ -120,6 +120,5 @@ Full details: - #[320](https://github.com/RedisTimeSeries/RedisTimeSeries/issues/320) Delete the existing key prior to restoring it. - #[323](https://github.com/RedisTimeSeries/RedisTimeSeries/issues/323) Empty first sample on aggregation. -{{< note >}} -The version inside Redis will be 10202 or 1.2.2 in semantic versioning. -{{< /note >}} +> [!NOTE] +> The version inside Redis will be 10202 or 1.2.2 in semantic versioning. diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.4-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.4-release-notes.md index b03b743da9..53f3a1320f 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.4-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.4-release-notes.md @@ -56,7 +56,7 @@ Update urgency: `HIGH`: There is a critical bug that may affect a subset of user Bug fixes: -- [#760](https://github.com/RedisTimeSeries/RedisTimeSeries/issues/760) Avoid closing the same key twice, causing server crash on [`RENAME`]({{< relref "/commands/rename" >}}) of other keys +- [#760](https://github.com/RedisTimeSeries/RedisTimeSeries/issues/760) Avoid closing the same key twice, causing server crash on [`RENAME`](/content/commands/rename.md) of other keys ## v1.4.9 (May 2021) diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.6-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.6-release-notes.md index 4f4dc91028..7e973178f7 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.6-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.6-release-notes.md @@ -50,17 +50,16 @@ Details: - Features: - - [#1193](https://github.com/RedisTimeSeries/RedisTimeSeries/pull/1193) Commands that don’t execute on the main thread now appear in [SLOWLOG]({{< relref "/commands/slowlog" >}}) + - [#1193](https://github.com/RedisTimeSeries/RedisTimeSeries/pull/1193) Commands that don’t execute on the main thread now appear in [SLOWLOG](/content/commands/slowlog.md) - Bug fixes: - [#1203](https://github.com/RedisTimeSeries/RedisTimeSeries/pull/1203) Compaction rules are not replicated (Replica Of) on Redis Enterprise - - [#1204](https://github.com/RedisTimeSeries/RedisTimeSeries/issues/1204) When the last sample is deleted with [`TS.DEL`]({{< relref "commands/ts.del" >}}), it may still be accessible with [`TS.GET`]({{< relref "commands/ts.get" >}}) - - [#1226](https://github.com/RedisTimeSeries/RedisTimeSeries/pull/1226) [`TS.MRANGE`]({{< relref "commands/ts.mrange" >}}), [`TS.MREVRANGE`]({{< relref "commands/ts.mrevrange" >}}): on a multi-shard environment, some chunks may be skipped + - [#1204](https://github.com/RedisTimeSeries/RedisTimeSeries/issues/1204) When the last sample is deleted with [`TS.DEL`](/content/commands/ts.del.md), it may still be accessible with [`TS.GET`](/content/commands/ts.get.md) + - [#1226](https://github.com/RedisTimeSeries/RedisTimeSeries/pull/1226) [`TS.MRANGE`](/content/commands/ts.mrange.md), [`TS.MREVRANGE`](/content/commands/ts.mrevrange.md): on a multi-shard environment, some chunks may be skipped -{{}} -New RDB version (v5). RDB files created with 1.6.16 are not backward compatible. -{{}} +> [!NOTE] +> New RDB version (v5). RDB files created with 1.6.16 are not backward compatible. ## v1.6.13 (June 2022) @@ -72,8 +71,8 @@ Details: - Bug fixes: - - [#1176](https://github.com/RedisTimeSeries/RedisTimeSeries/issues/1176), [#1187](https://github.com/RedisTimeSeries/RedisTimeSeries/pull/1187) When executing [`DEL`]({{< relref "commands/ts.del" >}}), chunk index could be set to a wrong value and cause some data to be inaccessible - - [#1180](https://github.com/RedisTimeSeries/RedisTimeSeries/pull/1180) When executing [`MADD`]({{< relref "commands/ts.madd" >}}), make sure that only successful insertions are replicated + - [#1176](https://github.com/RedisTimeSeries/RedisTimeSeries/issues/1176), [#1187](https://github.com/RedisTimeSeries/RedisTimeSeries/pull/1187) When executing [`DEL`](/content/commands/ts.del.md), chunk index could be set to a wrong value and cause some data to be inaccessible + - [#1180](https://github.com/RedisTimeSeries/RedisTimeSeries/pull/1180) When executing [`MADD`](/content/commands/ts.madd.md), make sure that only successful insertions are replicated ## v1.6.11 (May 2022) @@ -99,10 +98,10 @@ Details: - Bug fixes: - - [#1074](https://github.com/RedisTimeSeries/RedisTimeSeries/pull/1074) [`RANGE`]({{< relref "commands/ts.range" >}}), [`REVRANGE`]({{< relref "commands/ts.revrange" >}}), [`MRANGE`]({{< relref "commands/ts.mrange" >}}), and [`MREVRANGE`]({{< relref "commands/ts.mrevrange" >}}): Possibly incorrect result when using `ALIGN` and aggregating a bucket with a timestamp close to 0 + - [#1074](https://github.com/RedisTimeSeries/RedisTimeSeries/pull/1074) [`RANGE`](/content/commands/ts.range.md), [`REVRANGE`](/content/commands/ts.revrange.md), [`MRANGE`](/content/commands/ts.mrange.md), and [`MREVRANGE`](/content/commands/ts.mrevrange.md): Possibly incorrect result when using `ALIGN` and aggregating a bucket with a timestamp close to 0 - [#1094](https://github.com/RedisTimeSeries/RedisTimeSeries/pull/1094) [LibMR](https://github.com/RedisGears/LibMR): Potential memory leak; memory release delay - - [#1127](https://github.com/RedisTimeSeries/RedisTimeSeries/pull/1127) Memory leak on [`RANGE`]({{< relref "commands/ts.range" >}}) and [`REVRANGE`]({{< relref "commands/ts.revrange" >}}) when argument parsing fails - - [#1096](https://github.com/RedisTimeSeries/RedisTimeSeries/pull/1096) [`RANGE`]({{< relref "commands/ts.range" >}}), [`REVRANGE`]({{< relref "commands/ts.revrange" >}}), [`MRANGE`]({{< relref "commands/ts.mrange" >}}), and [`MREVRANGE`]({{< relref "commands/ts.mrevrange" >}}): Using `FILTER_BY_TS` without specifying timestamps now returns an error as expected + - [#1127](https://github.com/RedisTimeSeries/RedisTimeSeries/pull/1127) Memory leak on [`RANGE`](/content/commands/ts.range.md) and [`REVRANGE`](/content/commands/ts.revrange.md) when argument parsing fails + - [#1096](https://github.com/RedisTimeSeries/RedisTimeSeries/pull/1096) [`RANGE`](/content/commands/ts.range.md), [`REVRANGE`](/content/commands/ts.revrange.md), [`MRANGE`](/content/commands/ts.mrange.md), and [`MREVRANGE`](/content/commands/ts.mrevrange.md): Using `FILTER_BY_TS` without specifying timestamps now returns an error as expected ## v1.6.9 (February 2022) diff --git a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.8-release-notes.md b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.8-release-notes.md index 1440f3ae22..056989e031 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.8-release-notes.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.8-release-notes.md @@ -208,11 +208,11 @@ Details: - Bug fixes: - [#1360](https://github.com/RedisTimeSeries/RedisTimeSeries/pull/1360) Potential crash when upgrading from v1.6 to 1.8 if there are compactions with `min` or `max` aggregation (MOD-4559) - - [#1370](https://github.com/RedisTimeSeries/RedisTimeSeries/issues/1370) Potential crash when using [TS.REVRANGE]({{< relref "commands/ts.revrange" >}}) or [TS.MREVRANGE]({{< relref "commands/ts.mrevrange" >}}) with aggregation - - [#1347](https://github.com/RedisTimeSeries/RedisTimeSeries/pull/1347) When adding samples with [TS.ADD]({{< relref "commands/ts.add" >}}) or [TS.MADD]({{< relref "commands/ts.madd" >}}) using `*` as timestamp, the timestamp could differ between master and replica shards + - [#1370](https://github.com/RedisTimeSeries/RedisTimeSeries/issues/1370) Potential crash when using [TS.REVRANGE](/content/commands/ts.revrange.md) or [TS.MREVRANGE](/content/commands/ts.mrevrange.md) with aggregation + - [#1347](https://github.com/RedisTimeSeries/RedisTimeSeries/pull/1347) When adding samples with [TS.ADD](/content/commands/ts.add.md) or [TS.MADD](/content/commands/ts.madd.md) using `*` as timestamp, the timestamp could differ between master and replica shards - Improvements: - - [#1215](https://github.com/RedisTimeSeries/RedisTimeSeries/issues/1215) OSS cluster: Support TLS and IPv6; introduce new configuration parameter: [OSS_GLOBAL_PASSWORD]({{< relref "/develop/data-types/timeseries/" >}}configuration/#oss_global_password) + - [#1215](https://github.com/RedisTimeSeries/RedisTimeSeries/issues/1215) OSS cluster: Support TLS and IPv6; introduce new configuration parameter: [OSS_GLOBAL_PASSWORD](/content/develop/data-types/timeseries/configuration.md#oss_global_password) ## v1.8 GA (v1.8.3) (November 2022) @@ -227,15 +227,15 @@ RedisTimeSeries 1.8 introduces seven highly requested features, performance impr * **Optionally retrieving aggregation results for the latest (still open) bucket for compactions** - Till version 1.8, when a time series is a compaction, [TS.GET]({{< relref "commands/ts.get" >}}), [TS.MGET]({{< relref "commands/ts.mget" >}}), [TS.RANGE]({{< relref "commands/ts.range" >}}), [TS.REVRANGE]({{< relref "commands/ts.revrange" >}}), [TS.MRANGE]({{< relref "commands/ts.mrange" >}}), [TS.MREVRANGE]({{< relref "commands/ts.mrevrange" >}}) did not report the compacted value of the latest bucket. The reason is that the data in the latest bucket of a compaction is still partial. A bucket is ‘closed’ and compacted only upon the arrival of data that ‘opens’ a ‘new latest’ bucket. + Till version 1.8, when a time series is a compaction, [TS.GET](/content/commands/ts.get.md), [TS.MGET](/content/commands/ts.mget.md), [TS.RANGE](/content/commands/ts.range.md), [TS.REVRANGE](/content/commands/ts.revrange.md), [TS.MRANGE](/content/commands/ts.mrange.md), [TS.MREVRANGE](/content/commands/ts.mrevrange.md) did not report the compacted value of the latest bucket. The reason is that the data in the latest bucket of a compaction is still partial. A bucket is ‘closed’ and compacted only upon the arrival of data that ‘opens’ a ‘new latest’ bucket. There are use cases, however, where the compaction of the latest bucket should be retrieved as well. For example, a user may want to receive the count of events since the start of the decade, and the retention period for raw data is only one month. Till version 1.8, the user would have to run two queries - one on a compaction and one on the latest raw data, and then sum the results. Since version 1.8, by specifying `LATEST`, it is possible to retrieve the latest (possibly partial) bucket as well. - To report aggregations for the latest bucket, use the new optional `LATEST` flag to [TS.GET]({{< relref "commands/ts.get" >}}), [TS.MGET]({{< relref "commands/ts.mget" >}}), [TS.RANGE]({{< relref "commands/ts.range" >}}), [TS.REVRANGE]({{< relref "commands/ts.revrange" >}}), [TS.MRANGE]({{< relref "commands/ts.mrange" >}}), and [TS.REVRANGE]({{< relref "commands/ts.mrevrange" >}}). + To report aggregations for the latest bucket, use the new optional `LATEST` flag to [TS.GET](/content/commands/ts.get.md), [TS.MGET](/content/commands/ts.mget.md), [TS.RANGE](/content/commands/ts.range.md), [TS.REVRANGE](/content/commands/ts.revrange.md), [TS.MRANGE](/content/commands/ts.mrange.md), and [TS.REVRANGE](/content/commands/ts.mrevrange.md). * **Optionally retrieving aggregation results for empty buckets** - The commands [TS.RANGE]({{< relref "commands/ts.range" >}}), [TS.REVRANGE]({{< relref "commands/ts.revrange" >}}), [TS.MRANGE]({{< relref "commands/ts.mrange" >}}), and [TS.MREVRANGE]({{< relref "commands/ts.mrevrange" >}}) have an optional `[AGGREGATION aggregator bucketDuration]` parameter. When this parameter is specified, raw reports are aggregated per bucket. + The commands [TS.RANGE](/content/commands/ts.range.md), [TS.REVRANGE](/content/commands/ts.revrange.md), [TS.MRANGE](/content/commands/ts.mrange.md), and [TS.MREVRANGE](/content/commands/ts.mrevrange.md) have an optional `[AGGREGATION aggregator bucketDuration]` parameter. When this parameter is specified, raw reports are aggregated per bucket. Till version 1.8, results were not reported for empty buckets. With `EMPTY`, it is now possible to report aggregations for empty buckets as well. @@ -251,7 +251,7 @@ RedisTimeSeries 1.8 introduces seven highly requested features, performance impr For the `last` aggregator and the new `twa` aggregator, the `EMPTY` flag is used for gap filling (see below). - To report aggregations for empty buckets, use the new optional `EMPTY` flag in [TS.RANGE]({{< relref "commands/ts.range" >}}), [TS.REVRANGE]({{< relref "commands/ts.revrange" >}}), [TS.MRANGE]({{< relref "commands/ts.mrange" >}}), and [TS.MREVRANGE]({{< relref "commands/ts.mrevrange" >}}). + To report aggregations for empty buckets, use the new optional `EMPTY` flag in [TS.RANGE](/content/commands/ts.range.md), [TS.REVRANGE](/content/commands/ts.revrange.md), [TS.MRANGE](/content/commands/ts.mrange.md), and [TS.MREVRANGE](/content/commands/ts.mrevrange.md). Regardless of the values of `fromTimestamp` and `toTimestamp`, no data is reported for empty buckets that end before the earliest sample or begin after the latest sample in the time series. @@ -273,7 +273,7 @@ RedisTimeSeries 1.8 introduces seven highly requested features, performance impr {{A graph that illustrates gap-filling.}} - Consider we want to use [TS.RANGE]({{< relref "commands/ts.range" >}}) to calculate the average value of each bucket (p1, p2, p3 in the diagram above). Using avg, the value reported for bucket p2 would be NaN, as this bucket contains no samples. If we use `EMPTY` with `twa`, on the other hand, the average value for bucket p2 would be calculated based on the linear interpolation of the value left of p2 and the value right of p2. + Consider we want to use [TS.RANGE](/content/commands/ts.range.md) to calculate the average value of each bucket (p1, p2, p3 in the diagram above). Using avg, the value reported for bucket p2 would be NaN, as this bucket contains no samples. If we use `EMPTY` with `twa`, on the other hand, the average value for bucket p2 would be calculated based on the linear interpolation of the value left of p2 and the value right of p2. When sampling a continuous signal, we can use this ‘gap-filling’ capability to calculate the average value of the signal over equal-width buckets without concern about bucket alignment or missing samples. @@ -281,11 +281,11 @@ RedisTimeSeries 1.8 introduces seven highly requested features, performance impr * **Ability to control how bucket timestamps are reported** - Till version 1.8, [TS.RANGE]({{< relref "commands/ts.range" >}}), [TS.REVRANGE]({{< relref "commands/ts.revrange" >}}), [TS.MRANGE]({{< relref "commands/ts.mrange" >}}), and [TS.MREVRANGE]({{< relref "commands/ts.mrevrange" >}}) returned the start time of each reported bucket as its timestamp. + Till version 1.8, [TS.RANGE](/content/commands/ts.range.md), [TS.REVRANGE](/content/commands/ts.revrange.md), [TS.MRANGE](/content/commands/ts.mrange.md), and [TS.MREVRANGE](/content/commands/ts.mrevrange.md) returned the start time of each reported bucket as its timestamp. Changing this behavior and reporting each bucket’s start time, end time, or mid-time is now possible. This is required in many use cases. For example, when drawing bars in trading applications, annotating each bar with the end timestamp of the bucket it represents is very common. - The way bucket timestamps are reported can be specified with the new optional `BUCKETTIMESTAMP` parameter of [TS.RANGE]({{< relref "commands/ts.range" >}}), [TS.REVRANGE]({{< relref "commands/ts.revrange" >}}), [TS.MRANGE]({{< relref "commands/ts.mrange" >}}), and [TS.MREVRANGE]({{< relref "commands/ts.mrevrange" >}}). + The way bucket timestamps are reported can be specified with the new optional `BUCKETTIMESTAMP` parameter of [TS.RANGE](/content/commands/ts.range.md), [TS.REVRANGE](/content/commands/ts.revrange.md), [TS.MRANGE](/content/commands/ts.mrange.md), and [TS.MREVRANGE](/content/commands/ts.mrevrange.md). `-` or `low`: the bucket's start time (default) @@ -299,7 +299,7 @@ RedisTimeSeries 1.8 introduces seven highly requested features, performance impr But what if we want to aggregate daily events from 06:00 to 06:00 the next day? We can now specify alignment for compaction rules. - Alignment can be specified with the new optional `alignTimestamp` parameter of [TS.CREATERULE]({{< relref "commands/ts.createrule" >}}) and the [COMPACTION_POLICY]({{< relref "/develop/data-types/timeseries/configuration" >}}) configuration parameter. Specifying `alignTimestamp` ensures that there is a bucket that starts exactly at `alignTimestamp` and all other buckets are aligned accordingly. `alignTimestamp` is expressed in milliseconds. The default value is 0 (aligned with the epoch). + Alignment can be specified with the new optional `alignTimestamp` parameter of [TS.CREATERULE](/content/commands/ts.createrule.md) and the [COMPACTION_POLICY](/content/develop/data-types/timeseries/configuration.md) configuration parameter. Specifying `alignTimestamp` ensures that there is a bucket that starts exactly at `alignTimestamp` and all other buckets are aligned accordingly. `alignTimestamp` is expressed in milliseconds. The default value is 0 (aligned with the epoch). * **New reducers** @@ -307,8 +307,7 @@ RedisTimeSeries 1.8 introduces seven highly requested features, performance impr It is now possible, for example, to calculate the maximal temperature per timeframe for each sensor and then report the average temperature (avg reducer) over groups of sensors (grouped by a given label's value). - This can be specified with the new reducer types ([TS.MRANGE]({{< relref "commands/ts.mrange" >}}) and [TS.MREVRANGE]({{< relref "commands/ts.mrevrange" >}}): `avg`, `range`, `count`, `std.p`, `std.s`, `var.p`, and `var.s`. + This can be specified with the new reducer types ([TS.MRANGE](/content/commands/ts.mrange.md) and [TS.MREVRANGE](/content/commands/ts.mrevrange.md): `avg`, `range`, `count`, `std.p`, `std.s`, `var.p`, and `var.s`. -{{}} -New RDB version (v7). RDB files created with v1.8.3 are not backward compatible. -{{}} +> [!NOTE] +> New RDB version (v7). RDB files created with v1.8.3 are not backward compatible.