villebro commented on issue #35003: URL: https://github.com/apache/superset/issues/35003#issuecomment-3716647897
I like the idea of generalizing from SQLAlchemy to something more generic. I feel SQL, and in particular SQLAlchemy, has given us a lot over the years, and Superset wouldn't have become as successful as it has without it. However, I feel with a little architectural wizardry, we should be able to open up Superset to other sorts of integrations, like - Non-SQL based datasources, like Prometheus - Non-tabular datasources, like graph databases, REST APIs The [long standing request to support PromQL and other TSDBs](#2686) is a good indication that there is demand for Superset outside pure SQL. Making this generic isn't necessarily easy, but at least considering these will help us isolate the boundaries we want to work with in the future. For instance, if we do decide to only support tabular datasources, then that should dictate the structure of the `Explorable` and `ExplorableData` interfaces. But if we want to go more generic, we may need deeper abstractions, like `TabularExporableData` which in turn extends `ExplorableData`. The same would then need to apply to charts, controls etc, as SQL controls will likely behave very differently from non-tabular datasource controls. -- 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]
