Skip to content

[9.1][DOCS] Clarify dense vector field update graph availability (#131724) #133672

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

Merged
merged 1 commit into from
Aug 28, 2025
+9 −0
Merged

[9.1][DOCS] Clarify dense vector field update graph availability (#131724) #133672

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
9 changes: 9 additions & 0 deletions docs/reference/elasticsearch/mapping-reference/dense-vector.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -396,9 +396,18 @@ POST /my-bit-vectors/_search?filter_path=hits.hits

To better accommodate scaling and performance needs, updating the `type` setting in `index_options` is possible with the [Update Mapping API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-put-mapping), according to the following graph (jumps allowed):

::::{tab-set}
:::{tab-item} {{stack}} 9.1+
```txt
flat --> int8_flat --> int4_flat --> bbq_flat --> hnsw --> int8_hnsw --> int4_hnsw --> bbq_hnsw
```
:::
:::{tab-item} {{stack}} 9.0
```txt
flat --> int8_flat --> int4_flat --> hnsw --> int8_hnsw --> int4_hnsw
```
:::
::::

For updating all HNSW types (`hnsw`, `int8_hnsw`, `int4_hnsw`, `bbq_hnsw`) the number of connections `m` must either stay the same or increase. For the scalar quantized formats `int8_flat`, `int4_flat`, `int8_hnsw` and `int4_hnsw` the `confidence_interval` must always be consistent (once defined, it cannot change).

Expand Down
Loading