-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New ElasticSearch Query Runner #5794
Conversation
The new elasticsearch query runner is split into three: - A runner supporting the newest versions of ES, aggregation, nested aggregations and nested fields. - A runner for the SQL OpenDistro flavor - A runner for the SQL X-Pack flavor Fixes #4293
@wwl717195673 Can you please give this a look to make sure my one change looks good? The only change was to remove the dedicated |
That's good.Both run_query methods are totally same.You can remove it. |
Thanks! I'm just fixing the logos rendering next and this will be good as gold 👌 |
Alright, I have fixed the logos and deprecated |
I have reviewed the code.That's awesome!!! |
Thank you everyone for your diligent efforts on this pull request. The new ES query runner has now merged to |
How do I get the new query runner? I pulled latest and didnt see the UI changes |
Which "latest" did you pull? |
The 10.1.0 docker image
…On Thu, Jul 21, 2022, 5:27 PM Jesse ***@***.***> wrote:
Which "latest" did you pull?
—
Reply to this email directly, view it on GitHub
<#5794 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUAW7TCVUWP4IIORAGQVPPTVVG6EJANCNFSM53M5KGGA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
10.1 was released last year so it won't include changes merged since then 😉 If you want the latest preview build that includes this query runner you can use the preview image or you can wait for the V11 release later this summer. Another way to solve would be to |
Ah yes, should've opened my eyes on that one :-)
Many thanks! Gonna check out the preview release
…On Thu, Jul 21, 2022 at 6:45 PM Jesse ***@***.***> wrote:
10.1 was released last year so it won't include changes merged since then
😉
If you want the latest preview build that includes this query runner you
can use the preview image <https://hub.docker.com/r/redash/redash/tags>
or you can wait for the V11 release later this summer.
Another way to solve would be to curl the latest query_runner onto your
docker host, write your own dockerfile that copies this query runner over
the old one (I don't recommend this).
—
Reply to this email directly, view it on GitHub
<#5794 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUAW7TCWUYUB5G5NSGA4KVDVVHHJBANCNFSM53M5KGGA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
- A runner supporting the newest versions of ES, aggregation, nested aggregations and nested fields. - A runner for the SQL OpenDistro flavor - A runner for the SQL X-Pack flavor Co-authored-by: Nicolas Le Manchet <nicolas@lemanchet.fr> Co-authored-by: wwl717195673 <717195673@qq.com>
- A runner supporting the newest versions of ES, aggregation, nested aggregations and nested fields. - A runner for the SQL OpenDistro flavor - A runner for the SQL X-Pack flavor Co-authored-by: Nicolas Le Manchet <nicolas@lemanchet.fr> Co-authored-by: wwl717195673 <717195673@qq.com>
- A runner supporting the newest versions of ES, aggregation, nested aggregations and nested fields. - A runner for the SQL OpenDistro flavor - A runner for the SQL X-Pack flavor Co-authored-by: Nicolas Le Manchet <nicolas@lemanchet.fr> Co-authored-by: wwl717195673 <717195673@qq.com>
What type of PR is this?
Description
This PR incorporates the excellent work from #4391 with adjustments in #5701. I rebased from
master
and applied both patches to retain everyone's commit attributions.These changes have been reviewed twice and approved but were never merged. Here's hoping the third time's the charm.
In addition to those commits, I have deprecated the original
elasticsearch
query runner. Existing connections will continue to exist.How is this tested?
Unending thanks to @NicolasLM and @wwl717195673 for their unit and manual testing.
I also manually tested the deprecation:
elasticsearch
data sourcedeprecated=True
commit and reload UI3.elasticsearch2
databasedata_sources
tableRelated Tickets & Documents
Mobile & Desktop Screenshots/Recordings (if there are UI changes)
Data source selection screen: