Update Satellite to ElasticSearch 8.1.0 #3187
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
- update ElasticSearch-mock to 2.0.0 - update jest.config.js - fixup ES tests
RC-Lee
force-pushed
the
update-Satelite-ES-8.1.0
branch
from
0c761b6
to
2b352ee
Compare
|
Hello! Please rebase, as the following commit 6046273 has reorganized our file structure! |
|
closing until after autocomplete has been fully implemented. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Other changes in the Satellite folder
Issue This PR Addresses
This PR is part of #2913
The idea is to update ElasticSearch and ElasticSearch-mock first in Satellite, release Satellite, and then use the updated version of Satellite.
In the PR Satellite is updated and the Satellite tests will pass.
However, Search tests are breaking. Do note I only updated ES and ES-mock inside Satellite, and have not touched the Search service or any other Telescope code outside of Satellite.
This is a result of having Satellite within our monorepo and
pnpmcreating conflicts between Satellite and Telescope.Details of the bug are in #3191