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/MB-7069 Couchbase Server Reproduction: <br/> -Set a key with some non-JSON value <br/> -View that key through the document viewer in the UI <br/> -See that the value does not match what was just set <br/> <br/> I presume this is because we are compressing the data at the disk level and then reading that binary attachment back when viewing through the UI...but it&#39;s quite confusing for the user to not be able to see what they thought was simple string data. <br/> <br/> Does this at all affect views of non-JSON (i.e., increment counters)? Even in the random doc preview, this data does not come across correctly... MB-7069

Fix UI to support Non-JSON values ( was: Non-JSON values which are not integers show up as base-64 encoded when viewed through the UI document viewer)

Improvement Major Reopened Unresolved Public Aleksey Kondratenko Perry Krug 2.0-release-notes customer Wed, 31 Oct 2012 19:17:50 -0500 Wed, 27 Mar 2013 13:27:54 -0500 2.0 .next ns_server 0 2 Farshid,<br/> <br/> Please assign this bug to the view or UI team. ep-engine has nothing to do with view and its UI. Perry, <br/> <br/> can you please specify whether the document was an ascii or a binary data ? Ascii. I tried both a few characters in string and a single integer value (as if it were an increment counter value). <br/> <br/> This came up from a customer who created a CSV list and wanted to view it through the UI as well as design a view around it. <br/> <br/> I&#39;m fairly certain the problem is that this mechanism for viewing documents is coming directly from the on-disk datastore (as opposed to through memcached) and therefore it is compressed binary and not exactly what the application put in. <br/> <br/> Let me know if you need more specific reproduction details. Anything which doesn&#39;t parse as valid json are encoded as base64 and stored as an attachment. In the UI for document viewer these get displayed as binary. <br/> There was a recent bug fix for the increment counter values. So string integers will show up fine as they now parse as valid JSONs(screenshot attached-StringNumbersAsValidJson). Please see <a href="http://www.couchbase.com/issues/browse/MB-6961" title="result of INCR operations should show up in views as JSON number, not base64 string"><strike>MB-6961</strike></a> for detailed discussion. <br/> For normal strings, these will get displayed as binary(screenshot-StringAsNonJson). resolving this as won&#39;t fix since this is an expected behavior as mentioned in the last comment <br/> <br/> the fix for this would be to reverse the base64 coding ? <br/> for 2.0 i marked this to be documented since our documented editing section is not meant for non-json values ( e.g <a href="http://www.couchbase.com/issues/browse/MB-7031)">http://www.couchbase.com/issues/browse/MB-7031)</a> Sorry if it should be obvious...but this is already fixed in a later release and so just have to document for the beta? Or is it planned for this never to be supported? <br/> <br/> Thanks Farshid &gt;&gt;.but this is already fixed in a later release <br/> viewing non-json values on document editing page is not supported or expected behavior. <br/> however as Deep mentioned a corner case is fixed in <a href="http://www.couchbase.com/issues/browse/MB-6961" title="result of INCR operations should show up in views as JSON number, not base64 string"><strike>MB-6961</strike></a> <br/> <br/> once 7031 is merged ( before 2.0 GA ) user will see a better error message when document is non-json <br/> <br/> so for 2.0 GA we need to document that this behavior is not supported and expected. <br/> <br/> Okay, I might need to question that a little bit...how is a user supposed to write a view around a non-JSON (i.e. an incremement counter or CSV) if they can&#39;t see it in the document viewer? Writing such views is supposed to be supported right? Seems like this would have to be as well? <br/> <br/> Obviously document it for whenever we can&#39;t, but I think Dipti needs to decide how to address it. Note has been added to the corresponding section of the docs,and to the release notes. Reopening as it&#39;s still not clear whether this is something we want to support or not...and I argue that we should. The UI does not handle BLOB data very well. Data access using the APIs for BLOBs is completely supported and works well. Removing docs tag, additional server work required. Reassign when ready to document post-resolution. Date of First Response Thu, 1 Nov 2012 00:40:46 -0500 Rank 2852