The name of plugin is not reported consistently #56
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I realized that plugin names are note represented correctly according to plugin configuration in testing framework.
Please see the code in this PR for more details.
This PR is not meant to be merged, it is to demonstrate the issue.
More specifically, in tests based on
OpenSearchIntegTestCase
(ie, number of nodes and their configuration is variable) I can not expect that following code to work correctly:It turns out that on some nodes the plugin returns its classname as a value of the
getName()
;Maybe it is a consequence of how individual nodes and plugins are deployed into cluster in testing framework. However, it came as a surprise to me.
Issues Resolved
As of writing I am not aware of any opened issue. It may not be an issue if this is the design on testing framework (however, it is not documented).
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.