Hello,
we configured Magento 2.3.4 and Elasticsearch 6.7.1, but when we try to filter in the layered navigation for a dropdown attribute, we have the following error:
{"error":{"root_cause":[{"type":"parsing_exception","reason":"[terms] unknown token [START_ARRAY] after [finset]","line":1,"col":235}],"type":"parsing_exception","reason":"[terms] unknown token [START_ARRAY] after [finset]","line":1,"col":235},"status":400} {"exception":"[object] (Elasticsearch\\Common\\Exceptions\\BadRequest400Exception(code: 400): {\"error\":{\"root_cause\":[{\"type\":\"parsing_exception\",\"reason\":\"[terms] unknown token [START_ARRAY] after [finset]\",\"line\":1,\"col\":235}],\"type\":\"parsing_exception\",\"reason\":\"[terms] unknown token [START_ARRAY] after [finset]\",\"line\":1,\"col\":235},\"status\":400} at /opt/bitnami/apps/magento/htdocs/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php:636)"} []
Does anyone have experience on this?
Thanks.
Hello @benjcarriero
https://github.com/magento/magento2/commit/4844c67145e87ae77dc30b09907fa3dfbf181fd5
please check above commit and fix it.
if works then mark as solution.
Have you removed
$resolvedField = $this->fieldMapper->getFieldName( $match['field'], ['type' => FieldMapperInterface::TYPE_QUERY] );
Yes i did it.
Any update here? @benjcarriero - any chance you got this to work? Similar problem on our end.