On Mon, Oct 14, 2024 at 7:12 AM Shyam Rajamannar <shyam.ven...@couchbase.com.invalid> wrote:
> Hi Amogh, Jarek > > Sure, we will go with the custom provider approach. Thanks for the > feedback. > > Also, I just need to create a PR to https://github.com/apache/airflow-site > to update the ecosystem docs, right? > Yes. Just click "Suggest a change on this page" (bottom-left) and PR will be opened for you automatically with the right file to update. > > > Best regards, > Shyam Venkat > Couchbase > > From: Amogh Desai <amoghdesai....@gmail.com> > Date: Monday, 7 October 2024 at 11:37 AM > To: dev@airflow.apache.org <dev@airflow.apache.org> > Subject: Re: [DISCUSSION] Proposal to Add Couchbase Provider to Apache > Airflow > I second the thought of Jarek here. > > I also think it is better to go with third party providers in terms of long > term commitment > to the provider and the fact that it would provide better sustainability. > > Thanks & Regards, > Amogh Desai > > > On Tue, Oct 1, 2024 at 11:36 AM Jarek Potiuk <ja...@potiuk.com> wrote: > > > 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 > > > > > >
