With regards to Max Key Length, I noticed there is no validation or specific exception. A consumer would land up receiving 'The output byte buffer is too small to contain the encoded data, encoding 'Unicode (UTF-8)' fallback 'System.Text.EncoderReplacementFallback'. I know it is potentially an edge case but I wanted to ask whether we would consider adding some defensive code in the SDK against this scenario?
The docs have the wrong exception here: https://docs.couchbase.com/dotnet-sdk/current/howtos/error-handling.html#document-body-too-large
Reported on Gitter.im: