Skip to content
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

Excute query call by user action #1057

Closed
lukass77 opened this issue Apr 2, 2023 · 1 comment
Closed

Excute query call by user action #1057

lukass77 opened this issue Apr 2, 2023 · 1 comment

Comments

@lukass77
Copy link

lukass77 commented Apr 2, 2023

Today working on Turnilo , end user set the query criteria on filter / split / musures , after end user done with query critiria ..
the query submited automaticly to druid broker .

is there is some way that user set his query criteria and only after pressing a button on UI / explicitly submit the query to broker , point is to provide the end user the controll to deciede when to submit the query .. instead executing it automaticly ..??

think of a flow where user want to add 5 musures , and 2 filter .
today for each filter added a query is submitted to druid broker .. and for each filter query submitted to druid broker ..
so we end with 7 calls to the broker .. but what user want is a single call to the broker which is the last combination of 5 measures and 2 filters

can query execution can be controll by user action and not execute automaticly ?
if this is missing suggest to add this option , to configure turnilo .. with
env variable query_execution_mode , which can get two value - automaticly (default) as today , or user_action - user need to click a button on UI to execute the query after done setting query criteria .

@adrianmroz-allegro
Copy link
Contributor

Duplicate of #1052

@adrianmroz-allegro adrianmroz-allegro marked this as a duplicate of #1052 Apr 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants