Possibly update to Jackson `3.x`

[onobc]

Need to first determine if this is possible w/ Pulsar current use and dependence on Jackson 2.x.
Then update to 3.x if it is possible.
If not possible, ensure we can live w/ 2.x.

Note

Take a look at Spring Data PR

[therepanic]

Hi, @onobc. If it possible, you can assign me, and I can try to migrate to jackson 3. If we encounter any obstacles, we can decide whether to stay on 2.x or not.

[onobc]

Hi @therepanic , we can definitely pair on this but I will not have cycles to look for a couple of weeks. I will tell you what I know and hopefully give you enough info to start digging in.

So, the interesting piece here is understanding how to support both Jackson 2 and 3. You can see an example in the Spring Data PR listed in the description above. Where needed a pair of Jackson 2 and 3 classes are created and one of them is chosen at runtime based on the version of Jackson on the classpath.

Here are the areas of interest that need to be understood/investigated to decide direction:

• User's can set a custom object mapper used when producing/consuming messages (docs)

• Users's can set a custom object mapper that can be used for de/ser Pulsar message headers (this doc seems to not be linked in the main docs nav but is here and you can find more by exploring JsonPulsarHeaderMapper)

• If you search for ObjectMapper in the public API you can see where we will have to consider how to deal w/ an OM class from 2 and from 3 as they have package name change at the very least.

The biggest help would be digesting the Spring Data approach and then digging through the above areas and understanding what this will look like for Spring Pulsar.

Warning

The Pulsar Client and the Pulsar Server use Jackson 2 and have no current plans on updating to 3. I don't know what this means for the above but keep an eye out for weirdness / issues.