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
Please make sure you are familiar with the SIP process documented
(here)[https://github.com//issues/5602]. The SIP number should be the next number after the latest SIP listed here.
[SIP-<number>] Proposal for <title>
Motivation
Description of the problem to be solved.
Proposed Change
Describe how the feature will be implemented, or the problem will be solved. If possible, include mocks, screenshots, or screencasts (even if from different tools).
New or Changed Public Interfaces
Describe any new additions to the model, views or REST endpoints. Describe any changes to existing visualizations, dashboards and React components. Describe changes that affect the Superset CLI and how Superset is deployed.
New dependencies
Describe any npm/PyPI packages that are required. Are they actively maintained? What are their licenses?
Migration Plan and Compatibility
Describe any database migrations that are necessary, or updates to stored URLs.
Rejected Alternatives
Describe alternative approaches that were considered and rejected.
The text was updated successfully, but these errors were encountered:
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.
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.
Please make sure you are familiar with the SIP process documented
(here)[https://github.com//issues/5602]. The SIP number should be the next number after the latest SIP listed here.
[SIP-<number>] Proposal for <title>
Motivation
Description of the problem to be solved.
Proposed Change
Describe how the feature will be implemented, or the problem will be solved. If possible, include mocks, screenshots, or screencasts (even if from different tools).
New or Changed Public Interfaces
Describe any new additions to the model, views or
REST
endpoints. Describe any changes to existing visualizations, dashboards and React components. Describe changes that affect the Superset CLI and how Superset is deployed.New dependencies
Describe any
npm
/PyPI
packages that are required. Are they actively maintained? What are their licenses?Migration Plan and Compatibility
Describe any database migrations that are necessary, or updates to stored URLs.
Rejected Alternatives
Describe alternative approaches that were considered and rejected.
The text was updated successfully, but these errors were encountered: