-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SDK] Add support for createComponent extension points #2981
Comments
The workflow to create interface for any extension point is:
Steps to achieve the above workflow:
|
Design for createComponent with SQL plugin. SQL plugin requires ClusterState and ClusterSettings for createComponent extension point. |
As mentioned in the above comment, because of the new design we can try using sendRequest from RemoteConnectionManager to send a TransportRequest from SDK to OpenSearch to add the node in the RemoteConnectionManager map and check if the error mentioned here is resolved. |
Changing the node here to localNode of OpenSearch resolved the error. Moved the sendRequest in handlePluginRequest for a better approach.
|
Resolved the above issue. It was mainly because of using Enum in the CreateComponentRequest. Currently looking into opensearch-project/opensearch-sdk-java#6 |
Resolved opensearch-project/opensearch-sdk-java#6. The issue was because of creating a new transport object for the new CreateComponentRequest which resulted in a new ConnectionManagerMap. |
Is your feature request related to a problem? Please describe.
For every extension points, SDK should have a TransportRequest to communicate with OpenSearch. This issue focuses on the below extension point:
This covers
This extensions will also cover a part of communication of sql plugin with OpenSearch and make the plugin extensible.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: