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

User feedback on "explore_json" API request failure #7128

Closed
larshelge opened this issue Mar 26, 2019 · 1 comment
Closed

User feedback on "explore_json" API request failure #7128

larshelge opened this issue Mar 26, 2019 · 1 comment
Labels
inactive Inactive for >= 30 days

Comments

@larshelge
Copy link

larshelge commented Mar 26, 2019

This is a feature request for providing user-facing feedback on failed request for data through the explore_json API endpoint.

Story: A user puts together a chart and clicks "Run query". The query fails for some reason, e.g. because there is no data for the particular query / chart selection. The query currently fails silently with no user feedback and leaves the user wondering why nothing happens.

It would be useful to provide the user with some meaningful feedback in these cases. As an example, display a message "No data found" when there is no data returned for the query.

As an example, the /superset/explore_json/ API request might return HTTP status 400 with a message error: "No data" inside the JSON response. In this case, the "No data" could be displayed to the user.

Based on SuperSet version 0.28.1 connected to a Redshift cluster.

@larshelge larshelge changed the title User feedback on "explore_json" request failure User feedback on "explore_json" API request failure Mar 26, 2019
@stale
Copy link

stale bot commented May 25, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

@stale stale bot added the inactive Inactive for >= 30 days label May 25, 2019
@stale stale bot closed this as completed Jun 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
inactive Inactive for >= 30 days
Projects
None yet
Development

No branches or pull requests

1 participant