Skip to content

CMR-11357: update elasticsearch - #2473

Open
zimzoom wants to merge 1 commit into
masterfrom
CMR-11357
Open

CMR-11357: update elasticsearch#2473
zimzoom wants to merge 1 commit into
masterfrom
CMR-11357

Conversation

@zimzoom

@zimzoom zimzoom commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 57.92%. Comparing base (1db234b) to head (c842a89).

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2473      +/-   ##
==========================================
- Coverage   57.93%   57.92%   -0.01%     
==========================================
  Files        1073     1073              
  Lines       74658    74658              
  Branches     2174     2171       -3     
==========================================
- Hits        43251    43248       -3     
- Misses      29379    29380       +1     
- Partials     2028     2030       +2     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Comment thread dev-system/compose.yaml
context: .
dockerfile: resources/elasticsearch/Dockerfile.elasticsearch
image: cmr-elasticsearch:8.19.14
image: cmr-elasticsearch:8.19.17

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

our current elasticsearch cluster is 8.19.14, do we need to update our cluster as well?

"es-deps")

(def elastic-version "8.19.14")
(def elastic-version "8.19.17")

@jmaeng72 jmaeng72 Jul 31, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

any changes to es-spatial-plugin requires we create new AMI with these changes and update our elastic cluster to this new AMI across all ENVS. We need to make sure we do this.

We also need to test that our cluster will still work properly with this new es-spatial-plugin change. So pls test in WL before merging this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants