mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-06-28 17:34:17 -04:00
b7e3a1e14b
* delete asciidoc files
* add migrated files
* fix errors
* Disable docs tests
* Clarify release notes page titles
* Revert "Clarify release notes page titles"
This reverts commit 8be688648d.
* 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>
19 lines
938 B
Markdown
19 lines
938 B
Markdown
---
|
|
mapped_pages:
|
|
- https://www.elastic.co/guide/en/elasticsearch/plugins/current/plugin-authors.html
|
|
---
|
|
|
|
# Create Elasticsearch plugins [plugin-authors]
|
|
|
|
{{es}} plugins are modular bits of code that add functionality to {{es}}. Plugins are written in Java and implement Java interfaces that are defined in the source code. Plugins are composed of JAR files and metadata files, compressed in a single zip file.
|
|
|
|
There are two ways to create a plugin:
|
|
|
|
[Creating text analysis plugins with the stable plugin API](/extend/creating-stable-plugins.md)
|
|
: Text analysis plugins can be developed against the stable plugin API to provide {{es}} with custom Lucene analyzers, token filters, character filters, and tokenizers.
|
|
|
|
[Creating classic plugins](/extend/creating-classic-plugins.md)
|
|
: Other plugins can be developed against the classic plugin API to provide custom authentication, authorization, or scoring mechanisms, and more.
|
|
|
|
|
|
|