Impossible to use 'Search' since last update

[fm4tt0s]

• Elasticsearch version: 2.3
• Operating system: RHEL/running ES under docker
• Browser + version: Chrome Version 97.0.4692.99 (Official Build) (x86_64)
• Elasticvue version: 0.37.0
• How are you running elasticvue? : browser extension

When attempt to use 'Search' functionality it gives below error:

{
    "error": {
        "failed_shards": [
            {
                "index": "index_name",
                "node": "_xFRrOs-SgGU5-QTR3F8ew",
                "reason": {
                    "col": 69,
                    "line": 1,
                    "reason": "failed to parse search source. unknown search element [track_total_hits]",
                    "type": "search_parse_exception"
                },
                "shard": 0
            }
        ],
        "grouped": true,
        "phase": "query",
        "reason": "all shards failed",
        "root_cause": [
            {
                "col": 69,
                "line": 1,
                "reason": "failed to parse search source. unknown search element [track_total_hits]",
                "type": "search_parse_exception"
            }
        ],
        "type": "search_phase_execution_exception"
    },
    "status": 400
}

[cars10]

What happens when you customize the search query and remove track_total_hits?

[rodrigosouzazup]

What happens when you customize the search query and remove track_total_hits?

I have the same problem.

When I remove this field the query is executed successfully.

[cars10]

Do you also use an outdated version of elasticsearch, or does this happen with a newer version?

[rodrigosouzazup]

We use AES with versions "7.10" and "5.6" and the problem occurs only in version "5.6"

[cars10]

#85 will probably be reverted.

[fm4tt0s]

@cars10 thanks for the attention on the matter. this is confirmed; removing track_total_hits from customized query payload make it work fine.

[cars10]

I have published 0.38.0 with some fixes for outdated versions of elasticvue. Please update your clusters! At least for security reasons.