Right now the response for each node has two main parts:
All built-in analysis components found on the node (found in the node registry)
A break down by available AnalysisPlugins found on that node attributing each analysis component to a specific plugin/module (†)
It can be useful (and efficient) to give user an option to include or exclude individual parts from the response. Typically this can be achieved by introducing new request parameters.
(†) There are some analysis components that do not belong to any specific plugin, these represent the minimal OOTB set of components that are always available – for example when you are developing a plugin and run OpenSearch with that plugin installed using command line ./gradlew run then no additional modules or plugins are available on that node.
Right now the response for each node has two main parts:
AnalysisPlugins found on that node attributing each analysis component to a specific plugin/module (†)It can be useful (and efficient) to give user an option to include or exclude individual parts from the response. Typically this can be achieved by introducing new request parameters.
(†) There are some analysis components that do not belong to any specific plugin, these represent the minimal OOTB set of components that are always available – for example when you are developing a plugin and run OpenSearch with that plugin installed using command line
./gradlew runthen no additional modules or plugins are available on that node.