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)

Chiyoung Seo added a comment - 01/Nov/12 12:40 AM Farshid, Please assign this bug to the view or UI team. ep-engine has nothing to do with view and its UI.

Farshid Ghods added a comment - 01/Nov/12 12:44 AM Perry, can you please specify whether the document was an ascii or a binary data ?

Perry Krug added a comment - 01/Nov/12 4:32 AM Ascii. I tried both a few characters in string and a single integer value (as if it were an increment counter value). 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. I'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. Let me know if you need more specific reproduction details.

Deepkaran Salooja added a comment - 01/Nov/12 11:06 AM Anything which doesn'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. 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 MB-6961 for detailed discussion. For normal strings, these will get displayed as binary(screenshot-StringAsNonJson).

Farshid Ghods added a comment - 01/Nov/12 11:15 AM resolving this as won't fix since this is an expected behavior as mentioned in the last comment the fix for this would be to reverse the base64 coding ?

Farshid Ghods added a comment - 01/Nov/12 11:18 AM for 2.0 i marked this to be documented since our documented editing section is not meant for non-json values ( e.g http://www.couchbase.com/issues/browse/MB-7031)

Perry Krug added a comment - 01/Nov/12 11:23 AM 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? Thanks Farshid

Farshid Ghods added a comment - 01/Nov/12 11:29 AM >>.but this is already fixed in a later release viewing non-json values on document editing page is not supported or expected behavior. however as Deep mentioned a corner case is fixed in MB-6961 once 7031 is merged ( before 2.0 GA ) user will see a better error message when document is non-json so for 2.0 GA we need to document that this behavior is not supported and expected.

Perry Krug added a comment - 01/Nov/12 11:43 AM 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'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? Obviously document it for whenever we can't, but I think Dipti needs to decide how to address it.

MC Brown added a comment - 05/Nov/12 11:15 AM Note has been added to the corresponding section of the docs,and to the release notes.

Perry Krug added a comment - 05/Nov/12 11:52 AM Reopening as it's still not clear whether this is something we want to support or not...and I argue that we should.

Dipti Borkar added a comment - 06/Nov/12 2:34 AM The UI does not handle BLOB data very well. Data access using the APIs for BLOBs is completely supported and works well.

Karen Zeller added a comment - 27/Mar/13 1:27 PM Removing docs tag, additional server work required. Reassign when ready to document post-resolution.