Uploaded image for project: 'Couchbase .NET client library'
  1. Couchbase .NET client library
  2. NCBC-1843

In LookupIn last command is not always parsed correctly

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.7.4
    • Fix Version/s: 2.7.5
    • Component/s: library
    • Labels:
      None

      Description

      Given code the following code where the document "Lookupin_test" does not contain a field "hack-to-fix-last-always-1", the status of -1 is returned instead of the proper missing field status:

      var key = "LookupIn_test";
      var lookupInBuilder = bucket.LookupIn<dynamic>(key);
      lookupInBuilder.Get("click");
      lookupInBuilder.Get("with JSON");
      lookupInBuilder.Exists("hack-to-fix-last-always-1");//will result in MISSING_PATH
      var result = lookupInBuilder.Execute(); 

      The Message field is correct, but the response status for the field is not because an internal parsing error keeps the response status from being set.

        Attachments

        For Gerrit Dashboard: NCBC-1843
        # Subject Branch Project Status CR V

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              jmorris Jeff Morris
              Reporter:
              jmorris Jeff Morris
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Gerrit Reviews

                There are no open Gerrit changes

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.