Uploaded image for project: 'Couchbase Ruby client library'
  1. Couchbase Ruby client library
  2. RCBC-102

Store methods behaves inconsistently when persistence constraints specified

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.2.0
    • Fix Version/s: 1.2.1
    • Component/s: None
    • Security Level: Public
    • Labels:
      None

      Description

      The Bucket#set for example should return the object corresponding to arguments passed:

      1.9.3p327 (main):002:0> conn.set("foo", "bar")
      851339802448297984
      1.9.3p327 (main):003:0> conn.set("foo" => "bar", "baz" => "foo")

      {"foo"=>2995536636664938496, "baz"=>16831440216388861952}

      But when :observe option is used, it always return it like for multi-set

      1.9.3p327 (main):004:0> conn.set("foo", "bar", :observe => {:persisted => 1})

      {"foo"=>2559248876759744512}
      No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

        avsej Sergey Avseyev created issue -
        Show
        avsej Sergey Avseyev added a comment - http://review.couchbase.org/23336
        avsej Sergey Avseyev made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Fix Version/s 1.2.1 [ 10450 ]
        Resolution Fixed [ 1 ]
        Hide
        ingenthr Matt Ingenthron added a comment -

        that does seem to be an issue

        you're a better judge than I am, but I'd think we'd want the response to be the same whether or not using the :observe

        If the change makes it more consistent, then yes it's an API change from 1.2.0 but it's really getting back to what we expect so perfectly acceptable. Definitely something to release note though.

        Show
        ingenthr Matt Ingenthron added a comment - that does seem to be an issue you're a better judge than I am, but I'd think we'd want the response to be the same whether or not using the :observe If the change makes it more consistent, then yes it's an API change from 1.2.0 but it's really getting back to what we expect so perfectly acceptable. Definitely something to release note though.
        ingenthr Matt Ingenthron made changes -
        Flagged [Release Note]
        avsej Sergey Avseyev made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        brett19 Brett Lawson made changes -
        Workflow jira [ 23197 ] Couchbase SDK Workflow [ 44888 ]

          People

          • Assignee:
            avsej Sergey Avseyev
            Reporter:
            avsej Sergey Avseyev
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes