This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/master by this push:
new ef59789 Added compatibility notes for server 5 and beyond
ef59789 is described below
commit ef5978900e61318f23cc33c63170616a3f762a17
Author: kwosie <kwo...@users.noreply.github.com>
AuthorDate: Tue Jun 4 22:49:50 2019 +0200
Added compatibility notes for server 5 and beyond
I struggled a bit with the couchbase component, where it constantly
complained about authentication failure. Once I discovered that the camel
component is utilizing an older version of the couchbase sdk (1.4.13), I
thought I won't be able to use the component until it is upgraded to version
2.4+. But with the notes on using the legacy SDK, I managed to utilize this
couchbase component with my current version of couchbase.
---
components/camel-couchbase/src/main/docs/couchbase-component.adoc | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/components/camel-couchbase/src/main/docs/couchbase-component.adoc
b/components/camel-couchbase/src/main/docs/couchbase-component.adoc
index 0a75ae6..2584adb 100644
--- a/components/camel-couchbase/src/main/docs/couchbase-component.adoc
+++ b/components/camel-couchbase/src/main/docs/couchbase-component.adoc
@@ -148,3 +148,10 @@ The component supports 3 options, which are listed below.
|===
// spring-boot-auto-configure options: END
+=== Couchbase SDK compatibility
+This component is currently using a "Legacy SDK" version of couchbase-client.
+
+In order to authenticate with newer versions of Couchbase Server 5.0 and
beyond, as per instructions on the
https://docs.couchbase.com/java-sdk/2.7/sdk-authentication-overview.html/[CouchBase
Java SDK Authentication]:
+
+ * The value formerly interpreted as a bucket-name is now interpreted as a
username. The username must correspond to a user defined on the cluster that is
being accessed.
+ * The value formerly interpreted as a bucket-password is now interpreted as
the password of the defined user.
