Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
sdk-3.2
-
DOC-2021-Dec19-S25, DOC-2021-Dec31-S26, DOC-2022-S1, DOC-2022-S2
-
1
Description
The documentation is using the wrong name here:
https://docs.couchbase.com/dotnet-sdk/current/howtos/error-handling.html#document-body-too-large
From Gitter.im:
Hey All, I am busy looking at https://docs.couchbase.com/server/current/learn/clusters-and-availability/size-limitations.html and seeing how we could cater for these limits (CouchbaseNetClient query). In the documentation it mentions this https://docs.couchbase.com/dotnet-sdk/current/howtos/error-handling.html#document-body-too-large but this type 'RequestTooBigException' does not exist in https://github.com/couchbase/couchbase-net-client/search?q=RequestTooBigException? potentially the docs are outdated?
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?
Attachments
Issue Links
- relates to
-
NCBC-3008 RequestTooBigException should be ValueTooLargeException
- Resolved