pjfanning opened a new pull request, #1933: URL: https://github.com/apache/pekko-connectors/pull/1933
### Motivation The Opensearch integration tests only ran against Opensearch 1.3.20. The 1.x line is end-of-life (1.3.20 was its final release, May 2025), so the connector had no coverage against any currently supported Opensearch. ### Modification - Replaced the `opensearch1` compose service with `opensearch2` (2.19.6, port 9203) and `opensearch3` (3.8.0, port 9204). Both disable the demo security config (`DISABLE_INSTALL_DEMO_CONFIG` / `DISABLE_SECURITY_PLUGIN`, required from 2.12 onwards) and pin a 512m heap so the extra node does not grow the CI footprint. - Updated the `elasticsearch` CI `pre_cmd` to start both. - Turned `OpensearchV1Spec` into an abstract `OpensearchSpec` taking the base URL, with `Opensearch2Spec` and `Opensearch3Spec` running the whole spec against each server. - Added port 9204 to `OpensearchParameterizedTest`. No main-source changes, so no binary compatibility impact. ### Result The Opensearch connector is exercised against both supported Opensearch major lines instead of an end-of-life one. `OpensearchApiVersion.V1` remains the only API version — 2.x and 3.x keep the Elasticsearch 7.x compatible bulk and search API that it targets. ### Tests - `sbt "elasticsearch/Test/compile"` — success - `sbt "elasticsearch/scalafmtAll" "elasticsearch/javafmtAll"` — success - Integration run not done locally: the containers start, but this machine cannot run the suite. Relying on the `elasticsearch` CI job to exercise both new servers. ### References None — keeping test dependencies on supported versions -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
