This issue is created to track Extension Point implementation.
- Unchecked boxes are not implemented at all.
- Checked boxes have at least a partial implementation complete which addresses the most important use cases; some may need additional work for completeness, which will be identified by a linked issue.
- Extension points highlighted in bold are a priority as they are required for plugin migration
Not all extension points will need to be implemented for Extensions, and will be removed from the list when that determination is made.
The general approach to implementation is:
- Create a
FooExtension interface corresponding to the FooPlugin interface, with the same default implementations.
- During initialization, communicate which interfaces an Extension implements to OpenSearch
- Review existing functionality, usually implemented in the
Node class that runs on OpenSearch bootstrap, where a module iterates over plugins implementing a particular interface and and "registers" the implemented extensions points, adding them to maps/lists, etc.
- Determine whether functionality is primarily local to the extension (the easy case) or integral to OpenSearch (which requires serializing and deserializing via Writable interface) and implement appropriately. For example:
- NamedXContent is local to an extension. The static initializers from OpenSearch are created and no transport communication actually happens.
- RestHandlers are integrated with the OpenSearch RestController. The handled methods and paths must be communicated over transport to OpenSearch to be registered. This is done using Strings.
- Settings are integrated with OpenSearch. The settings must be turned into a Writeable object to be sent over transport, and re-created on the other end. This is done using the WriteableSetting class.
Extension Points applicable to all plugins are defined in the Plugin interface:
The following interfaces also implement custom functionality:
-
ActionPlugin
-
AnalysisPlugin
-
CircuitBreakerPlugin
-
EnginePlugin
-
ExtensiblePlugin
-
IndexStorePlugin
-
IngestPlugin
-
MapperPlugin
-
PersistentTaskPlugin
-
RepositoryPlugin
-
ReloadablePlugin
-
ScriptPlugin
-
SearchPlugin
-
SystemIndexPlugin
This issue is created to track Extension Point implementation.
Not all extension points will need to be implemented for Extensions, and will be removed from the list when that determination is made.
The general approach to implementation is:
FooExtensioninterface corresponding to theFooPlugininterface, with the same default implementations.Nodeclass that runs on OpenSearch bootstrap, where a module iterates over plugins implementing a particular interface and and "registers" the implemented extensions points, adding them to maps/lists, etc.Extension Points applicable to all plugins are defined in the
Plugininterface:The following interfaces also implement custom functionality:
ActionPlugin
AnalysisPlugin
CircuitBreakerPlugin
EnginePlugin
ExtensiblePlugin
IndexStorePlugin
IngestPlugin
MapperPlugin
PersistentTaskPlugin
RepositoryPlugin
ReloadablePlugin
ScriptPlugin
SearchPlugin
SystemIndexPlugin