[Feature/extensions] Modified Environment settings support #4731
[Feature/extensions] Modified Environment settings support #4731owaiskazi19 merged 7 commits intoopensearch-project:feature/extensionsfrom joshpalis:environment-settings
Conversation
… Refactored response to include the entire environment settings object from node.java Signed-off-by: Joshua Palis <jpalis@amazon.com>
Signed-off-by: Joshua Palis <jpalis@amazon.com>
Signed-off-by: Joshua Palis <jpalis@amazon.com>
Signed-off-by: Joshua Palis <jpalis@amazon.com>
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
Codecov Report
@@ Coverage Diff @@
## feature/extensions #4731 +/- ##
========================================================
+ Coverage 70.52% 70.73% +0.21%
+ Complexity 57898 57846 -52
========================================================
Files 4708 4706 -2
Lines 278528 277831 -697
Branches 40661 40389 -272
========================================================
+ Hits 196420 196515 +95
+ Misses 65740 65093 -647
+ Partials 16368 16223 -145
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
| } | ||
|
|
||
| public EnvironmentSettingsResponse(StreamInput in) throws IOException { | ||
| super(in); |
There was a problem hiding this comment.
Nit: I don't like seeing super(in) (which in the Response case is a no-op) without a corresponding out.writeTo(). Makes me think too much. :)
| assertTrue(responseSettings.containsAll(componentSettings)); | ||
| assertTrue(componentSettings.containsAll(responseSettings)); | ||
| EnvironmentSettingsResponse environmentSettingsResponse = new EnvironmentSettingsResponse(settings); | ||
| assertEquals(settings, environmentSettingsResponse.getEnvironmentSettings()); |
There was a problem hiding this comment.
We should add a test to compare if the setting present in the list matches the one we have added to the list
There was a problem hiding this comment.
With this modification to Environment settings support, we are no longer transporting a list of Setting<T> objects but rather an entire Settings object, so we are not adding anything to any list. As for the comparison test for this transported Settings object, this is handled on line 501.
…t Setting<T> objects will return either the registered setting value from the Settings object, or the default value of the Setting<T> object Signed-off-by: Joshua Palis <jpalis@amazon.com>
Signed-off-by: Joshua Palis <jpalis@amazon.com>
…st for better clarity Signed-off-by: Joshua Palis <jpalis@amazon.com>
|
Summary of EnvironmentSettings workflow modification for future reference : Previous Design : Extensions will send OpenSearch a list of
New Design : While performing create-component integration for Anomaly Detection, it was determined that the entire environment
|
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
owaiskazi19
left a comment
There was a problem hiding this comment.
Thanks for addressing the comments!
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
Description
Environment Settings support for extensibility will now pass the entire
Settingsobject from OpenSearch node environment to the SDK.Companion PR : opensearch-project/opensearch-sdk-java#179
Issues Resolved
opensearch-project/opensearch-sdk-java#78
Check List
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.