Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Backport 2.19] Fix index name in bitmap filtering docs #9233

Merged
merged 1 commit into from
Feb 17, 2025
Merged

[Backport 2.19] Fix index name in bitmap filtering docs #9233

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions _query-dsl/term/terms.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -256,9 +256,9 @@ Parameter | Data type | Description
**Introduced 2.17**
{: .label .label-purple }

The `terms` query can filter for multiple terms simultaneously. However, when the number of terms in the input filter increases to a large value (around 10,000), the resulting network and memory overhead can become significant, making the query inefficient. In such cases, consider encoding your large terms filter using a [roaring bitmap](https://github.com/RoaringBitmap/RoaringBitmap) for more efficient filtering.
The `terms` query can filter for multiple terms simultaneously. However, when the number of terms in the input filter increases to a large value (around 10,000), the resulting network and memory overhead can become significant, making the query inefficient. In such cases, consider encoding your large terms filter using a [roaring bitmap](https://github.com/RoaringBitmap/RoaringBitmap) for more efficient filtering.

The following example assumes that you have two indexes: a `products` index, which contains all the products sold by a company, and a `customers` index, which stores filters representing customers who own specific products.
The following example assumes that you have two indexes: a `products` index, which contains all the products sold by a company, and a `customers` index, which stores filters representing customers who own specific products.

First, create a `products` index and map `product_id` as a `keyword`:

Expand All @@ -277,7 +277,7 @@ PUT /products
Next, index three documents that correspond to products:

```json
PUT students/_doc/1
PUT /products/_doc/1
{
"name": "Product 1",
"product_id" : "111"
Expand All @@ -286,7 +286,7 @@ PUT students/_doc/1
{% include copy-curl.html %}

```json
PUT students/_doc/2
PUT /products/_doc/2
{
"name": "Product 2",
"product_id" : "222"
Expand All @@ -295,7 +295,7 @@ PUT students/_doc/2
{% include copy-curl.html %}

```json
PUT students/_doc/3
PUT /products/_doc/3
{
"name": "Product 3",
"product_id" : "333"
Expand Down
Loading