spyoungtech opened a new issue, #24487:
URL: https://github.com/apache/superset/issues/24487
SQLLab utilizes the `/api/v1/query/updated_since` endpoint to retrieve
updated queries in order to ultimately display results.
#### How to reproduce the bug
1. Start superset and superset workers with caching and a result backend
(redis) configured
2. Configure asynchronous results for your database connection (database
connections -> edit -> advanced -> performance)
3. Open SQLLab
4. (with browser network inspector open) Select database and schema and run
a simple query
5. Observe this (may) succeed, populating the query result data in the UI
and:
- The call to `/api/v1/query/updated_since` returned a non-empty array
containing the relevant query result key
- There is a subsequent network call to retrieve the result data using
the result key from the previous response
6. (With browser inspector still open) Run another query -- this can be the
same query or a different one
7. Observe that the query results are unexpectedly not displayed with the
message "Run a query to display results" shown and:
- The call to `/api/v1/query/updated_since` returned an empty array
- No subsequent network calls are made
8. Check the superset worker logs to confirm there are no errors in
processing the query or storing results
9. Obtain the result key from the superset worker logs and confirm results
actually exist
### Expected results
It is expected that whenever a query is run in the SQL Lab that results will
populate in the UI and will not show the message "Run a query to display
results" -- or perhaps specifically that the `/api/v1/query/updated_since` does
not return an empty array
### Actual results
No updated queries are returned by the call to `/api/v1/query/updated_since`
and hence the UI never populates any result data, despite the fact the query
indeed runs and has results
#### Screenshots
Here are a couple videos showing the problem as described
<details>
<summary>full video</summary>
[full
version](https://github.com/apache/superset/assets/15212758/77bb2c50-d795-4497-a5ba-6a0dd4f86726)
</details>
<details>
<summary>short video</summary>
[short
version](https://github.com/apache/superset/assets/15212758/9357b64c-5096-4ebd-8059-449544d73f30)
</details>
### Environment
(please complete the following information):
- browser type and version: firefox 114.0.1 on MacOS
- superset version: docker latest
(`apache/superset:45901dafbb1258f57dd314a03e211fd81b258a58`)
- python version: 3.9.16 (from docker image)
- node.js version: (not sure? N/A)
- any feature flags active: None
### Checklist
Make sure to follow these steps before submitting your issue - thank you!
- [x] I have checked the superset logs for python stacktraces and included
it here as text if there are any.
- [x] I have reproduced the issue with at least the latest released version
of superset.
- [x] I have checked the issue tracker for the same issue and I haven't
found one similar.
### Additional context
Add any other context about the problem here.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
