You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference/rest-api.md
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -334,6 +334,12 @@ Updates the configurations of an index. This endpoint follows PUT semantics, whi
334
334
- The indexing settings update is automatically picked up by the indexer nodes once the control plane emits a new indexing plan.
335
335
- The doc mapping update is automatically picked up by the indexer nodes once the control plane emit a new indexing plan.
336
336
337
+
:::warning
338
+
339
+
If you use the ingest or ES bulk API (V2), the old doc mapping will still be used to validate new documents that end up being persisted on existing shards (see [#5738](https://github.com/quickwit-oss/quickwit/issues/5738)).
340
+
341
+
:::
342
+
337
343
Updating the doc mapping doesn't reindex existing data. Queries and results are mapped on a best-effort basis when querying older splits. For more details, check [the reference](updating-mapper.md) out.
Copy file name to clipboardExpand all lines: docs/reference/updating-mapper.md
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,12 @@ Quickwit allows updating the mapping it uses to add more fields to an existing i
6
6
7
7
When you update a doc mapping for an index, Quickwit will restart indexing pipelines to take the changes into account. As both this operation and the document ingestion are asynchronous, there is no strict happens-before relationship between ingestion and update. This means a document ingested just before the update may be indexed according to the newer doc mapper, and document ingested just after the update may be indexed with the older doc mapper.
8
8
9
+
:::warning
10
+
11
+
If you use the ingest or ES bulk API (V2), the old doc mapping will still be used to validate new documents that end up being persisted on existing shards (see [#5738](https://github.com/quickwit-oss/quickwit/issues/5738)).
12
+
13
+
:::
14
+
9
15
## Querying
10
16
11
17
Quickwit always validate queries against the most recent mapping.
0 commit comments