0
Fixed

Error: Failed to parse query when typing first "

Brian R 3 months ago updated by Vlad R 2 weeks ago 4

In content search, with Elasticsearch installed, we are trying to search for a phrase using double quotes.  When we type the first quotation mark ", we get ERROR: {"error":{"root_cause":[{"type":"query_shard_exception","reason":"Failed to parse query [\"]","index_uuid":"ywFHU8VlTaa_Ks7IRAhFtA","index":"files"}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"dfs","grouped":true,"failed_shards":[{"shard":0,"index":"files","node":"R47pK0fVSwqf0sKIS2MTpQ","reason":{"type":"query_shard_exception","reason":"Failed to parse query [\"]","index_uuid":"ywFHU8VlTaa_Ks7IRAhFtA","index":"files","caused_by":{"type":"parse_exception","reason":"Cannot parse '\"': Lexical error at line 1, column 2. Encountered: after : \"\"","caused_by":{"type":"token_mgr_error","reason":"Lexical error at line 1, column 2. Encountered: after : \"\""}}}}]},"status":400}

Screen shot attached:


Started

This problem will be fixed with the next software update. In the meantime, if you don't type the double-quote and wait, you have enough time to type a keyword, or just click "Ok" on the error prompt and continue writing a keyword.

Thank you for reporting the problem!

Unfortunately even using a single quote, starting to type and not waiting will still throw the error. Is there a way I can configure Elastic search to use the match_phrase query by default in Filerun? Because currently the error will persist until I finish the phrase and use double quotes. 

Thanks in advance