As discussed before - in slack and issues, we are currently in the process of discussing the process of accepting new providers [1] - there were potential changes discussed there - including incubation period, having a team that is committed (and accountable) to make sure that the provider submitted to Airflow is going to be maintained in the future - I think it will take that discussion to complete before we consider accepting new providers.
I suggest you respond to the governance thread and comment on those proposals and explain how your proposal fits the proposed governance process, what you see as possible changes or where you see difficulties - that would certainly help in finalising the discussion and helping with unblocking new provider submissions. Actually I think it's a good idea to have anyone who wants to submit a new provider to actively participate in that discussion - because there are certain things we thing about "expecting" from those who submit the provider and certain level of commitment it involves, so getting feedback from those who would like to submit a new provider is crucial to get the process better. [1] https://lists.apache.org/thread/qrv0j4dxp2yg09gds40vh49dhkbrj5q9 J. On Fri, Oct 24, 2025 at 2:30 PM Pratyush Maheshwari < [email protected]> wrote: > Hi All, > > Please find the raised issue: > https://github.com/apache/airflow/issues/56846 > > Overview > I would like to contribute a comprehensive MariaDB provider to Apache > Airflow that includes: > > Native MariaDB connector support > ColumnStore engine integration > Bulk data loading with cpimport utility > S3 integration for data transfer > SSH-based remote execution > > > Why a Separate MariaDB Provider? > While MySQL provider exists, MariaDB has unique features that justify a > dedicated provider: > > Native MariaDB Connector: Uses mariadb library instead of generic MySQL > connector > It is seen that using Native Mariadb as a python connector performs 2-3x > better for operations like insert_many, json handling and select queries. > cpimport Utility: Bulk loading functionality specific to MariaDB > ColumnStore > ColumnStore Engine Support: Validation and optimization for ColumnStore > tables > S3 Integration: Direct S3 load/dump operations > SSH Integration: Remote execution capabilities > Components Included > MariaDBHook: Main hook with native connector support > MariaDBOperator: SQL execution operator > MariaDBCpImportOperator: Bulk data loading for ColumnStore > MariaDBS3LoadOperator: Load data from S3 to MariaDB > MariaDBS3DumpOperator: Export MariaDB data to S3 > > Comprehensive test suite with 95%+ coverage > Example DAGs for all features > Complete documentation > Dependencies > mariadb>=1.1.0 (native connector) > boto3>=1.26.0 (S3 integration) > paramiko>=2.7.0 (SSH support) > > Please let me know your thoughts before I submit my PR. > > Thanks, > Pratush Maheshwari >
