-
Notifications
You must be signed in to change notification settings - Fork 9.4k
ElasticSearch8 seemingly not deprecated #39809
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
Comments
Hi @vandijkstef. Thank you for your report.
Join Magento Community Engineering Slack and ask your questions in #github channel. |
Hi @engcom-November. Thank you for working on this issue.
|
Hello @vandijkstef , Thank you for your report and collaboration. We attempt to reproduce the issue in our latest 2.4 develop and 2.4.8 both the instance and its reproducible and kindly refer to the screenshot for your reference. ![]() Steps to Reproduce
We followed the preconditions and steps as provided and encountered therefor. Therefore, we are marking this ticket as "Issue: Confirmed." Thank you! |
✅ Jira issue https://jira.corp.adobe.com/browse/AC-14440 is successfully created for this GitHub issue. |
✅ Confirmed by @engcom-November. Thank you for verifying the issue. |
Preconditions and environment
Magento 2.4.8 w/ OpenSearch. - PHP8.3
Steps to reproduce
Expected result
I would expect a deprecated module not being a requirement for a core module. Therefor I'd expect to be able to be disabled/uninstalled and have search properly working. Else I'd expect the setup/di steps to be aware of this dependency requirement and fail.
Actual result
Search is broken (page crash) since AdvancedSearch, while using OpenSearch is ALSO using/requiring ElasticSearch.
Here is the trace showing ElasticSearch dependency:
Additional information
Enabling just
Magento_Elasticsearch
makes it work again.Release note
No response
Triage and priority
The text was updated successfully, but these errors were encountered: