* [docs] Migrate docs from AsciiDoc to Markdown (#123507) * delete asciidoc files * add migrated files * fix errors * Disable docs tests * Clarify release notes page titles * Revert "Clarify release notes page titles" This reverts commit8be688648d
. * Comment out edternal URI images * Clean up query languages landing pages, link to conceptual docs * Add .md to url * Fixes inference processor nesting. --------- Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Co-authored-by: Liam Thompson <leemthompo@gmail.com> Co-authored-by: Martijn Laarman <Mpdreamz@gmail.com> Co-authored-by: István Zoltán Szabó <szabosteve@gmail.com> (cherry picked from commitb7e3a1e14b
) # Conflicts: # docs/build.gradle # docs/reference/migration/index.asciidoc # docs/reference/migration/migrate_9_0.asciidoc # docs/reference/release-notes.asciidoc # docs/reference/release-notes/9.0.0.asciidoc # docs/reference/release-notes/highlights.asciidoc * Fix build file * Really fix build file --------- Co-authored-by: Colleen McGinnis <colleen.j.mcginnis@gmail.com>
2.3 KiB
Plugin management (Cloud Enterprise) [ece-add-plugins]
Plugins extend the core functionality of Elasticsearch. Elastic Cloud Enterprise makes it easy to add plugins to your deployment by providing a number of plugins that work with your version of Elasticsearch. One advantage of these plugins is that you generally don’t have to worry about upgrading plugins when upgrading to a new Elasticsearch version, unless there are breaking changes. The plugins simply are upgraded along with the rest of your deployment.
Adding plugins to a deployment is as simple as selecting it from the list of available plugins, but different versions of Elasticsearch support different plugins. Plugins are available for different purposes, such as:
- National language support, phonetic analysis, and extended unicode support
- Ingesting attachments in common formats and ingesting information about the geographic location of IP addresses
- Adding new field datatypes to Elasticsearch
Additional plugins might be available. If a plugin is listed for your version of Elasticsearch, it can be used.
To add plugins when creating a new deployment:
- Log into the Cloud UI and select Create deployment.
- Make your initial deployment selections, then select Customize Deployment.
- Beneath the Elasticsearch master node, expand the Manage plugins and settings caret.
- Select the plugins you want.
- Select Create deployment.
The deployment spins up with the plugins installed.
To add plugins to an existing deployment:
-
On the Deployments page, select your deployment.
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
-
From your deployment menu, go to the Edit page.
-
Beneath the Elasticsearch master node, expand the Manage plugins and settings caret.
-
Select the plugins that you want.
-
Select Save changes.
There is no downtime when adding plugins to highly available deployments. The deployment is updated with new nodes that have the plugins installed.