-
Notifications
You must be signed in to change notification settings - Fork 80
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
WIP: Add compatibility to Elasticsearch 8 #608
Closed
alexander-schranz
wants to merge
2
commits into
sulu:2.5
from
alexander-schranz:feature/elasticsearch-7-8-layer
Closed
WIP: Add compatibility to Elasticsearch 8 #608
alexander-schranz
wants to merge
2
commits into
sulu:2.5
from
alexander-schranz:feature/elasticsearch-7-8-layer
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
alexander-schranz
force-pushed
the
feature/elasticsearch-7-8-layer
branch
3 times, most recently
from
April 21, 2022 02:21
c1d9b48
to
1936db7
Compare
alexander-schranz
force-pushed
the
feature/elasticsearch-7-8-layer
branch
from
August 8, 2022 11:23
178c189
to
3f290dc
Compare
alexander-schranz
force-pushed
the
feature/elasticsearch-7-8-layer
branch
from
August 8, 2022 11:25
3f290dc
to
33ca96f
Compare
alexander-schranz
force-pushed
the
feature/elasticsearch-7-8-layer
branch
from
August 16, 2022 18:23
33ca96f
to
2a5298c
Compare
alexander-schranz
changed the title
Try rest api compatibility layer
Add compatibility to Elasticsearch 8
Aug 16, 2022
alexander-schranz
force-pushed
the
feature/elasticsearch-7-8-layer
branch
5 times, most recently
from
August 16, 2022 20:15
2e562b4
to
50ff505
Compare
alexander-schranz
changed the title
Add compatibility to Elasticsearch 8
WIP: Add compatibility to Elasticsearch 8
Aug 16, 2022
We need first add support for MassiveSearch before adding here support. Else it doesn't make a lot of sense if MassiveSearch is not suporting it. |
alexander-schranz
force-pushed
the
feature/elasticsearch-7-8-layer
branch
from
August 16, 2022 20:40
50ff505
to
80ff896
Compare
alexander-schranz
force-pushed
the
feature/elasticsearch-7-8-layer
branch
4 times, most recently
from
April 18, 2023 09:23
ce6baa6
to
fdccc26
Compare
alexander-schranz
force-pushed
the
feature/elasticsearch-7-8-layer
branch
from
November 13, 2023 15:17
fdccc26
to
553b0a9
Compare
alexander-schranz
force-pushed
the
feature/elasticsearch-7-8-layer
branch
from
November 14, 2023 09:12
553b0a9
to
0dd1723
Compare
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.
Try handcraftedinthealps/ElasticsearchBundle#28
TODO: