[RCBC-102] Store methods behaves inconsistently when persistence constraints specified Created: 15/Dec/12  Updated: 08/Feb/13  Resolved: 15/Dec/12

Status: Closed
Project: Couchbase Ruby client library
Component/s: None
Affects Version/s: 1.2.0
Fix Version/s: 1.2.1
Security Level: Public

Type: Bug Priority: Major
Reporter: Sergey Avseyev Assignee: Sergey Avseyev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

  1.9.3p327 (main):002:0> conn.set("foo", "bar")
  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})

Comment by Sergey Avseyev [ 15/Dec/12 ]
Comment by Matt Ingenthron [ 15/Dec/12 ]
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.
Generated at Thu Dec 18 08:34:30 CST 2014 using JIRA 5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9.