I’m working with the Java client, and I want to do some BSON encoding (for append operations) and I’m unable to leverage bson4jackson because it depends on the public Jackson namespace, yet rather the dependency on Jackson is included in core-io.
So, I’m stuck with:
Why is it this way and not a traditional dependency? Any workarounds?
Bumping this up to re-engage discussion. Just got burned by things not working as expected due to a mix of Jacksons. If I have my entities annotated with “real” Jackson and then they are processed by “couchbase” Jackson, the annotations are in a different namespace and not respected.
This leads to really awful, undesirable behavior: Data loss.
I think it should be reconsidered to have this. It just opens up the opportunities for undetectable bugs.