Elasticsearch Regular Search Returns No Results – Magento2 Configuration Guide

catalogsearchconfigurationelasticsearchmagento2server-setup

I've recently upgraded my Magento to 2.4 which necessitates the use of Elasticsearch.

Using the search function always shows the message "Your search returned no results". However using "Advanded Search" returns results as normal.

I've tested the connection as per this screenshot and there seems to be no issues.

I've checked another question regarding this (309450) but the solution there (turning off modules) doesn't seem to have fixed the issue.

I've also run the command below in SSL

curl http://localhost:9200/_cluster/health?pretty

This got the following result.

{
  "cluster_name" : "my-application",
  "status" : "yellow",
  "timed_out" : false,
  "number_of_nodes" : 1,
  "number_of_data_nodes" : 1,
  "active_primary_shards" : 4,
  "active_shards" : 4,
  "relocating_shards" : 0,
  "initializing_shards" : 0,
  "unassigned_shards" : 4,
  "delayed_unassigned_shards" : 0,
  "number_of_pending_tasks" : 0,
  "number_of_in_flight_fetch" : 0,
  "task_max_waiting_in_queue_millis" : 0,
  "active_shards_percent_as_number" : 50.0
}

I have also looked in the exception log and found the following error which seems to relate to elasticsearch:

[2021-11-26 11:05:07] main.CRITICAL: {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Text fields are not optimised for operations that require per-document field data like aggregations and sorting, so these operations are disabled by default. Please use a keyword field instead. Alternatively, set fielddata=true on [links_title] in order to load field data by uninverting the inverted index. Note that this can use significant memory."}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"query","grouped":true,"failed_shards":[{"shard":0,"index":"magento2_product_1_v31","node":"r9_ZsNBiTqiP7FJDre9MmA","reason":{"type":"illegal_argument_exception","reason":"Text fields are not optimised for operations that require per-document field data like aggregations and sorting, so these operations are disabled by default. Please use a keyword field instead. Alternatively, set fielddata=true on [links_title] in order to load field data by uninverting the inverted index. Note that this can use significant memory."}}],"caused_by":{"type":"illegal_argument_exception","reason":"Text fields are not optimised for operations that require per-document field data like aggregations and sorting, so these operations are disabled by default. Please use a keyword field instead. Alternatively, set fielddata=true on [links_title] in order to load field data by uninverting the inverted index. Note that this can use significant memory.","caused_by":{"type":"illegal_argument_exception","reason":"Text fields are not optimised for operations that require per-document field data like aggregations and sorting, so these operations are disabled by default. Please use a keyword field instead. Alternatively, set fielddata=true on [links_title] in order to load field data by uninverting the inverted index. Note that this can use significant memory."}}},"status":400} {"exception":"[object] (Elasticsearch\\Common\\Exceptions\\BadRequest400Exception(code: 400): {\"error\":{\"root_cause\":[{\"type\":\"illegal_argument_exception\",\"reason\":\"Text fields are not optimised for operations that require per-document field data like aggregations and sorting, so these operations are disabled by default. Please use a keyword field instead. Alternatively, set fielddata=true on [links_title] in order to load field data by uninverting the inverted index. Note that this can use significant memory.\"}],\"type\":\"search_phase_execution_exception\",\"reason\":\"all shards failed\",\"phase\":\"query\",\"grouped\":true,\"failed_shards\":[{\"shard\":0,\"index\":\"magento2_product_1_v31\",\"node\":\"r9_ZsNBiTqiP7FJDre9MmA\",\"reason\":{\"type\":\"illegal_argument_exception\",\"reason\":\"Text fields are not optimised for operations that require per-document field data like aggregations and sorting, so these operations are disabled by default. Please use a keyword field instead. Alternatively, set fielddata=true on [links_title] in order to load field data by uninverting the inverted index. Note that this can use significant memory.\"}}],\"caused_by\":{\"type\":\"illegal_argument_exception\",\"reason\":\"Text fields are not optimised for operations that require per-document field data like aggregations and sorting, so these operations are disabled by default. Please use a keyword field instead. Alternatively, set fielddata=true on [links_title] in order to load field data by uninverting the inverted index. Note that this can use significant memory.\",\"caused_by\":{\"type\":\"illegal_argument_exception\",\"reason\":\"Text fields are not optimised for operations that require per-document field data like aggregations and sorting, so these operations are disabled by default. Please use a keyword field instead. Alternatively, set fielddata=true on [links_title] in order to load field data by uninverting the inverted index. Note that this can use significant memory.\"}}},\"status\":400} at /var/www/vhosts/sitename.co.uk/httpdocs/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php:632)"} []
[2021-11-26 11:05:12] main.CRITICAL: {"error":{"root_cause":[{"type":"query_shard_exception","reason":"failed to create query: field:[sku] was indexed without position data; cannot run PhraseQuery","index_uuid":"qI8SDvZQSFGVhINcjyR_cw","index":"magento2_product_1_v31"}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"query","grouped":true,"failed_shards":[{"shard":0,"index":"magento2_product_1_v31","node":"r9_ZsNBiTqiP7FJDre9MmA","reason":{"type":"query_shard_exception","reason":"failed to create query: field:[sku] was indexed without position data; cannot run PhraseQuery","index_uuid":"qI8SDvZQSFGVhINcjyR_cw","index":"magento2_product_1_v31","caused_by":{"type":"illegal_state_exception","reason":"field:[sku] was indexed without position data; cannot run PhraseQuery"}}}]},"status":400} {"exception":"[object] (Elasticsearch\\Common\\Exceptions\\BadRequest400Exception(code: 400): {\"error\":{\"root_cause\":[{\"type\":\"query_shard_exception\",\"reason\":\"failed to create query: field:[sku] was indexed without position data; cannot run PhraseQuery\",\"index_uuid\":\"qI8SDvZQSFGVhINcjyR_cw\",\"index\":\"magento2_product_1_v31\"}],\"type\":\"search_phase_execution_exception\",\"reason\":\"all shards failed\",\"phase\":\"query\",\"grouped\":true,\"failed_shards\":[{\"shard\":0,\"index\":\"magento2_product_1_v31\",\"node\":\"r9_ZsNBiTqiP7FJDre9MmA\",\"reason\":{\"type\":\"query_shard_exception\",\"reason\":\"failed to create query: field:[sku] was indexed without position data; cannot run PhraseQuery\",\"index_uuid\":\"qI8SDvZQSFGVhINcjyR_cw\",\"index\":\"magento2_product_1_v31\",\"caused_by\":{\"type\":\"illegal_state_exception\",\"reason\":\"field:[sku] was indexed without position data; cannot run PhraseQuery\"}}}]},\"status\":400} at /var/www/vhosts/sitename.co.uk/httpdocs/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php:632)"} []

I'd appreciate any advice on this topic.

UPDATE: ISSUE RESOLUTION

Thanks to Edgarth for his assistance, there were a few extra steps I had to perform but he pointed me in the right direction.

Essentially I had to disable the "Search" and "filter" options for some of the product attributes (I presume that SKU was the troublesome one given the error) and run the following commands in SQL:

UPDATE catalog_eav_attribute 
SET is_filterable_in_search = 0 
WHERE attribute_id IN (SELECT attribute_id FROM eav_attribute WHERE entity_type_id = 4 AND backend_type = 'varchar')

UPDATE catalog_eav_attribute AS cea
INNER JOIN eav_attribute AS ea
ON ea.attribute_id = cea.attribute_id
SET cea.is_filterable = 0, cea.is_filterable_in_search = 0
WHERE (cea.is_filterable = 1 OR cea.is_filterable_in_search = 1)
AND frontend_input NOT IN ('boolean', 'multiselect', 'select', 'price');

After doing this and reindexing, the search function seems to be working properly now.

Best Answer

Check in your env.php file if you have

  'catalog' => [
            'search' => [
                'enable_eav_indexer' => '1',
                'engine' => 'elasticsearch7',
                'elasticsearch7_server_hostname' => 'elasticsearch'
            ]
        ],

Related Solutions

Magento – Issue with Elastic search 6.x in Magento 2.3.3

Got across this several times and we came across this https://support.magento.com/hc/en-us/articles/360027356612-Elasticsearch-5-is-configured-but-search-page-does-not-load-with-Fielddata-is-disabled-error which not only identifies the problem but also gives a fix which works with several Magento versions. I tried 2.3.5 and 2.4.2.

By default, only certain types of product attributes can be used in Layered Navigation. They are Yes/No, Dropdown, Multipleselect, and Price. That is why in Magento Admin, you cannot set an attribute of any other type as Use in Layered Navigation = Filterable or Use in Search Results Layered Navigation = Yes. But there is a technical possibility to get around this limitation by directly changing the is_filterable and is_filterable_in_search values in the database. If this happens, and any other attribute type, like Date, Text, etc., is set to be used in Layered Navigation, Elasticsearch 5 (my edit: and others like ElasticSearch 6 and 7) throws an exception.

Fielddata is disabled on text fields by default. Set fielddata=true on [%attribute_code%]] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory.

Step 1. Identify the product attributes which generate the issue using an SQL tool like phpmyadmin

SELECT ea.attribute_code, ea.frontend_input, cea.is_filterable, cea.is_filterable_in_search FROM eav_attribute AS ea
    INNER JOIN catalog_eav_attribute AS cea ON ea.attribute_id = cea.`attribute_id`
    WHERE (is_filterable = 1 OR is_filterable_in_search = 1) AND frontend_input NOT IN ('boolean', 'multiselect', 'select', 'price');

To fix the issue, you need to set is_filterable (that is, used in Layered Navigation) and filterable_in_search (that is, used in search results Layered Navigation) to "0" (not used).

UPDATE catalog_eav_attribute AS cea
    INNER JOIN eav_attribute AS ea
        ON ea.attribute_id = cea.attribute_id
SET cea.is_filterable = 0, cea.is_filterable_in_search = 0
WHERE (cea.is_filterable = 1 OR cea.is_filterable_in_search = 1) 
    AND frontend_input NOT IN ('boolean', 'multiselect', 'select', 'price');

then reindex all

bin/magento indexer:reindex

The fix says to reindex only catalogsearch_fulltext but this won't work if you have custom search modules since they use different indexes.

Magento 2.4.1 – Sort by Newest Not Working

I don't know this is the correct way to do this or not. I was waiting for someone to give a better answer but not getting one. So I am using this for now.

# Get the attribute_id of 'created_at'
select attribute_id from eav_attribute where attribute_code = 'created_at' and entity_type_id=4;

# Set frontend_label
update eav_attribute set frontend_label = 'Created At' where attribute_id=112;

# Set used_for_sort_by
update catalog_eav_attribute set used_for_sort_by = 1 where attribute_id=112;

Best Answer

Related Solutions

Magento – Issue with Elastic search 6.x in Magento 2.3.3

Magento 2.4.1 – Sort by Newest Not Working

Related Topic