Configure Couchbase to use the application's ObjectMapper

[micopiira]

Could the CouchbaseAutoConfiguration use existing Jackson ObjectMapper bean instance by default?

Maybe add something like this to the CouchbaseAutoConfiguration class?

@Bean
@ConditionalOnBean(ObjectMapper.class)
public ClusterEnvironmentBuilderCustomizer cluster(ObjectMapper objectMapper) {
  return builder -> builder.jsonSerializer(JacksonJsonSerializer.create(objectMapper));
}

[philwebb]

On the surface, this seems like a good suggestion, however, there's a downside. If we auto-configure the builder.jsonSerializer then the user hasn't got a good way to opt-out and go back to the defaults. Unfortunately you can't call builder.jsonSerializer(null).

There's also some interesting logic regarding CryptoManager (see JacksonJsonSerializer.create(CryptoManager cryptoManager).

@micopiira Can you explain a bit more about why you're plugging in the ObjectMapper bean? Do you want specific Jackson customization?

[micopiira]

@philwebb The default CouchbaseAutoConfiguration does not support serializing Java 8/JSR310 types (Optional, Instant, etc.) out of the box, because the DefaultJsonSerializers ObjectMapper does not register Jdk8Module or JavaTimeModule.

Ofcourse I can configure this myself, but I would expect a Spring Boot application to support this out of the box.

And regarding your earlier comment of opting-out, I guess users could always call builder.jsonSerializer(DefaultJsonSerializer.create()) ?

[philwebb]

Thanks @micopiira, that's useful feedback.

[wilkinsona]

Now that we know that it's easy to restore Couchbase's defaults (thanks for the hint, @micopiira), I think it makes sense for us to configure Couchbase to use Boot's ObjectMapper out of the box.