Create bucket with on non default port through java api

zxcvmnb · November 23, 2016, 9:15am

For some reason java api to insertBucket hardcodes authType to sasl.
See

couchbase/couchbase-java-client/blob/master/src/main/java/com/couchbase/client/java/cluster/DefaultAsyncClusterManager.java#L282


            }
        }));
}


@Override
public Observable<BucketSettings> updateBucket(final BucketSettings settings) {
    final String payload = getConfigureBucketPayload(settings, false);


    return ensureBucketIsHealthy(hasBucket(settings.name())
        .doOnNext(new Action1<Boolean>() {
            @Override
            public void call(Boolean exists) {
                if(!exists) {
                    throw new BucketDoesNotExistException("Bucket " + settings.name() + " does not exist!");
                }
            }
        }).flatMap(new Func1<Boolean, Observable<UpdateBucketResponse>>() {
            @Override
            public Observable<UpdateBucketResponse> call(Boolean exists) {
                return core.send(new UpdateBucketRequest(settings.name(), payload, username, password));
            }

Setting port passed by user in bucket settings is irrelevant after this, since buckets with sasl authType are always created with fixed port.

Why is sasl authType hardcoded there ?

ingenthr · November 23, 2016, 11:36pm

The main reason is that the port setting really sets up server side moxi. With the Java client, we don’t use moxi-- we go directly to the port and sasl auth. That’s actually be the preferred method since about Couchbase 1.8 back in 2011.

Do you still use server side moxi? If so, what client requires you to use it?

zxcvmnb · November 24, 2016, 12:05pm

Sorry, I am not familiar with moxi, but I guess you mean that bucket create will succeed but any further operations on it will fail.
IMHO with SDK it generally should be possible to create any bucket which can be created from UI or CLI.

ingenthr · November 28, 2016, 5:55pm

Mainly what I mean is that Couchbase’s support for setting the port number on a bucket is probably not doing what you think it is doing. When you configure this, it’s running a proxy for clients that don’t know how to do authentication. It’s a deprecated, non-recommended feature, so there is no reason to add SDK support for configuring it.