Java client compression threshold
Tue, 02/12/2013 - 06:38
Hi,
In my company we are using couchbase to store our meta data for real time requests.
The data is updated by a java server using the Java sdk and the data is read by a ngnix server that is not using the java sdk.
A problem we encountered is that when reading large values the response was binary instead of string.
After checking the client java source code i saw that the default set operation is using a transcoder with a 16KB compression threshold, values larger than 16KB are compressed.
The documentation does not address this issue, can you please update the documentation to mention it since it is not obvious.
I have filed an issue for this which you can follow at the link below. We will get the documentation updated as soon as possible.
http://www.couchbase.com/issues/browse/JCBC-296