Skip to content
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

Merged

Conversation

noCharger
Copy link
Collaborator

@noCharger noCharger commented Feb 17, 2025

Description

Related Issues

Check List

  • Commits are signed per the DCO using --signoff.
  • Public documentation issue/PR created.

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.

Signed-off-by: Louis Chu <clingzhi@amazon.com>
Signed-off-by: Louis Chu <clingzhi@amazon.com>
@noCharger noCharger changed the title Remove opendistro settings Remove opendistro settings and endpoints Feb 18, 2025
@penghuo penghuo added the v3.0.0 label Feb 18, 2025
penghuo
penghuo previously approved these changes Feb 18, 2025
Copy link
Collaborator

@penghuo penghuo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thx!

@noCharger
Copy link
Collaborator Author

SQLBackwardsCompatibilityIT > testBackwardsCompatibility FAILED
    org.junit.ComparisonFailure: expected:<...t":{},"persistent":{["plugins.sql.cursor.keep_alive":"7m"]}}> but was:<...t":{},"persistent":{[]}}>
        at __randomizedtesting.SeedInfo.seed([33BCEBCEDDBE50B3:D883D600A7658539]:0)
        at org.junit.Assert.assertEquals(Assert.java:117)
        at org.junit.Assert.assertEquals(Assert.java:146)
        at org.opensearch.sql.bwc.SQLBackwardsCompatibilityIT.verifySQLSettings(SQLBackwardsCompatibilityIT.java:134)
        at org.opensearch.sql.bwc.SQLBackwardsCompatibilityIT.testBackwardsCompatibility(SQLBackwardsCompatibilityIT.java:97)
  1> [2025-02-18T02:29:53,909][INFO ][o.o.s.b.SQLBackwardsCompatibilityIT] [testBackwardsCompatibility] before test
  1> [2025-02-18T02:29:54,088][INFO ][o.o.s.b.SQLBackwardsCompatibilityIT] [testBackwardsCompatibility] initializing REST clients against [http://[::1]:42701, http://127.0.0.1:39011, http://[::1]:[423](https://github.com/opensearch-project/sql/actions/runs/13380702669/job/37368667914?pr=3326#step:6:424)69, http://127.0.0.1:37635, http://[::1]:33825, http://127.0.0.1:33885]
  1> [2025-02-18T02:29:54,652][INFO ][o.o.s.b.SQLBackwardsCompatibilityIT] [testBackwardsCompatibility] after test

Tests with failures:
 - org.opensearch.sql.bwc.SQLBackwardsCompatibilityIT.testBackwardsCompatibility

will do a sanity test before merging

Signed-off-by: Louis Chu <clingzhi@amazon.com>
@noCharger noCharger force-pushed the remove-opendistro-settings branch from 7bc5696 to a4c4e8a Compare February 19, 2025 21:21
@noCharger noCharger self-assigned this Feb 19, 2025
@@ -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.

Copy link
Member

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?

Copy link
Collaborator Author

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.");
Copy link
Member

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

Copy link
Collaborator Author

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.

@noCharger noCharger merged commit c8e4e9a into opensearch-project:main Feb 20, 2025
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants