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
Describe the bug
We can update a doc mapping with PUT api/v1/indexes/<index id>, indexing pipelines are automatically restarted, but when we hit the ingest V2 endpoint after the update, documents obeying the new doc mapping are likely be considered as invalid by existing shards that still use the previous doc mapping.
Describe the bug
We can update a doc mapping with
PUT api/v1/indexes/<index id>
, indexing pipelines are automatically restarted, but when we hit the ingest V2 endpoint after the update, documents obeying the new doc mapping are likely be considered as invalid by existing shards that still use the previous doc mapping.Steps to reproduce (if applicable)
Test was added in https://github.com/quickwit-oss/quickwit/pull/5739/files
Expected behavior
The best solution is likely to force the recreation of all shards for the existing index
The text was updated successfully, but these errors were encountered: