You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Redash allows scheduling queries even if they include parameters. But scheduling a parameterized query against the QRDS always fails. The issue must be the parameters. Because if I remove the parameters then the whole thing works.
Steps to Reproduce
1. Create a simple, filterable query
SELECT 'bar' "foo";
2. Use Query Results with a parameter
SELECT datetime('now') "stamp", "foo" from query_xxxx WHERE "foo" = {{ param }}
query_xxxx points to the query from step one. param can be a dropdown list, text, or query based dropdown list type. No matter how you do it, set the parameter equal to a string literal: bar. Observe that the query returns proper data
Stamp
Bar
2020-01-01 22:00
foo
I faked the date for this example.
3. Set a query refresh schedule
Here I'll use a one minute interval. What we would expect is that after one minute, the query should be executed by the scheduler and will return data like this:
Stamp
Bar
2020-01-01 22:05
foo
We'd also expect the Redash UI to indicate the query was reflected at 22:05 (or whatever the associated server time was at execution time). But it doesn't. It still shows 22:00. No matter how long you wait.
4. Remove the parameter from the QRDS query
SELECT datetime('now') "stamp", "foo" from query_xxxx WHERE "foo" = 'bar'
Perform the same test from step three. Observe that the query updates as expected.
Technical details:
Redash Version: v9 Alpha
Browser/OS: FF / Safari / Chrome
How did you install Redash: SaaS
The text was updated successfully, but these errors were encountered:
Issue Summary
Redash allows scheduling queries even if they include parameters. But scheduling a parameterized query against the QRDS always fails. The issue must be the parameters. Because if I remove the parameters then the whole thing works.
Steps to Reproduce
1. Create a simple, filterable query
2. Use Query Results with a parameter
query_xxxx
points to the query from step one.param
can be a dropdown list, text, or query based dropdown list type. No matter how you do it, set the parameter equal to a string literal:bar
. Observe that the query returns proper dataI faked the date for this example.
3. Set a query refresh schedule
Here I'll use a one minute interval. What we would expect is that after one minute, the query should be executed by the scheduler and will return data like this:
We'd also expect the Redash UI to indicate the query was reflected at 22:05 (or whatever the associated server time was at execution time). But it doesn't. It still shows 22:00. No matter how long you wait.
4. Remove the parameter from the QRDS query
Perform the same test from step three. Observe that the query updates as expected.
Technical details:
The text was updated successfully, but these errors were encountered: