-
Notifications
You must be signed in to change notification settings - Fork 146
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
Remove opendistro settings and endpoints #3326
Remove opendistro settings and endpoints #3326
Conversation
Signed-off-by: Louis Chu <clingzhi@amazon.com>
Signed-off-by: Louis Chu <clingzhi@amazon.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thx!
will do a sanity test before merging |
Signed-off-by: Louis Chu <clingzhi@amazon.com>
7bc5696
to
a4c4e8a
Compare
@@ -16,36 +16,6 @@ Introduction | |||
|
|||
When OpenSearch bootstraps, SQL plugin will register a few settings in OpenSearch cluster settings. Most of the settings are able to change dynamically so you can control the behavior of SQL plugin without need to bounce your cluster. You can update the settings by sending requests to either ``_cluster/settings`` or ``_plugins/_query/settings`` endpoint, though the examples are sending to the latter. | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need to list the removed settings in breaking change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need to list the removed settings in breaking change?
As long as we include this change in the release notes, I think it is less confusing to remove them from the documents.
@@ -93,21 +93,33 @@ public void testBackwardsCompatibility() throws Exception { | |||
List<Map<String, Object>> plugins = (List<Map<String, Object>>) response.get("plugins"); | |||
Set<Object> pluginNames = | |||
plugins.stream().map(map -> map.get("name")).collect(Collectors.toSet()); | |||
String version = (String) response.get("version"); | |||
|
|||
boolean isBackwardsIncompatibleVersion = version.startsWith("2."); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would we test 2.x using main code? I thought we would remove 2.x from build.gradle so this won't happen, since they are not backward compatible
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would we test 2.x using main code? I thought we would remove 2.x from build.gradle so this won't happen, since they are not backward compatible
I think the majority of the features are still backward compatible, besides those planned to deparcate in 3.0. Maybe discuss the bwc version of main branch on thread #1880.
Description
Related Issues
Check List
--signoff
.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.