Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. 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)

    Details

    • Type: Improvement
    • Status: Reopened
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0
    • Fix Version/s: feature-backlog
    • Component/s: ns_server
    • Security Level: Public
    • Labels:
      None

      Description

      Reproduction:
      -Set a key with some non-JSON value
      -View that key through the document viewer in the UI
      -See that the value does not match what was just set

      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's quite confusing for the user to not be able to see what they thought was simple string data.

      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...

      No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

        Hide
        dipti Dipti Borkar added a comment -

        The UI does not handle BLOB data very well. Data access using the APIs for BLOBs is completely supported and works well.

        Show
        dipti Dipti Borkar added a comment - The UI does not handle BLOB data very well. Data access using the APIs for BLOBs is completely supported and works well.
        Hide
        kzeller kzeller added a comment -

        Removing docs tag, additional server work required. Reassign when ready to document post-resolution.

        Show
        kzeller kzeller added a comment - Removing docs tag, additional server work required. Reassign when ready to document post-resolution.
        Hide
        alkondratenko Aleksey Kondratenko (Inactive) added a comment -

        As discussed I'm not seeing any sensible way to support arbitrary values and don't think it's worth trying to.

        Show
        alkondratenko Aleksey Kondratenko (Inactive) added a comment - As discussed I'm not seeing any sensible way to support arbitrary values and don't think it's worth trying to.
        Hide
        perry Perry Krug added a comment -

        This does come up on a fairly regular basis, especially since we do advocate using strings and integers within our documents (as non-JSON) and yet we don't display them properly in the UI. Could we just do a base64 decode on the value and display whatever returns from that?

        Show
        perry Perry Krug added a comment - This does come up on a fairly regular basis, especially since we do advocate using strings and integers within our documents (as non-JSON) and yet we don't display them properly in the UI. Could we just do a base64 decode on the value and display whatever returns from that?
        Hide
        alkondratenko Aleksey Kondratenko (Inactive) added a comment -

        If you want specifically to support strings and integers then please ask specifically for that. And work with Anil on spec.

        Show
        alkondratenko Aleksey Kondratenko (Inactive) added a comment - If you want specifically to support strings and integers then please ask specifically for that. And work with Anil on spec.

          People

          • Assignee:
            anil Anil Kumar
            Reporter:
            perry Perry Krug
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:

              Gerrit Reviews

              There are no open Gerrit changes