-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Changed examples deleting Elasticsearch indices #2635
base: master
Are you sure you want to change the base?
Conversation
Preview of modified Markdown: |
@@ -463,11 +463,12 @@ Restart Solr for `solrconfig.xml` changes to take effect. | |||
Elasticsearch schema's templates change, for example, with the addition of new features such as spellchecking. | |||
When this happens, you need to erase the index, update the schema, and rebuild the index. | |||
|
|||
To delete the index, you can use an HTTP request. | |||
To delete the index, use the [delete index REST API](https://www.elastic.co/guide/en/elasticsearch/reference/7.17/indices-delete-index.html). | |||
Use the command as in the following example: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use the command as in the following example: | |
Use the commands as in the following example: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm.. I am not sure how destructive it is when running on elastic.co servers ( if it deletes metadata needed by the service too ?), but if we don't delete everything, we must document better what we delete. These default_
values comes from the template, https://doc.ibexa.co/en/latest/search/search_engines/elasticsearch/configure_elasticsearch/#define-a-template
So with out-of-the-box config, the new documentation is correct. But with changed templates, the commands needs to be adjusted accordingly
Target: master, 4.6, 3.3
Community feedback:
I've verified locally that it works by running the Elasticsearch container and then executing:
which is enough to solve the issue described in https://issues.ibexa.co/browse/IBX-3758, but potentially less desctuctive.