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
Environment:
Magento 2.3.3 Commerce edition
ElasticSuite v 2.8.3
I'm configuring elastic suite on a new environment with test data.
Using Search query "Product 33" magento now returns products with names: "Configurable Product 33"," Simple product 33" and "Configurable Product Attribute Set 3 3".
Question: is it possible to configure elasticsuite extension that search using query like "Product 33" will return also products with names like Simple product 331, Simple product 332?...
Now to get for example the product with name "Simple product 331" in search I have to enter a query either "Product" (which will return also lot of other products) or "Product 331" (which will return exactly the product "Simple product 331")
The text was updated successfully, but these errors were encountered:
You can try changing the settings. For example ElasticSuite -> Search Relevance -> Relevance Configuration -> Fulltext Base Settings -> Minimum Should Match http://joxi.ru/ZrJ0V44iMk3Q82
But it'll impair search results (result for minimum_should_match = 99% - http://joxi.ru/v29nQDDHzjdQzA)
Environment:
Magento 2.3.3 Commerce edition
ElasticSuite v 2.8.3
I'm configuring elastic suite on a new environment with test data.
Using Search query "Product 33" magento now returns products with names: "Configurable Product 33"," Simple product 33" and "Configurable Product Attribute Set 3 3".
Question: is it possible to configure elasticsuite extension that search using query like "Product 33" will return also products with names like Simple product 331, Simple product 332?...
Now to get for example the product with name "Simple product 331" in search I have to enter a query either "Product" (which will return also lot of other products) or "Product 331" (which will return exactly the product "Simple product 331")
The text was updated successfully, but these errors were encountered: