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!
[ x] I have checked the superset logs for python stacktraces and included it here as text if any
[ x] I have reproduced the issue with at least the latest released version of superset
[ x] I have checked the issue tracker for the same issue and I haven't found one similar
Superset version
up to 0.26.2
Expected results
could join other table when creating a chart
Actual results
could not join other table
Steps to reproduce
Table join is vital important for us. During the time we use superset in production, we have created tons of intermedium flat tables which joins many data in order to make a compromise to the lack of join in superset. This intermedium table is not efficient when adding new columns and creating itself.
sqllab will not do the trick here since time range is fixed in the sql and Charts cannot push the time range to the sub sql. Besides, if the data amount of a table is very huge, makes it harder for the query engine to run.
The text was updated successfully, but these errors were encountered:
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.
Make sure these boxes are checked before submitting your issue - thank you!
Superset version
up to 0.26.2
Expected results
could join other table when creating a chart
Actual results
could not join other table
Steps to reproduce
Table join is vital important for us. During the time we use superset in production, we have created tons of intermedium flat tables which joins many data in order to make a compromise to the lack of join in superset. This intermedium table is not efficient when adding new columns and creating itself.
sqllab will not do the trick here since time range is fixed in the sql and
Charts
cannot push the time range to the sub sql. Besides, if the data amount of a table is very huge, makes it harder for the query engine to run.The text was updated successfully, but these errors were encountered: