You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make sure these boxes are checked before submitting your issue - thank you!
I have checked the superset logs for python stacktraces and included it here as text if 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
Superset version
0.18.4
Expected results
I've set a filter slice in order to filter a whole dashboard at once, but I need the other slices to execute themselves only if a filter is set, because there's (700*(12*10)*20)*12 records if I just run the query without any filter.
Actual results
No filter set at first, (700*(12*10)*20)*12 records, huge loading time
The text was updated successfully, but these errors were encountered:
You can hack something possibly by adding a flag to the slice and then sort out how to return an error if there's not filter set in the ui. Anyway 20M rows shouldn't be something that a machine can't handle.
Yes, that's the point. If I set a filter, it goes from 20M to 250 rows, which is way better. And the point is I can't even save the query in order to do anything with it, since Superset can't fetch the data from it.
Make sure these boxes are checked before submitting your issue - thank you!
Superset version
0.18.4
Expected results
I've set a filter slice in order to filter a whole dashboard at once, but I need the other slices to execute themselves only if a filter is set, because there's (700*(12*10)*20)*12 records if I just run the query without any filter.
Actual results
No filter set at first, (700*(12*10)*20)*12 records, huge loading time
The text was updated successfully, but these errors were encountered: