Tatu Saloranta

Right, unfortunately use of `JsonNode` is not going to be easy as things are. There was an idea originally to allow customized alternative trees (from ObjectMapper perspective) but things get...

It should all "just work" if (and only if) matching Avro Schema has compatible definition, so I am not 100% sure what the problem is. Maybe a simple test case...

Ahhhh. So the contributions for adding that were somewhat... Opinionated. I forgot that as it's not code I wrote or designed. But one thing that could be done easily, I...

@mpsandiford Just to make sure I understand this correctly: I think you are suggesting addition of a `CBORGenerator.Feature` that would force use of length-prefix for all Strings. Is that correct?...

Ok cool. As I said, it may take a while to get this done if I do it (would be in 2.10.0 regardless, being new feature) just due to piling...

(modified title as #1 already covers case of known-length arrays)

As per example, usage would be via Streaming API (generator), and supporting that should be a bit easier than general-purpose databind. At databind, `Map`s could perhaps be supported as well....

Not really. You can by-pass encoder with `writeRaw` / `writeRawValue` but that pretty much defeats the purpose.

Ah. Well spotted. The reason I missed that was that I had thought of adding method in `JsonGenerator`, but hadn't because of being unsure if and how to combine with...

@quannh0308 I don't think this can work as general `SerializationFeature` as it is CBOR-specific, unfortunately: tracking of sizes for all uses complicates code and adds overhead, primarily because then potentially...