SDK 2.0: custom serialization

[cameronpearce]

I have also found this bug and describe it here:

Couchbase Bucket does not use configured transcoder

I have configured the JSON serialiser settings using the Cluster constructor that takes a ClientConfiguration class. When using the CouchbaseBucket class, any of the upsert methods, it creates an instance of Set, but uses the constructor that does not take the transcoder that the bucket is using, hence, it then defaults to DefaultTranscoder without any custom config settings. Is there a reason for this? If not, can it be changed to inherit the buckets transcoder on Upsert? Thanks Cam

It is on the Upsert Methods on the CouchbaseBucket class.
It creates a new instance of Set which does not pass the buckets transcoder which is configured with your custom settings (serialisation/deserialisation settings).

Hence it defaults to the default transcoder with the CamelCasePropertyNamesContractResolver.