2. Follow the instructions to create a free database.
-This free Redis Cloud database comes out of the box with all the Redis Community Edition features.
+This free Redis Cloud database comes out of the box with all the Redis Open Source features.
-You can alternatively use the [installation guides]({{< relref "/operate/oss_and_stack/install/install-stack/" >}}) to install Redis Community Edition on your local machine.
+You can alternatively use the [installation guides]({{< relref "/operate/oss_and_stack/install/install-stack/" >}}) to install Redis Open Source on your local machine.
## Connect
-The first step is to connect to your Redis Community Edition database. You can find further details about the connection options in this documentation site's [Tools section]({{< relref "/develop/tools" >}}). The following example shows how to connect to a Redis Community Edition server that runs on localhost (`-h 127.0.0.1`) and listens on the default port (`-p 6379`):
+The first step is to connect to your Redis Open Source database. You can find further details about the connection options in this documentation site's [Tools section]({{< relref "/develop/tools" >}}). The following example shows how to connect to a Redis Open Source server that runs on localhost (`-h 127.0.0.1`) and listens on the default port (`-p 6379`):
{{< clients-example search_quickstart connect >}}
> redis-cli -h 127.0.0.1 -p 6379
@@ -173,7 +173,7 @@ Please see the [query documentation]({{< relref "/develop/interact/search-and-qu
## Next steps
-You can learn more about how to use Redis Community Edition as a vector database in the following quick start guide:
+You can learn more about how to use Redis Open Source as a vector database in the following quick start guide:
* [Redis as a vector database]({{< relref "/develop/get-started/vector-database" >}})
diff --git a/content/develop/get-started/faq.md b/content/develop/get-started/faq.md
index fa4e7a7f8c..60f4e550af 100644
--- a/content/develop/get-started/faq.md
+++ b/content/develop/get-started/faq.md
@@ -56,7 +56,7 @@ to split your data set into multiple Redis instances, please read the
Redis Ltd., the company sponsoring Redis development, has developed a
"Redis on Flash" solution that uses a mixed RAM/flash approach for
larger data sets with a biased access pattern. You may check their offering
-for more information, however this feature is not part of the Redis Community Edition
+for more information, however this feature is not part of the Redis Open Source
code base.
## Can you use Redis with a disk-based database?
diff --git a/content/develop/get-started/vector-database.md b/content/develop/get-started/vector-database.md
index 6e5e9e5b85..6b2511074a 100644
--- a/content/develop/get-started/vector-database.md
+++ b/content/develop/get-started/vector-database.md
@@ -46,7 +46,7 @@ Data is often unstructured, which means that it isn't described by a well-define
## Create a Redis vector database
-You can use [Redis Community Edition]({{< relref "/operate/oss_and_stack/" >}}) as a vector database. It allows you to:
+You can use [Redis Open Source]({{< relref "/operate/oss_and_stack/" >}}) as a vector database. It allows you to:
* Store vectors and the associated metadata within hashes or [JSON]({{< relref "/develop/data-types/json" >}}) documents
* Create and configure secondary indices for search
@@ -61,7 +61,7 @@ The easiest way to get started is to use Redis Cloud:
2. Follow the instructions to create a free database.
-This free Redis Cloud database comes out of the box with all the Redis Community Edition features.
+This free Redis Cloud database comes out of the box with all the Redis Open Source features.
You can alternatively use the [installation guides]({{< relref "/operate/oss_and_stack/install/install-stack/" >}}) to install Redis on your local machine.
diff --git a/content/develop/interact/search-and-query/_index.md b/content/develop/interact/search-and-query/_index.md
index f211cbf847..2c7569f2e8 100644
--- a/content/develop/interact/search-and-query/_index.md
+++ b/content/develop/interact/search-and-query/_index.md
@@ -45,9 +45,9 @@ Here are the next steps to get you started:
## Enable the Redis Query Engine
-The Redis Query Engine is available in Redis Community Edition, Redis Software, and Redis Cloud.
+The Redis Query Engine is available in Redis Open Source, Redis Software, and Redis Cloud.
See
-[Install Redis Community Edition]({{< relref "/operate/oss_and_stack/install/install-stack" >}}) or
+[Install Redis Open Source]({{< relref "/operate/oss_and_stack/install/install-stack" >}}) or
[Install Redis Enterprise]({{< relref "/operate/rs/installing-upgrading/install" >}})
for full installation instructions.
diff --git a/content/develop/interact/search-and-query/administration/configuration.md b/content/develop/interact/search-and-query/administration/configuration.md
index 835ff3cc92..93cb069fb6 100644
--- a/content/develop/interact/search-and-query/administration/configuration.md
+++ b/content/develop/interact/search-and-query/administration/configuration.md
@@ -16,11 +16,11 @@ title: Configuration parameters
weight: 1
---
{{< note >}}
-As of Redis Community Edition (CE) 8.0, configuration parameters for Redis Query Engine (RQE) are now set in the following ways:
+As of Redis 8 in Redis Open Source (Redis 8), configuration parameters for the time series data structure are now set in the following ways:
* At load time via your `redis.conf` file.
* At run time (where applicable) using the [`CONFIG SET`]({{< relref "/commands/config-set" >}}) command.
-Also, CE 8.0 persists RQE configuration parameters just like any other configuration parameters (for example, using the [`CONFIG REWRITE`]({{< relref "/commands/config-rewrite/" >}}) command).
+Also, Redis 8 persists RQE configuration parameters just like any other configuration parameters (e.g., using the [`CONFIG REWRITE`]({{< relref "/commands/config-rewrite/" >}}) command).
{{< /note >}}
## RQE configuration parameters
@@ -78,7 +78,7 @@ The following table summarizes which configuration parameters can be set at run-
| FORK_GC_CLEAN_NUMERIC_EMPTY_NODES | Deprecated in v8.0.0. | :white_large_square: |||
{{< note >}}
-Parameter names for Redis CE versions < 8.0, while deprecated, will still be supported in version 8.0.
+Parameter names for Redis Open Source versions < 8.0, while deprecated, will still be supported in Redis 8.
{{< /note >}}
---
@@ -237,7 +237,7 @@ Type: integer
Valid range: `[1 .. 9,223,372,036,854,775,807]`
-Redis CE default: `100`
+Redis Open Source default: `100`
Redis Software default: `-1` (unlimited)
@@ -269,7 +269,7 @@ Type: integer
Valid range: `[1 .. 9,223,372,036,854,775,807]`
-Redis CE default: `-1` (unlimited)
+Redis Open Source default: `-1` (unlimited)
Redis Software default: `-1` (unlimited)
@@ -312,7 +312,7 @@ Type: integer
Valid range: `[1 .. 9,223,372,036,854,775,807]`
-Redis CE default: `1000000`
+Redis Open Source default: `1000000`
Redis Software default: `1000000`
@@ -358,7 +358,7 @@ Type: integer
Valid range: `[2 .. 4,294,967,295]`
-Redis CE default: `4`
+Redis Open Source default: `4`
Redis Software and Redis Cloud default: `2`
@@ -457,7 +457,7 @@ Type: integer
Value range: `[1 .. 9,223,372,036,854,775,807]`
-Redis CE default: `500`
+Redis Open Source default: `500`
Redis Software default: `500`
@@ -541,7 +541,7 @@ Default: `0`
## Set configuration parameters at module load-time (deprecated)
-These methods are deprecated beginning with Redis CE v8.0.0.
+These methods are deprecated beginning with Redis 8.
Setting configuration parameters at load-time is done by appending arguments after the `--loadmodule` argument when starting a server from the command line, or after the `loadmodule` directive in a Redis config file. For example:
@@ -565,7 +565,7 @@ $ redis-server --loadmodule ./redisearch.so [OPT VAL]...
## Set configuration parameters at run-time (for supported parameters, deprecated)
-These methods are deprecated beginning with Redis CE v8.0.0.
+These methods are deprecated beginning with Redis 8.
RQE exposes the `FT.CONFIG` endpoint to allow for the setting and retrieval of configuration parameters at run-time.
diff --git a/content/develop/interact/search-and-query/administration/design.md b/content/develop/interact/search-and-query/administration/design.md
index 2791100923..09ae618240 100644
--- a/content/develop/interact/search-and-query/administration/design.md
+++ b/content/develop/interact/search-and-query/administration/design.md
@@ -17,7 +17,7 @@ title: Internal design
weight: 1
---
-Redis Community Edition ("CE") implements inverted indexes on top of Redis, but unlike previous implementations of Redis inverted indexes, it uses a custom data encoding that allows more memory and CPU efficient searches, and more advanced search features.
+Redis Open Source implements inverted indexes on top of Redis, but unlike previous implementations of Redis inverted indexes, it uses a custom data encoding that allows more memory and CPU efficient searches, and more advanced search features.
This document details some of the design choices and how these features are implemented.
@@ -41,7 +41,7 @@ An [inverted index](https://en.wikipedia.org/wiki/Inverted_index) is the data st
When a search is performed, either a single index is traversed, or the intersection or union of two or more indexes is traversed. Classic Redis implementations of search engines use sorted sets as inverted indexes. This works but has significant memory overhead, and it also does not allow for encoding of offsets, as explained above.
-Redis CE uses string DMA (see above) to efficiently encode inverted indexes. It combines [delta encoding](https://en.wikipedia.org/wiki/Delta_encoding) and [varint encoding](https://developers.google.com/protocol-buffers/docs/encoding#varints) to encode entries, minimizing space used for indexes, while keeping decompression and traversal efficient.
+Redis Open Source uses string DMA (see above) to efficiently encode inverted indexes. It combines [delta encoding](https://en.wikipedia.org/wiki/Delta_encoding) and [varint encoding](https://developers.google.com/protocol-buffers/docs/encoding#varints) to encode entries, minimizing space used for indexes, while keeping decompression and traversal efficient.
For each hit (document/word entry), the following items are encoded:
@@ -134,7 +134,7 @@ As of release 0.6, the implementation uses a multi-level range tree, saving rang
Another important feature for searching and querying is auto-completion or suggestion. It allows you to create dictionaries of weighted terms, and then query them for completion suggestions to a given user prefix. For example, if you put the term “lcd tv” into a dictionary, sending the prefix “lc” will return it as a result. The dictionary is modeled as a compressed trie (prefix tree) with weights, that is traversed to find the top suffixes of a prefix.
-Redis CE also allows for fuzzy suggestions, meaning you can get suggestions to user prefixes even if the user has a typo in the prefix. This is enabled using a Levenshtein automaton, allowing efficient searching of a dictionary for all terms within a maximal Levenshtein distance of a term or prefix. Suggestions are weighted based on both their original score and their distance from a prefix typed by the user. Only suggestions where the prefix is up to one Levenshtein distance away from the typed prefix are supported for performance reasons.
+Redis Open Source also allows for fuzzy suggestions, meaning you can get suggestions to user prefixes even if the user has a typo in the prefix. This is enabled using a Levenshtein automaton, allowing efficient searching of a dictionary for all terms within a maximal Levenshtein distance of a term or prefix. Suggestions are weighted based on both their original score and their distance from a prefix typed by the user. Only suggestions where the prefix is up to one Levenshtein distance away from the typed prefix are supported for performance reasons.
However, since searching for fuzzy prefixes, especially very short ones, will traverse an enormous amount of suggestions (in fact, fuzzy suggestions for any single letter will traverse the entire dictionary!), it is recommended that you use this feature carefully, and only when considering the performance penalty it incurs. Since Redis is single threaded, blocking it for any amount of time means no other queries can be processed at that time.
diff --git a/content/develop/interact/search-and-query/administration/overview.md b/content/develop/interact/search-and-query/administration/overview.md
index 213c2724db..fde6ac9ee8 100644
--- a/content/develop/interact/search-and-query/administration/overview.md
+++ b/content/develop/interact/search-and-query/administration/overview.md
@@ -9,7 +9,7 @@ categories:
- oss
- kubernetes
- clients
-description: 'Technical overview of the search and query features of Redis Community Edition'
+description: 'Technical overview of the search and query features of Redis Open Source'
linkTitle: Technical overview
title: Technical overview
weight: 1
@@ -17,7 +17,7 @@ weight: 1
## Abstract
-Redis Query Engine ("RQE") is a powerful text search and secondary indexing engine that is built on top of Redis Community Edition.
+Redis Query Engine ("RQE") is a powerful text search and secondary indexing engine that is built on top of Redis Open Source.
Unlike other Redis search libraries, it does not use the internal data structures of Redis such as sorted sets. Using its own highly optimized data structures and algorithms, it allows for advanced search features, high performance, and a low memory footprint. It can perform simple text searches, as well as complex structured queries, filtering by numeric properties and geographical distances.
@@ -283,7 +283,7 @@ Highlighting will highlight the found term and its variants with a user-defined
## Autocomplete
-Another important feature for Redis CE is its autocomplete engine. This allows users to create dictionaries of weighted terms, and then query them for completion suggestions to a given user prefix. Completions can have payloads, which are user-provided pieces of data that can be used for display. For example, completing the names of users, it is possible to add extra metadata about users to be displayed.
+Another important feature for Redis Open Source is its autocomplete engine. This allows users to create dictionaries of weighted terms, and then query them for completion suggestions to a given user prefix. Completions can have payloads, which are user-provided pieces of data that can be used for display. For example, completing the names of users, it is possible to add extra metadata about users to be displayed.
For example, if a user starts to put the term “lcd tv” into a dictionary, sending the prefix “lc” will return the full term as a result. The dictionary is modeled as a compact trie (prefix tree) with weights, which is traversed to find the top suffixes of a prefix.
diff --git a/content/develop/interact/search-and-query/advanced-concepts/_index.md b/content/develop/interact/search-and-query/advanced-concepts/_index.md
index c4d72551c5..d0f89aeecb 100644
--- a/content/develop/interact/search-and-query/advanced-concepts/_index.md
+++ b/content/develop/interact/search-and-query/advanced-concepts/_index.md
@@ -16,7 +16,7 @@ title: Advanced concepts
weight: 7
---
-Redis Community Edition supports the following Redis Query Engine features. This article provides you an overview.
+Redis Open Source supports the following Redis Query Engine features. This article provides you an overview.
## Indexing features
@@ -54,10 +54,10 @@ Redis Community Edition supports the following Redis Query Engine features. This
## Cluster support
-The Redis Query Engine features of Redis Community Edition are also available for distributed databases that can scale to billions of documents and hundreds of servers.
+The Redis Query Engine features of Redis Open Source are also available for distributed databases that can scale to billions of documents and hundreds of servers.
## Supported platforms
-Redis Community Edition is developed and tested on Linux and macOS on x86_64 CPUs.
+Redis Open Source is developed and tested on Linux and macOS on x86_64 CPUs.
Atom CPUs are not supported.
diff --git a/content/develop/interact/search-and-query/advanced-concepts/chinese.md b/content/develop/interact/search-and-query/advanced-concepts/chinese.md
index 2fabc5128a..774206a96e 100644
--- a/content/develop/interact/search-and-query/advanced-concepts/chinese.md
+++ b/content/develop/interact/search-and-query/advanced-concepts/chinese.md
@@ -9,7 +9,7 @@ categories:
- oss
- kubernetes
- clients
-description: Chinese support for searching and querying in Redis Community Edition
+description: Chinese support for searching and querying in Redis Open Source
linkTitle: Chinese
title: Chinese support
weight: 15
diff --git a/content/develop/interact/search-and-query/advanced-concepts/dialects.md b/content/develop/interact/search-and-query/advanced-concepts/dialects.md
index c8dfaecb59..4891096cb5 100644
--- a/content/develop/interact/search-and-query/advanced-concepts/dialects.md
+++ b/content/develop/interact/search-and-query/advanced-concepts/dialects.md
@@ -15,10 +15,10 @@ title: Query dialects
weight: 5
---
-Redis Community Edition (CE) currently supports four query dialects for use with the [`FT.SEARCH`]({{< relref "/commands/ft.search/" >}}), [`FT.AGGREGATE`]({{< relref "/commands/ft.aggregate/" >}}), and other Redis Query Engine commands.
+Redis Open Source currently supports four query dialects for use with the [`FT.SEARCH`]({{< relref "/commands/ft.search/" >}}), [`FT.AGGREGATE`]({{< relref "/commands/ft.aggregate/" >}}), and other Redis Query Engine commands.
Dialects provide for enhancing the query API incrementally, introducing innovative behaviors and new features that support new use cases in a way that does not break the API for existing applications.
-{{< note >}}Dialects 1, 3, and 4 are deprecated in CE version 8. However, DIALECT 1 remains the default.
+{{< note >}}Dialects 1, 3, and 4 are deprecated in Redis 8 in Redis Open Source. However, DIALECT 1 remains the default.
{{< /note >}}
## `DIALECT 1` (Deprecated)
diff --git a/content/develop/interact/search-and-query/advanced-concepts/geo.md b/content/develop/interact/search-and-query/advanced-concepts/geo.md
index 96e8fe5f87..a5e2193d7b 100644
--- a/content/develop/interact/search-and-query/advanced-concepts/geo.md
+++ b/content/develop/interact/search-and-query/advanced-concepts/geo.md
@@ -58,7 +58,7 @@ for geospatial data:
- [`GEO`](#geo): This uses a simple format where individual geospatial
points are specified as numeric longitude-latitude pairs.
-- [`GEOSHAPE`](#geoshape): [Redis Community Edition]({{< relref "/operate/oss_and_stack" >}}) also
+- [`GEOSHAPE`](#geoshape): [Redis Open Source]({{< relref "/operate/oss_and_stack" >}}) also
supports `GEOSHAPE` indexing in v7.2 and later.
This uses a subset of the
[Well-Known Text (WKT)](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry)
diff --git a/content/develop/interact/search-and-query/advanced-concepts/highlight.md b/content/develop/interact/search-and-query/advanced-concepts/highlight.md
index d257dcda52..9340bf6111 100644
--- a/content/develop/interact/search-and-query/advanced-concepts/highlight.md
+++ b/content/develop/interact/search-and-query/advanced-concepts/highlight.md
@@ -15,7 +15,7 @@ title: Highlighting
weight: 7
---
-Redis Community Edition uses advanced algorithms for highlighting and summarizing, which enable only the relevant portions of a document to appear in response to a search query. This feature allows users to immediately understand the relevance of a document to their search criteria, typically highlighting the matching terms in bold text.
+Redis Open Source uses advanced algorithms for highlighting and summarizing, which enable only the relevant portions of a document to appear in response to a search query. This feature allows users to immediately understand the relevance of a document to their search criteria, typically highlighting the matching terms in bold text.
## Command syntax
diff --git a/content/develop/interact/search-and-query/advanced-concepts/phonetic_matching.md b/content/develop/interact/search-and-query/advanced-concepts/phonetic_matching.md
index 7b6c54c0c4..8678063b07 100644
--- a/content/develop/interact/search-and-query/advanced-concepts/phonetic_matching.md
+++ b/content/develop/interact/search-and-query/advanced-concepts/phonetic_matching.md
@@ -19,7 +19,7 @@ Phonetic matching, for example "Jon" vs. "John", allows searching for terms base
Phonetic matching is based on the use of a phonetic algorithm. A phonetic algorithm transforms the input term to an approximate representation of its pronunciation. This allows terms to be indexed and searched by their pronunciation.
-As of v1.4, Redis Query Engine, which is included in Redis Community Edition, provides phonetic matching of text fields specified with the `PHONETIC` attribute. This causes the terms in such fields to be indexed both by their textual value as well as their phonetic approximation.
+As of v1.4, Redis Query Engine, which is included in Redis Open Source, provides phonetic matching of text fields specified with the `PHONETIC` attribute. This causes the terms in such fields to be indexed both by their textual value as well as their phonetic approximation.
Performing a search on `PHONETIC` fields will, by default, also return results for phonetically similar terms. This behavior can be controlled with the [`$phonetic` query attribute]({{< relref "/develop/interact/search-and-query/query/#query-attributes" >}}).
diff --git a/content/develop/interact/search-and-query/advanced-concepts/scoring.md b/content/develop/interact/search-and-query/advanced-concepts/scoring.md
index ba2682272b..976cc0836e 100644
--- a/content/develop/interact/search-and-query/advanced-concepts/scoring.md
+++ b/content/develop/interact/search-and-query/advanced-concepts/scoring.md
@@ -17,7 +17,7 @@ weight: 8
When searching, documents are scored based on their relevance to the query. The score is a floating point number between 0.0 and 1.0, where 1.0 is the highest score. The score is returned as part of the search results and can be used to sort the results.
-Redis Community Edition comes with a few very basic scoring functions to evaluate document relevance. They are all based on document scores and term frequency. This is regardless of the ability to use [sortable fields]({{< relref "/develop/interact/search-and-query/advanced-concepts/sorting" >}}). Scoring functions are specified by adding the `SCORER {scorer_name}` argument to a search query.
+Redis Open Source comes with a few very basic scoring functions to evaluate document relevance. They are all based on document scores and term frequency. This is regardless of the ability to use [sortable fields]({{< relref "/develop/interact/search-and-query/advanced-concepts/sorting" >}}). Scoring functions are specified by adding the `SCORER {scorer_name}` argument to a search query.
If you prefer a custom scoring function, it is possible to add more functions using the [extension API]({{< relref "/develop/interact/search-and-query/administration/extensions" >}}).
diff --git a/content/develop/interact/search-and-query/advanced-concepts/stemming.md b/content/develop/interact/search-and-query/advanced-concepts/stemming.md
index e2fd04d984..3815d400a0 100644
--- a/content/develop/interact/search-and-query/advanced-concepts/stemming.md
+++ b/content/develop/interact/search-and-query/advanced-concepts/stemming.md
@@ -106,7 +106,7 @@ Indexing a Chinese document is different than indexing a document in most other
Chinese tokenization is done by scanning the input text and checking every character or sequence of characters against a dictionary of predefined terms and determining the most likely match based on the surrounding terms and characters.
-Redis Community Edition makes use of the [Friso](https://github.com/lionsoul2014/friso) chinese tokenization library for this purpose. This is largely transparent to the user and often no additional configuration is required.
+Redis Open Source makes use of the [Friso](https://github.com/lionsoul2014/friso) chinese tokenization library for this purpose. This is largely transparent to the user and often no additional configuration is required.
## Using custom dictionaries
diff --git a/content/develop/interact/search-and-query/advanced-concepts/stopwords.md b/content/develop/interact/search-and-query/advanced-concepts/stopwords.md
index 3b3ec74e78..c93bdb4c60 100644
--- a/content/develop/interact/search-and-query/advanced-concepts/stopwords.md
+++ b/content/develop/interact/search-and-query/advanced-concepts/stopwords.md
@@ -15,7 +15,7 @@ title: Stop words
weight: 1
---
-Redis Community Edition has a default list of [stop words](https://en.wikipedia.org/wiki/Stop_words). These are words that are usually so common that they do not add much information to search, but take up a lot of space and CPU time in the index.
+Redis Open Source has a default list of [stop words](https://en.wikipedia.org/wiki/Stop_words). These are words that are usually so common that they do not add much information to search, but take up a lot of space and CPU time in the index.
When indexing, stop words are discarded and not indexed. When searching, they are also ignored and treated as if they were not sent to the query processor. This is done when parsing the query.
diff --git a/content/develop/interact/search-and-query/advanced-concepts/synonyms.md b/content/develop/interact/search-and-query/advanced-concepts/synonyms.md
index 63f1dc0877..b7324ea501 100644
--- a/content/develop/interact/search-and-query/advanced-concepts/synonyms.md
+++ b/content/develop/interact/search-and-query/advanced-concepts/synonyms.md
@@ -9,13 +9,13 @@ categories:
- oss
- kubernetes
- clients
-description: Details on synonym support with Redis Community Edition
+description: Details on synonym support with Redis Open Source
linkTitle: Synonym
title: Synonym support
weight: 11
---
-Redis Community Edition supports synonyms. That is, searching for synonym words defined by the synonym data structure.
+Redis Open Source supports synonyms. That is, searching for synonym words defined by the synonym data structure.
The synonym data structure is a set of groups, each of which contains synonym terms. For example, the following synonym data structure contains three groups, and each group contains three synonym terms:
diff --git a/content/develop/interact/search-and-query/basic-constructs/_index.md b/content/develop/interact/search-and-query/basic-constructs/_index.md
index 1ac1aa577c..39be9bc2ed 100644
--- a/content/develop/interact/search-and-query/basic-constructs/_index.md
+++ b/content/develop/interact/search-and-query/basic-constructs/_index.md
@@ -15,7 +15,7 @@ title: Basic constructs
weight: 2
---
-You can use Redis Community Edition as a powerful search and query engine. It allows you to create indexes and perform efficient queries on structured data, as well as text-based and vector searches on unstructured data.
+You can use Redis Open Source as a powerful search and query engine. It allows you to create indexes and perform efficient queries on structured data, as well as text-based and vector searches on unstructured data.
This section introduces the basic constructs of querying and searching, and explains how to use them to build powerful search capabilities into your applications.
diff --git a/content/develop/interact/search-and-query/basic-constructs/field-and-type-options.md b/content/develop/interact/search-and-query/basic-constructs/field-and-type-options.md
index 3f1912a200..6380aaaf91 100644
--- a/content/develop/interact/search-and-query/basic-constructs/field-and-type-options.md
+++ b/content/develop/interact/search-and-query/basic-constructs/field-and-type-options.md
@@ -16,7 +16,7 @@ weight: 2
---
-Redis Community Edition provides various field types that allow you to store and search different kinds of data in your indexes. This page explains the available field types, their characteristics, and how they can be used effectively.
+Redis Open Source provides various field types that allow you to store and search different kinds of data in your indexes. This page explains the available field types, their characteristics, and how they can be used effectively.
## Numeric fields
diff --git a/content/develop/interact/search-and-query/best-practices/dev-to-prod-best-practices.md b/content/develop/interact/search-and-query/best-practices/dev-to-prod-best-practices.md
index dd3208fa2a..b0ca0c2d52 100644
--- a/content/develop/interact/search-and-query/best-practices/dev-to-prod-best-practices.md
+++ b/content/develop/interact/search-and-query/best-practices/dev-to-prod-best-practices.md
@@ -12,7 +12,7 @@ linkTitle: RQE DEV to PROD
weight: 2
---
-Transitioning a Redis Community Edition with Redis Query Engine (RQE) environment from development to production requires thoughtful consideration of configuration, performance tuning, and resource allocation. This guide outlines key practices to ensure your Redis deployment operates optimally under production workloads.
+Transitioning a Redis Open Source with Redis Query Engine (RQE) environment from development to production requires thoughtful consideration of configuration, performance tuning, and resource allocation. This guide outlines key practices to ensure your Redis deployment operates optimally under production workloads.
## Configuration parameter considerations
@@ -102,4 +102,4 @@ Production environments must be sized for peak load scenarios to ensure performa
2. Autoscaling:
- Consider using autoscaling strategies in cloud environments to dynamically adjust resources based on load.
-By following these best practices, you can ensure a smooth and efficient transition from development to production with Redis Community Edition and RQE. Proper configuration, rigorous testing, and careful resource planning are critical to delivering a reliable and high-performance Redis deployment.
+By following these best practices, you can ensure a smooth and efficient transition from development to production with Redis Open Source and RQE. Proper configuration, rigorous testing, and careful resource planning are critical to delivering a reliable and high-performance Redis deployment.
diff --git a/content/develop/interact/search-and-query/deprecated/development.md b/content/develop/interact/search-and-query/deprecated/development.md
index 678c0fbc58..a7b7ed3443 100644
--- a/content/develop/interact/search-and-query/deprecated/development.md
+++ b/content/develop/interact/search-and-query/deprecated/development.md
@@ -145,7 +145,7 @@ Run the following from the project root dir:
```make build``` will build RediSearch.
-`make build COORD=1` will build Redis Community Edition RediSearch Coordinator.
+`make build COORD=1` will build Redis Open Source RediSearch Coordinator.
`make build STATIC=1` will build as a static library.
diff --git a/content/develop/interact/search-and-query/deprecated/payloads.md b/content/develop/interact/search-and-query/deprecated/payloads.md
index f3904927d9..e6956b2196 100644
--- a/content/develop/interact/search-and-query/deprecated/payloads.md
+++ b/content/develop/interact/search-and-query/deprecated/payloads.md
@@ -19,7 +19,7 @@ weight: 12
The payload feature is deprecated in 2.0
{{% /alert %}}
-Usually, Redis Community Edition stores documents as hashes or JSON. But if you want to access some data for aggregation or scoring functions, Redis can store that data as an inline payload. This will allow us to evaluate the properties of a document for scoring purposes at a very low cost.
+Usually, Redis Open Source stores documents as hashes or JSON. But if you want to access some data for aggregation or scoring functions, Redis can store that data as an inline payload. This will allow us to evaluate the properties of a document for scoring purposes at a very low cost.
Since the scoring functions already have access to the DocumentMetaData, which contains document flags and score, Redis can add custom payloads that can be evaluated in run-time.
diff --git a/content/develop/interact/search-and-query/indexing/_index.md b/content/develop/interact/search-and-query/indexing/_index.md
index 2663b58b2d..d8845e10ea 100644
--- a/content/develop/interact/search-and-query/indexing/_index.md
+++ b/content/develop/interact/search-and-query/indexing/_index.md
@@ -15,7 +15,7 @@ title: Indexing
weight: 3
---
-In addition to indexing Redis hashes, Redis Community Edition can also index JSON documents.
+In addition to indexing Redis hashes, Redis Open Source can also index JSON documents.
## Create index with JSON schema
diff --git a/content/develop/interact/search-and-query/query-use-cases/_index.md b/content/develop/interact/search-and-query/query-use-cases/_index.md
index 8b6c36c20e..f5d3946a61 100644
--- a/content/develop/interact/search-and-query/query-use-cases/_index.md
+++ b/content/develop/interact/search-and-query/query-use-cases/_index.md
@@ -17,7 +17,7 @@ weight: 5
**Application search and external secondary index**
-Redis Community Edition supports application search, whether the source of record is Redis or another database. In the latter case, you can use Redis as an external secondary index for numeric or full-text data.
+Redis Open Source supports application search, whether the source of record is Redis or another database. In the latter case, you can use Redis as an external secondary index for numeric or full-text data.
**Secondary index for Redis data**
diff --git a/content/develop/interact/search-and-query/query/_index.md b/content/develop/interact/search-and-query/query/_index.md
index c05c1d1f57..aaaab886f3 100644
--- a/content/develop/interact/search-and-query/query/_index.md
+++ b/content/develop/interact/search-and-query/query/_index.md
@@ -16,7 +16,7 @@ title: Query data
weight: 5
---
-Redis Community Edition distinguishes between the [FT.SEARCH]({{< relref "/commands/ft.search" >}}) and [FT.AGGREGATE]({{< relref "/commands/ft.aggregate" >}}) query commands. You should use [FT.SEARCH]({{< relref "/commands/ft.search" >}}) if you want to perform selections and projections only. If you also need to apply mapping functions, group, or aggregate data, use the [FT.AGGREGATE]({{< relref "/commands/ft.aggregate" >}}) command.
+Redis Open Source distinguishes between the [FT.SEARCH]({{< relref "/commands/ft.search" >}}) and [FT.AGGREGATE]({{< relref "/commands/ft.aggregate" >}}) query commands. You should use [FT.SEARCH]({{< relref "/commands/ft.search" >}}) if you want to perform selections and projections only. If you also need to apply mapping functions, group, or aggregate data, use the [FT.AGGREGATE]({{< relref "/commands/ft.aggregate" >}}) command.
* **Selection**: A selection allows you to return all documents that fulfill specific criteria.
* **Projection**: Projections are used to return specific fields of the result set. You can also map/project to calculated field values.
diff --git a/content/develop/interact/search-and-query/query/geo-spatial.md b/content/develop/interact/search-and-query/query/geo-spatial.md
index d1473bbe8e..63ea965629 100644
--- a/content/develop/interact/search-and-query/query/geo-spatial.md
+++ b/content/develop/interact/search-and-query/query/geo-spatial.md
@@ -15,7 +15,7 @@ title: Geospatial queries
weight: 4
---
-The geospatial feature in Redis Community Edition allows you to query for data associated with geographic locations. You can either query for locations within a specific radius or based on geometric shapes, such as polygons. A polygon shape could, for instance, represent a lake or the layout of a building.
+The geospatial feature in Redis Open Source allows you to query for data associated with geographic locations. You can either query for locations within a specific radius or based on geometric shapes, such as polygons. A polygon shape could, for instance, represent a lake or the layout of a building.
The examples in this article use the following schema:
diff --git a/content/develop/interact/search-and-query/query/vector-search.md b/content/develop/interact/search-and-query/query/vector-search.md
index 4178cd8c88..bf0f5e8bc8 100644
--- a/content/develop/interact/search-and-query/query/vector-search.md
+++ b/content/develop/interact/search-and-query/query/vector-search.md
@@ -15,7 +15,7 @@ title: Vector search
weight: 5
---
-This article gives you a good overview of how to perform vector search queries with the Redis Query Engine, which is part of Redis Community Edition. See the [Redis as a vector database quick start guide]({{< relref "/develop/get-started/vector-database" >}}) for more information about Redis as a vector database. You can also find more detailed information about all the parameters in the [vector reference documentation]({{< relref "/develop/interact/search-and-query/advanced-concepts/vectors" >}}).
+This article gives you a good overview of how to perform vector search queries with the Redis Query Engine, which is part of Redis Open Source. See the [Redis as a vector database quick start guide]({{< relref "/develop/get-started/vector-database" >}}) for more information about Redis as a vector database. You can also find more detailed information about all the parameters in the [vector reference documentation]({{< relref "/develop/interact/search-and-query/advanced-concepts/vectors" >}}).
A vector search query on a vector field allows you to find all vectors in a vector space that are close to a given vector. You can query for the k-nearest neighbors or vectors within a given radius.
diff --git a/content/develop/tools/insight/_index.md b/content/develop/tools/insight/_index.md
index 14cc1a16e2..c64dd78593 100644
--- a/content/develop/tools/insight/_index.md
+++ b/content/develop/tools/insight/_index.md
@@ -35,7 +35,7 @@ Redis Insight is a powerful tool for visualizing and optimizing data in Redis, m
* Automatically discover and add your local Redis databases (that use standalone connection type and do not require authentication).
* Discover your databases in Redis Enterprise Cluster and databases with Flexible plans in Redis Cloud.
-* Use a form to enter your connection details and add any Redis database running anywhere (including Redis Community Edition Cluster or Sentinel).
+* Use a form to enter your connection details and add any Redis database running anywhere (including Redis Open Source cluster or sentinel).
* Connect to a Redis Data Integration (RDI) management plane, create, test, and deploy RDI pipelines, and view RDI statistics.
@@ -94,8 +94,8 @@ The CLI is accessible at any time within the application.
### Workbench
Workbench is an advanced command line interface with intelligent command auto-complete and complex data visualization support.
-* Built-in guides: you can conveniently discover Redis and Redis Community Edition features using the built-in guides.
-* Command auto-complete support for all features in Redis and Redis Community Edition.
+* Built-in guides: you can conveniently discover Redis and Redis Open Source features using the built-in guides.
+* Command auto-complete support for all features in Redis and Redis Open Source.
* Advanced, schema-aware auto-complete for Redis Query Engine, which provides for faster query building with context-sensitive suggestions that recognize indexes, schemas, and fields based on your current query. Start typing any Redis Query Engine command in to try this feature. See below for an example of an in-progress `FT.SEARCH` command.
@@ -129,7 +129,7 @@ View and manage the list of consumer groups. See existing consumers in a given c
### Search features
-If you're using the indexing, querying, or full-text search features of Redis Community Edition, Redis Insight provides UI controls to quickly and conveniently run search queries against a preselected index. You can also create a secondary index of your data in a dedicated pane.
+If you're using the indexing, querying, or full-text search features of Redis Open Source, Redis Insight provides UI controls to quickly and conveniently run search queries against a preselected index. You can also create a secondary index of your data in a dedicated pane.
diff --git a/content/develop/tools/redis-for-vscode/_index.md b/content/develop/tools/redis-for-vscode/_index.md
index 2ce173b76d..9f1c46f9e1 100644
--- a/content/develop/tools/redis-for-vscode/_index.md
+++ b/content/develop/tools/redis-for-vscode/_index.md
@@ -136,7 +136,7 @@ For strings, hashes, lists, sets, and sorted sets, the extension supports numero
{{< image filename="images/dev/connect/vscode/vscode-edit-value-formatters.png" >}}
-Also for Hash keys, you can set per-field TTLs (highlighted in yellow in the image above), a new feature added to Redis Community Edition 7.4.
+Also for Hash keys, you can set per-field TTLs (highlighted in yellow in the image above), a new feature added to Redis Open Source 7.4.
## CLI tool {#cli}
diff --git a/content/develop/tools/redis-for-vscode/release-notes/v1.0.0.md b/content/develop/tools/redis-for-vscode/release-notes/v1.0.0.md
index d026d4fab9..54e3a69a9d 100644
--- a/content/develop/tools/redis-for-vscode/release-notes/v1.0.0.md
+++ b/content/develop/tools/redis-for-vscode/release-notes/v1.0.0.md
@@ -14,7 +14,7 @@ Redis for VS Code is the official Visual Studio Code extension that provides an
### Headlines
-* Universal Redis Support: Connect to any Redis instance, including Redis Community Edition, Redis Cloud, Redis Software, and Redis on Azure Cache.
+* Universal Redis Support: Connect to any Redis instance, including Redis Open Source, Redis Cloud, Redis Software, and Redis on Azure Cache.
* Advanced Connectivity: Supports TLS certificates and SSH tunnels, with an option for automatic data decompression for GZIP, SNAPPY, Brotli, and more.
@@ -28,7 +28,7 @@ Redis for VS Code is the official Visual Studio Code extension that provides an
- Database connections:
- - Connect to any Redis instance, including Redis Community Edition, Redis Cloud, Redis Software, and Redis on Azure Cache.
+ - Connect to any Redis instance, including Redis Open Source, Redis Cloud, Redis Software, and Redis on Azure Cache.
- View, edit, and manage your Redis database connections.
diff --git a/content/develop/whats-new/8-0-rc-1.md b/content/develop/whats-new/8-0.md
similarity index 84%
rename from content/develop/whats-new/8-0-rc-1.md
rename to content/develop/whats-new/8-0.md
index 9d578ec1fa..2db79b4355 100644
--- a/content/develop/whats-new/8-0-rc-1.md
+++ b/content/develop/whats-new/8-0.md
@@ -1,18 +1,26 @@
---
-title: Redis 8.0-RC1
+title: Redis 8.0
alwaysopen: false
+aliases:
+- /develop/whats-new/8-0-rc-1/
categories:
- docs
- operate
- rs
- rc
-description: What's new in Redis 8.0-RC1
-linkTitle: What's new in Redis 8.0-RC1
+description: What's new in Redis 8 in Redis Open Source
+linkTitle: What's new in Redis 8.0
weight: 5
---
## Highlights
+- **Name change**: Redis Community Edition is now **Redis Open Source**
+- **License options**:
+ - Redis Source Available License 2.0 (RSALv2)
+ - Server Side Public License v1 (SSPLv1)
+ - GNU Affero General Public License (AGPLv3)
+
- **Integrated modules** now part of core:
- JSON
- Probabilistic: Bloom, Cuckoo, Count-min sketch, Top-K, and t-digest
@@ -55,7 +63,7 @@ weight: 5
## Packaging
-Redis 8.0-RC1 is available in the following distributions:
+Redis 8 in Redis Open Source is available in the following distributions:
- [Docker](https://hub.docker.com/_/redis)
- APT
diff --git a/content/develop/whats-new/_index.md b/content/develop/whats-new/_index.md
index 08a3728280..0bc6edca0f 100644
--- a/content/develop/whats-new/_index.md
+++ b/content/develop/whats-new/_index.md
@@ -123,14 +123,14 @@ weight: 10
* Updates to the [key eviction]({{< relref "/develop/reference/eviction" >}}) page.
* Updates to the Redis Insight page related to its new Redis Query Engine auto-completion [feature]({{< relref "/develop/tools/insight#workbench">}}).
* Restructured and added testable connection examples to the [client pages]({{< relref "/develop/clients" >}}).
-* Added [Redis Community Edition]({{< relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisce" >}}) and [Redis Stack]({{< relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisstack" >}}) release notes.
+* Added [Redis Open Source]({{< relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisce" >}}) and [Redis Stack]({{< relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisstack" >}}) release notes.
* Added new [Redis for AI]({{< relref "/develop/ai" >}}) page.
* Added new [Predis (PHP client library)]({{< relref "/develop/clients/php" >}}) page.
## Q3 2024 (July - September) Updates
* Updated the [RAG with Redis quick start guide]({{< relref "/develop/get-started/rag" >}}).
-* Updates for [Redis Community Edition version 7.4]({{< relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisce" >}}).
+* Updates for [Redis Open Source version 7.4]({{< relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisce" >}}).
* Added new [Redis Insight debugging]({{< relref "/develop/tools/insight/debugging" >}}) page.
* Completed a major re-write/restructuring of the [vector indexing page]({{< relref "/develop/interact/search-and-query/advanced-concepts/vectors" >}}).
* Added new [client-side caching page]({{< relref "/develop/clients/client-side-caching" >}}).
diff --git a/content/develop/whats-new/redis-feature-sets.md b/content/develop/whats-new/redis-feature-sets.md
index 6727540144..ca3a8a072e 100644
--- a/content/develop/whats-new/redis-feature-sets.md
+++ b/content/develop/whats-new/redis-feature-sets.md
@@ -17,7 +17,7 @@ To use a new feature introduced in a later feature set, you must upgrade the cor
| Redis feature set | What's new |
|-------------------|------------|
-| **Feature set version:** 8.0-RC1| See [here]({{< relref "/develop/whats-new/8-0-rc-1" >}})|
+| **Feature set version:** 8.0| See [here]({{< relref "/develop/whats-new/8-0" >}})|
| **Feature set version:** 7.4In-memory database for caching & streaming.
diff --git a/layouts/partials/header/products-mobile.html b/layouts/partials/header/products-mobile.html index 4c4de2b2a9..d77c5acf9c 100644 --- a/layouts/partials/header/products-mobile.html +++ b/layouts/partials/header/products-mobile.html @@ -30,7 +30,7 @@In-memory database for caching & streaming.