[prakashreddy.imduri]

1 year, 9 months ago #31536

Getting this error repeatedly on production, not in branches.

Uncaught Elasticsearch\Common\Exceptions\BadRequest400Exception: {"error":{"root_cause":[{"type":"parsing_exception","reason":"No text specified for text query","line":1,"col":85}],"type":"x_content_parse_exception","reason":"[1:85] [bool] failed to parse field [must]","caused_by":{"type":"parsing_exception","reason":"No text specified for text query","line":1,"col":85}},"status":400} in /code/wp-content/plugins/wpsolr-pro/wpsolr/core/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php:693
Stack trace:
#0 /code/wp-content/plugins/wpsolr-pro/wpsolr/core/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php(333): Elasticsearch\Connections\Connection->process4xxError(Array, Array, Array)
#1 /code/wp-content/plugins/wpsolr-pro/wpsolr/core/vendor/react/promise/src/FulfilledPromise.php(28): Elasticsearch\Connections\Connection->Elasticsearch\Connections\{closure}(Array)
#2 /code/wp-content/plugins/wpsolr-pro/wpsolr/core/vendor/ezimuel/rin

Around 2k times errors got triggered. Can you tell me possibility of this error

[wpsolr]

1 year, 9 months ago #31537

It looks like your Elasticsearch query is not well-formed, perhaps the query keywords are missing.
If you added custom code to modify the query, activate the WPSOLR’s query log to check the problem.

[prakashreddy.imduri]

1 year, 9 months ago #31540

Log With query monitor or without it in this case ?

[wpsolr]

1 year, 9 months ago #31541

Indeed.