-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Magento 2.3 Beta version : Elastic search V 6.0 issue #18974
Comments
Hi @tejasvyas1988. Thank you for your report.
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
where @tejasvyas1988 do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?
|
Note that in 2.2 (also tested in 2.3), it seems that connections to Elasticsearch silently fail when you click the 'Test Connection' button in the Store Configuration - Catalog Search admin section, and there's no indication that only 2.x and 5.x are officially supported either in any error messages (none are logged) or in the UI. Just noting here that Elasticsearch 2.x was EOL almost a year ago (Feb 2018) and Elasticsearch 5.x will be EOL in March 2019 (when 7.0.0 is released); see: https://www.elastic.co/support/eol It would be nice if Magento's ES support could be a little more lively, as I still feel the sting of running the unsupported Apache Solr 3.6.2 version for many many years for Magento 1.x sites :/ |
ElasticSearch docs regarding changes to the |
I was checking in this file vendor\magento\module-elasticsearch\Elasticsearch5\Model\Client\Elasticsearch.php and find the below code in addFieldsMapping function: |
any updates on the previous question? @magento-engcom-team |
Guys, Magento 2.3 is currently supporting Elasticsearch 5.2.x and Elasticsearch 2.x so it isn't an issue. |
@slavvka - So... is there any plan to support a version of Elasticsearch which will not be deprecated/unsupported within the next 4 months? |
@slavvka So Magento 2.3 will be released with support to deprecated tools? |
Agreed it would be nice to keep up a bit better with ElasticSearch release cadence. This is something we are looking to improve. Remember that as of this spring, we had support for only Elastic 2.x (not that this is a good thing). As an FYI, support for 5.x was contributed by the community, so that is also an option. At the end of the day, this is currently a feature request and not a bug. |
Moving conversation here, which is a feature request: #21277 (since this was closed). Also, is MySQL search being deprecated? If so, it might be good to get Magento working with a more modern version of Elasticsearch... |
Preconditions (*)
1.Magento 2.3 beta version
2.Elastic Search 6.4
Steps to reproduce (*)
1.Install the Elastic Version 6.4
2.Select the option Elastic Search 5+ from admin Configuration
3. Perform Magento reindexing
Expected result (*)
Enabling [_all] is disabled in 6.0. As a replacement, you can use [copy_to] on mapping fields to create your own catch-all field.
Actual result (*)
The text was updated successfully, but these errors were encountered: