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

chore(elasticsearch-plugin): Update ElasticSearch supported version from v7.9.1 to v8.13.1 #3121

Open
wants to merge 115 commits into
base: major
Choose a base branch
from

Conversation

LeftoversTodayAppAdmin
Copy link

Description

ElasticSearch version greater than 7.9.1 cannot be currently used because thats what the plugin is looking for and it matches the warning in the documentation.
https://github.com/vendure-ecommerce/vendure/blob/master/packages/elasticsearch-plugin/package.json
https://docs.vendure.io/reference/core-plugins/elasticsearch-plugin/

But the issue linked in the documentation was closed a long time ago: elastic/elasticsearch-js#1519

This chore updates the documentation, plugin ES client dependency and E2E testing docker container to all use the newer matching version of ElasticSearch 8.13.1 and corresponding node package.

Breaking changes

BREAKING CHANGE: users must keep the minimum version in sync across:

  • "@elastic/elasticsearch": "^8.13.1" in package.json of their Vendure instance
  • "@elastic/elasticsearch": "^8.13.1", in package.json of their elasticsearch-plugin
  • ElasticSearch itself must be at 8.13.1

Since the package.json file for the plugin is being updated to use ~8.13.1, it will not be backwards compatible with older v7 ElasticSearch deployments.

Source
Language clients are forward compatible; meaning that clients support communicating with greater or equal minor versions of Elasticsearch. Elasticsearch language clients are only backwards compatible with default distributions and without guarantees made.

Please refer to ElasticSearch documentation for upgrading your deployment without any breaks or data loss.

Screenshots

You can add screenshots here if applicable.

Checklist

📌 Always:

  • [✅] I have set a clear title
  • [✅ ] My PR is small and contains a single feature
  • [✅ ] I have checked my own PR

👍 Most of the time:

  • [✅] I have added or updated test cases - Updated the docker compose file used in E2E testing to ensure ES version matches the @elastic/elasticsearch node package version
  • [✅ ] I have updated the documentation for ElasticSearch Plugin

michaelbromley and others added 30 commits July 17, 2024 15:32
…ommerce#2961)

Remove a workaround that led to refetching relations in customFields.
Prevent refetching of customFields during hydration
michaelbromley and others added 28 commits September 18, 2024 16:01
This is now set to the default setting in GitHub, which means
the config file is not needed and maintenance will be
easier.
Fixes vendure-ecommerce#2097. This commit alters the way we store the RequestContext object
on the `req` object so that we can better target individual handlers, preventing
parallel execution of queries from interfering with one another.
The fix f235249 inadvertently broke transactions across field
resolvers in all databases apart from SQLite. This commit solves that.
This commit introduces some new low-level APIs to the data layer
of the Admin UI. It allows us to control which custom fields
get dynamically added to fragments when making queries & mutations.

It also exposes a new method on the QueryResult class which allows
us to update & refetch the underlying DocumentNode whenever
the selected custom fields changes.

Relates to vendure-ecommerce#3097
Copy link

vercel bot commented Oct 9, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
docs ✅ Ready (Inspect) Visit Preview Oct 9, 2024 0:56am

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.