Fixes #7272: Error in rehash DB migration with Elasticsearch queries

[wm3]

What type of PR is this?

• Bug Fix

Description

When migrating from Redash 10.1.0 to 25.1.0, the initialization of the Elasticsearch query runner is triggered, causing an error to be thrown. In addition to the measures implemented in #7258, the current fix ensures that the migration proceeds successfully.

How is this tested?

• Manually

The same issue as #7272 occurred in the current environment. After applying this fix, running docker-compose run --rm server manage db upgrade completed the migration successfully, and it was confirmed that Elasticsearch queries can now be executed.

Related Tickets & Documents

• Rehash DB Migration throw an error when processing elasticsearch queries #7272 (comment)
• Handle the case when query runner configuration is an empty dict #7258

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 64.01%. Comparing base (10ce280) to head (e20fac0).
Report is 1 commits behind head on master.

Files with missing lines	Patch %	Lines
redash/query_runner/elasticsearch.py	0.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #7292   +/-   ##
=======================================
  Coverage   64.01%   64.01%           
=======================================
  Files         163      163           
  Lines       13410    13410           
  Branches     1905     1905           
=======================================
  Hits         8585     8585           
  Misses       4490     4490           
  Partials      335      335           

Files with missing lines	Coverage Δ
redash/query_runner/elasticsearch.py	15.46% <0.00%> (ø)

[wm3]

@eradman
It seems that an error is occurring in the coverage. Is it necessary to add additional tests?