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

[Bug] Sqllab -> Explore -> Bar Chart #5947

Closed
hughhhh opened this issue Sep 20, 2018 · 3 comments
Closed

[Bug] Sqllab -> Explore -> Bar Chart #5947

hughhhh opened this issue Sep 20, 2018 · 3 comments
Labels
inactive Inactive for >= 30 days

Comments

@hughhhh
Copy link
Member

hughhhh commented Sep 20, 2018

When users write a query and then move to the explore view, the table view reders but once they try to click a Bar Chart - Distribution type viz the explore blanks out. The only way to get back the current state is copying the link and reloading the page.

Steps to Reproduce:

  1. Goto sqllab
  2. Run the query
  3. Click Explore btn
  4. Change viz type to 'Distribution Bar Chart`
  5. Set metrics = SUM(ride_count) and series = 'venue_name`

StackTrack:
{“error”: “The datasource associated with this chart no longer exists”, “stacktrace”: “Traceback (most recent call last):\n File \“/srv/venvs/service/trusty/service_venv_python3.6/lib/python3.6/site-packages/superset/views/core.py\“, line 1158, in explore_json\n datasource_id, datasource_type, form_data)\n File \“/srv/venvs/service/trusty/service_venv_python3.6/lib/python3.6/site-packages/superset/views/core.py\“, line 1217, in datasource_info\n ‘The datasource associated with this chart no longer exists’)\nException: The datasource associated with this chart no longer exists\n”}

bug-explore

@hughhhh hughhhh assigned hughhhh and unassigned hughhhh Sep 20, 2018
@iamnewneo
Copy link

I am also facing the same issue. How can we solve this? @hughhhh did you find any hack for this?

@mrshu
Copy link
Contributor

mrshu commented Mar 14, 2019

I also ran into this today. @hughhhh @iamnewneo do you happen to have any way of mitigating this problem? Could it be in nay way related to #5019?

Thanks!

@stale
Copy link

stale bot commented May 13, 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 13, 2019
@stale stale bot closed this as completed May 20, 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

3 participants