http://www.couchbase.com/issues This file is an XML representation of an issue en-us 5.2.4 845 26-12-2012 http://www.couchbase.com/issues/browse/SPY-85 Spymemcached Java Client In <a href="http://www.couchbase.com/issues/browse/SPY-58" title="JSON documents can be inadvertently compressed"><strike>SPY-58</strike></a> compressing for JSON was disabled. We picked spymemcached because it did compression and couldn&#39;t find any documentation saying JSON wouldn&#39;t be compressed. Whether to compress JSON or not should be a configuration value that can be passed in much like compressionThreshold. <br/> <br/> Currently our only solution appears to prepend one character that isn&#39;t { or [ and then remove it after doing a get. But I would say that not compressing any string just because it starts with a { or [ isn&#39;t really desirable because it means that if I expect/want compression of my string I now have to check every string I put into the client and prepend and remove a leading character just to get compression. SPY-85

JSON documents can't be compressed

Bug Major Open Unresolved Public Michael Nitschinger Joshua Shanks Fri, 6 Apr 2012 13:24:51 -0500 Thu, 15 Nov 2012 19:47:56 -0600 2.8.1 library 1 2 We&#39;ll agree that it was probably not the best solution. We need to find a better approach for this. One strong consideration is enhancing flags, allowing compression and doing compression at both the client and the server. That requires more help from the server folks. The other challenge here is that there is no standard JSON type and even if there were, we&#39;d not likely want to key off of it. <br/> <br/> To address this for now, maybe it&#39;d be best to have a way to disable this behavior? Agreed some kind of configuration would be great. As someone who is using the client with a standard memcached server I think ideally the default would be to compress everything but as long as it was configurable and documented it&#39;d be a step in the right direction. I was going to look at making it a configuration option but can&#39;t get all of the unit tests to run, maybe I can try again if <a href="http://www.couchbase.com/issues/browse/SPY-86" title="Test failures in HEAD of master">SPY-86</a> get resolved. Lowering priority because this needs server side planning as well Rank 9520