You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is due to the fact that many parts of the ElasticSuite module are retrieving informations from Elasticsearch (Product Collection is retrieving facets, count of products by attribute set, etc ....).
Also, there is no point using the module without setting the search engine to Smile Elasticsuite, since most of the module standard features just cannot work with MySQL engine, or with Solr or whatever.
You can consider this is by design. You have 2 choices here :
Use Elasticsuite with proper Elasticsuite search engine : Maybe we should set the configuration field as read-only when Elasticsuite is installed.
Do not use Elasticsuite at all
I close this issue for now, you can reopen it if needed.
When module is enabled and we change Catalog/Search/Engine back to MySQL, catalogsearch still call ElasticSuite and elasticsearch.
Preconditions
Magento Version : 2.1.7
ElasticSuite Version : 2.3.6
Environment : developer
Third party modules :
Steps to reproduce
Expected result
The text was updated successfully, but these errors were encountered: