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

Your dashboard is too large. Please reduce the size before save it. #15169

Closed
1 of 3 tasks
ramesh2744 opened this issue Jun 15, 2021 · 8 comments
Closed
1 of 3 tasks

Your dashboard is too large. Please reduce the size before save it. #15169

ramesh2744 opened this issue Jun 15, 2021 · 8 comments
Labels
#bug Bug report

Comments

@ramesh2744
Copy link

ramesh2744 commented Jun 15, 2021

Expected results

Dashboard should allow to add the new charts and resizing the charts after clicking save button.

Actual results:

I have an existing dashboard created and contains some charts. Now, I'm trying to add the new charts to it.
Dashboard is not allowing me to save after adding the new charts. Instead, it shows a pop up as shown in below screenshot.

Screenshots

image

Environment

  • superset version: 1.0.1
  • python version: python 3.7
  • OS: Ubuntu 16.04

Checklist

  • I have checked the superset logs for python stack traces and included it here as text if there are any.
  • I have reproduced the issue with at least the latest released version of superset.
  • I have checked the issue tracker for the same issue and I haven't found one similar.
@ramesh2744 ramesh2744 added the #bug Bug report label Jun 15, 2021
@ramesh2744
Copy link
Author

ramesh2744 commented Jun 15, 2021

I got confusion in adding for this one as bug or improvement. For now, I Kept this issue as a bug. Please change it to respective category as needed.

@yousoph
Copy link
Member

yousoph commented Nov 11, 2021

Hi @ramesh2744 , have you run into this issue recently? If so, can you give a bit more info about your dashboard? How many charts, tabs, types of charts, etc
Thanks!

@yousoph
Copy link
Member

yousoph commented Nov 30, 2021

Closing as we've been unable to repro. Please reopen with more details if you're still able to reproduce this issue, thanks!

@yousoph yousoph closed this as completed Nov 30, 2021
@kaspergaj
Copy link

I still experience the issue with the latest Superst 1.3.2.

We're making dashboards where clients can only view and apply filters (not create their own charts). Therefore the dashboards have to be extensive to support any desired visualisation.

One of the impacted dashboards have 5 main tabs, about 75 charts, and 10 filterboxes. It's mainly bar charts in this one, but other impacted dashboards have time-series charts.

@Kingflyinger
Copy link

I still experience the issue with the latest Superst 1.3.2.

We're making dashboards where clients can only view and apply filters (not create their own charts). Therefore the dashboards have to be extensive to support any desired visualisation.

One of the impacted dashboards have 5 main tabs, about 75 charts, and 10 filterboxes. It's mainly bar charts in this one, but other impacted dashboards have time-series charts.

this issue has been closed,if you need help please open a new issue

@Kingflyinger
Copy link

I still experience the issue with the latest Superst 1.3.2.

We're making dashboards where clients can only view and apply filters (not create their own charts). Therefore the dashboards have to be extensive to support any desired visualisation.

One of the impacted dashboards have 5 main tabs, about 75 charts, and 10 filterboxes. It's mainly bar charts in this one, but other impacted dashboards have time-series charts.

I searched the code,and found edit the config.py can solve it.
1642055089495_466A4241-3C35-47e5-A82F-B6D6F4602773

SUPERSET_DASHBOARD_POSITION_DATA_LIMIT = 85195

@villebro
Copy link
Member

@Kingflyinger FYI, you can modify that parameter in your superset_config.py. The default value is set based on the maximum size of the TEXT column type in an old MySQL version: https://stackoverflow.com/questions/6766781/maximum-length-for-mysql-type-text#:~:text=TEXT%20is%20a%20string%20data,maximum%20length%20of%204%2C294%2C967%2C295%20characters. For Postgres or a newer version of MySQL I believe this is around 1Gb, so you can safely add a few zeros to the current default value which is 65535.

@Kingflyinger
Copy link

@Kingflyinger FYI, you can modify that parameter in your superset_config.py. The default value is set based on the maximum size of the TEXT column type in an old MySQL version: https://stackoverflow.com/questions/6766781/maximum-length-for-mysql-type-text#:~:text=TEXT%20is%20a%20string%20data,maximum%20length%20of%204%2C294%2C967%2C295%20characters. For Postgres or a newer version of MySQL I believe this is around 1Gb, so you can safely add a few zeros to the current default value which is 65535.

thank you for your information, I searched DB storage and found nothing. happy to know I can just add zeros

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#bug Bug report
Projects
None yet
Development

No branches or pull requests

5 participants