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

LookupIn should re-order subdoc requests so that XATTRs come first.

    XMLWordPrintable

Details

    • Task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 3.0.2
    • 3.0.3
    • None
    • None
    • 1

    Description

      Currently, if a user issues a LookupIn request with XATTR values after non-XATTR values, an exception explaining that XATTRs must come first is propagated to the user.

      Per the RFC: (https://docs.google.com/document/d/1_fPJn9trqG6e7iTpzqwCnurvxmBlguFVjh00F2Co7Y8/edit#heading=h.iurhbf52si1i)

      The server requires that all Xattr operations must come before any regular operations when sent to the server; however, when the results are returned from the server the previous order specified by the User must be returned so that ContentAs(int index) can be used to fetch the correct result. A data structure may be used internally to “remember” this ordering.

      Therefore, the SDK should re-order the request before sending them to the server, and restore the order of the results for the user.

      Attachments

        Issue Links

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

          Activity

            There are no comments yet on this issue.

            People

              richard.ponton Richard Ponton
              richard.ponton Richard Ponton
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty