Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please support CiviCRM #17108

Closed
colleendowd opened this issue Oct 14, 2021 · 1 comment
Closed

Please support CiviCRM #17108

colleendowd opened this issue Oct 14, 2021 · 1 comment

Comments

@colleendowd
Copy link

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.

@srinify
Copy link
Contributor

srinify commented Oct 14, 2021

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.

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!

@srinify srinify closed this as completed Oct 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants