srinify commented on issue #17108: URL: https://github.com/apache/superset/issues/17108#issuecomment-943378356
Hi there @colleendowd welcome to the Superset community! Currently, Superset's design & architecture is optimized for querying SQL speaking data sources. This could be a data warehouse, a traditional OLTP database, a federated query engine, or something else entirely that speaks SQL. This is the current base requirement! Afterwards, the data source needs a SQLAlchemy dialect & a Python DB-API 2.0 driver as well. I've written about some of the requirements here [in this blog post](https://preset.io/blog/building-database-connector/). **CiviCRM** It doesn't seem like CiviCRM has a sqlalchemy dialect and it doesn't look like a SQL speaking database more generally. Most organizations copy data using data-syncing tools like Meltano, Airbyte, FiveTran, Stitch Data, etc from a 3rd party source (like CiviCRM) to their internal data warehouse. This is considered the best practice here! **SIP** I saw that you filled out the template for a SIP. For future reference -- SIP's are focused on big structural changes to the Superset project, not for feature requests. I hope this context helps! -- 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]
