GitHub user rajathc93 created a discussion: Add e6data as a standard supported 
database engine in Apache Superset

### Background

We’d like to propose adding **e6data** as a standard, natively supported 
connector in **Apache Superset** (visible in the “+ Database” flow).

Currently, we can connect to e6data using a custom SQLAlchemy URI by manually 
adding our connector package to `requirements.txt` 
([**e6data-python-connector** on 
PyPI](https://pypi.org/project/e6data-python-connector/)) and then creating a 
custom connection.
However, features such as **time grain support** and **engine-specific 
configurations** currently require manual changes under `db_engine_specs`.


### About e6data
e6data is a distributed, high-performance query engine designed for low-latency 
interactive analytics. It supports querying open table formats such as **Delta, 
Iceberg, and Hudi** across multiple catalogs (Glue, Hive, Unity Catalog, etc.) 
and integrates with BI tools via JDBC/SQLAlchemy connectors.


---

### Motivation
Adding e6data as a standard connector will:
- Simplify onboarding for Superset users who want to query large open-format 
datasets.
- Eliminate manual config changes to enable e6data connections.
- Promote consistency and supportability via standardized engine spec and test 
coverage.

---

### Questions for Maintainers
- What is the process for getting a **new connector officially accepted** as a 
standard database support in Superset?
- Are there specific guidelines or review steps (schema validation, tests, 
docs) we should follow?
- Is there a preferred way to add the connector endpoint for the new Database 
Connection UI?

We’re happy to contribute both the dialect and the Superset integration code, 
along with documentation and tests.



GitHub link: https://github.com/apache/superset/discussions/35901

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: 
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to