Why not release your own provider and expose it via https://airflow.apache.org/ecosystem/#third-party-airflow-plugins-and-providers. - there are plenty of 3rd-party providers written, maintained and released by respective owners. We are reluctant in accepting new providers because - to put it bluntly - this means that the community has to make sure it works, test it and whenever couchbase changes or modifies their API, also follow that up. It's much easier the other way round - when the respective owner maintains their own provider (and many do as you can see).
What makes you think that couchbase will do better as "community managed" ? J. On Thu, Sep 19, 2024 at 10:12 PM Shyam Rajamannar <shyam.ven...@couchbase.com.invalid> wrote: > Hi, > > My name is Shyam, and I work at Couchbase. On behalf of Couchbase, I would > like to contribute to Apache Airflow by adding a Couchbase provider. This > contribution is aimed at enabling a wider reach of Couchbase as a viable > option for users of Apache Airflow, facilitating easier integration and use > in ETL and data pipeline processes. > > I have forked the repository and implemented the initial code for the > Couchbase provider. You can find the draft PR for your review here: > https://github.com/apache/airflow/pull/42271 > > Summary of Changes: We created a hook for Couchbase that exposes the > Couchbase client, scope, and collection. Additionally, the code includes > functionality to modify the connection field information. > > Please let me know if you have any feedback or suggestions. > > Thank you! > > Best regards, > Shyam Venkat > Couchbase >
