-
Notifications
You must be signed in to change notification settings - Fork 27
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
Add support for couchbase3 client #623
Comments
Community members can take a look at the PR first. Although it is a draft, the API part has been completed. Next, the main tasks are to complete the annotations, documentation, testing, and testing framework. Most APIs are based on collection. In Couchbase3, cluster (Connection) ->bucket ->scope ->collection So I made the collection an implicit The old couchbase has a SessionKey (setting, bucket) connection pool, which we no longer need. I haven't implemented it yet. The connection is not based on buckets, but on clusters. I will temporarily put aside the implementation of pekko-couchbase-discovery. |
@pjfanning @mdedetrich @He-Pin |
Thanks for putting a lot into this, I will check this after work. |
I have basically completed the work on adding couchbase3, but not doc. |
I've merged the implementation PR but left this open because we'll need at least some doc changes to reflect the new cloudbase3 connector. |
Yeah, I just finished my vacation, but I'm about to go on a business trip and will be doing this PR on this Sunday |
I spent about 6 weekends (30 hours) trying to transitie Couchbase2 to Couchbase3 smoothly. In the end, I basically completed the code migration, but it became very ugly and difficult to use and test, so I closed that PR.
#400
#503
#504
I spent about 3 days rewriting the connector. Mainly referring to the mongo connector.
The new connector is similar to the Mongo connector, with only API packaging for the SDK. The couchbase-SDK is already very powerful.
Couchbase-sdk also provides APIs for mono and flux (based on the built-in Completufurture). I also design the API of pekko-connector-3 with the async api(Completufuture)
I just did two tests, and I will complete the rest and docs next week or Labor Day.
Source api
Flow api
Sink api
The text was updated successfully, but these errors were encountered: