airbots opened a new issue #17666: URL: https://github.com/apache/superset/issues/17666
When we use sql editor to create a query and get the derived data. If we want to save it, Superset does not check if schema is not configured or not. It should. If we let be null and click "save as", the schema will be null. And non-superuser will never see this dataset anymore when they click the datasets on the navigation bar and can not create a chart based on the derived data. #### How to reproduce the bug 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error ### Expected results what you expected to happen. ### Actual results what actually happens. #### Screenshots If applicable, add screenshots to help explain your problem. ### Environment (please complete the following information): - browser type and version: - superset version: `superset version` - python version: `python --version` - node.js version: `node -v` - any feature flags active: ### Checklist Make sure to follow these steps before submitting your issue - thank you! - [ ] I have checked the superset logs for python stacktraces 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. ### Additional context Add any other context about the problem here. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
