Couchbase Server

Better error responses for append/prepend "not stored"

Details

  • Type: Technical task Technical task
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.8.1
  • Fix Version/s: 2.1
  • Component/s: couchbase-bucket
  • Security Level: Public
  • Labels:
    None

Description

At the moment, the server only responds with "not stored" to append/prepend operations for multiple possible reasons:
-The item was over 20mb
-The item didn't exist
-others?

It would be very helpful to our users to have these split out with separate error messages. For instance, incr/decr respond with "not found" as opposed to "not stored" when the item doesn't exist, and set operations return with "value too large" when it is over 20mb.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Mike Wiederhold added a comment -
We can add some better messages for given error codes, but at the end of the day it is up to the clients to display these and users to ask for them. I know capability is available in the java sdk, but I doubt it is in many of our other clients.
Show
Mike Wiederhold added a comment - We can add some better messages for given error codes, but at the end of the day it is up to the clients to display these and users to ask for them. I know capability is available in the java sdk, but I doubt it is in many of our other clients.
Hide
Permalink
Matt Ingenthron added a comment -
Actually, it is more likely in the scripting ones, such as PHP and Ruby. They're a bit more freeform. I'm not sure about .NET, but I've added John as a watcher here.

John, can you comment?
Show
Matt Ingenthron added a comment - Actually, it is more likely in the scripting ones, such as PHP and Ruby. They're a bit more freeform. I'm not sure about .NET, but I've added John as a watcher here. John, can you comment?
Hide
Permalink
John Zablocki added a comment -
The .NET client is echoing back the status codes/messages, so if the server response changed, so should the client's handling of it.
Show
John Zablocki added a comment - The .NET client is echoing back the status codes/messages, so if the server response changed, so should the client's handling of it.
Hide
Permalink
Mike Wiederhold added a comment -
This stuff needs to be taken care of in memcached and that poses an issue because memcached receives an error code that could have multiple meanings.
Show
Mike Wiederhold added a comment - This stuff needs to be taken care of in memcached and that poses an issue because memcached receives an error code that could have multiple meanings.
Hide
Permalink
Trond Norbye added a comment -
Mike: it is the error code returned from the engine that is returned back to the caller (it goes through the same codepath as set/add/replace/cas etc). Given that this method is implemented inside ep-engine it may return the appropriate error message back. Do you still want me to look at it?
Show
Trond Norbye added a comment - Mike: it is the error code returned from the engine that is returned back to the caller (it goes through the same codepath as set/add/replace/cas etc). Given that this method is implemented inside ep-engine it may return the appropriate error message back. Do you still want me to look at it?

People

  • Assignee:
    Mike Wiederhold
    Reporter:
    Perry Krug
Vote (0)
Watch (2)

Dates

  • Created:
    Updated: