Details
-
Bug
-
Resolution: Fixed
-
Major
-
5.5.0, 5.5.1, 5.5.2, 5.5.3, 5.5.4, 5.5.5, 6.0.0, 6.0.1, 6.0.2
Description
Summary
When performing a GET on a document that is both compressed and has xattrs.
If the client supports compression, we can get into a situation where we uncompress the document but send it to the client with the compressed flag still set.
Details
With a get request the document is uncompressed to allow the xattrs to be stripped before the document is sent to the client. However we do not clear the snappy datatype on the document before sending the document.
On a client that does not support compression that is OK because we set the document datatype based on the intersect of what the document datatype is and what the client supports and hence the snappy datatype is cleared. However on a client that supports compression the snappy datatype is not cleared.
This results in the server sending a document that is marked as snappy compressed but the payload is not compressed. Therefore the SDK raises an error when it attempts to decompress the payload.
Attachments
Issue Links
- is duplicated by
-
MB-36299 community edition negotiating snappy, setting bit when it should not
- Closed