-
Notifications
You must be signed in to change notification settings - Fork 371
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
Hue UI showing Should be running if Processing response multiple times #3167
Comments
Hi @sbbagal13, thanks for reporting. I have reproduced this on our demo site and will create an internal jira to have this further investigated and fixed. |
This issue is stale because it has been open 30 days with no activity and is not "roadmap" labeled or part of any milestone. Remove stale label or comment or this will be closed in 5 days. |
@bjornalm I hope, we are going to keep this open and working towards resolution. |
@sbbagal13 It has not been forgotten. @agl29 can you have a look? |
Hi, We are also facing similar issue intermittently. Especially first time when user logs in or randomly when we run query from Hue UI. |
Hello @sbbagal13 and @vpattar , |
Hello @agl29 , which tag/build will have these Trino enhancements? |
Hello , We are also facing this issue of "Should be running if Processing response" error on hue ui . This seems to be happen randomly when we run query from Hue UI or first time when user logs in . We are running hue with presto as on kubernetes environment. The current configration is as below ` interpreters: | [[[mysql]]] [[[presto]]] Can I know if there is a fix for this that is being worked on ? If yes, in which hue version would this be available ? |
Running Trino queries from Hue and multiple time UI showing error " Should be running if Processing response" multiple times but query gets executed at backend , no response back to UI (Error image attached)
version: 4.10 latest from Docker hub
Rerunning same query will works fine but earlier query unnecessary wastes the resources from Trino.
The text was updated successfully, but these errors were encountered: