-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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.
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
[Product documentation] Use default ELSER deployment #204559
Labels
Team:AI Infra
AppEx AI Infrastructure Team
Comments
Pinging @elastic/appex-ai-infra (Team:AI Infra) |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this issue
Jan 8, 2025
## Summary Fix elastic#204559 Use the default ELSER deployment (`.elser-2-elasticsearch`) for the product documentation semantic_text fields instead of maintaining our own custom deployment. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> (cherry picked from commit 015911d)
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this issue
Jan 13, 2025
## Summary Fix elastic#204559 Use the default ELSER deployment (`.elser-2-elasticsearch`) for the product documentation semantic_text fields instead of maintaining our own custom deployment. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
viduni94
pushed a commit
to viduni94/kibana
that referenced
this issue
Jan 23, 2025
## Summary Fix elastic#204559 Use the default ELSER deployment (`.elser-2-elasticsearch`) for the product documentation semantic_text fields instead of maintaining our own custom deployment. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With elastic/elasticsearch#116931, we now have that default
.elser-2-elasticsearch
that can lazily deploy.We should adapt the product documentation indices and its install workflow to use that deployment.
We should make that those changes will not impact customers with the KB already setup, but I think it should be fine given the used model/dep is stored in the index's meta.
The text was updated successfully, but these errors were encountered: