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
-
Flagged:Release Note
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}
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}
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.