Feature Request : A Status Code to indicate Success or Failure (instead of just errorCode in event of failure)

[conikeec]

In event of a network failure, an insert into etcd might fail, but an external process might query of an non-existent key for variety of reasons.

Non-existent keys send a distinct failed message:

{"errorCode":100,"message":"Key Not Found","cause":"/D0A1A866-6591-40CF-99EE-15AE1BF3A7F1"}

Successful value fetch from key does not hold a statusCode at this point

[{"action":"GET","key":"/51b8cc7c-c7d8-4d6e-86ee-1a381db2f068/status","value":"COMPLETED","expiration":"2013-08-11T06:04:23.647167583-07:00","ttl":29849,"index":97}]

Is it possible to add an upper level 'statusCode' to indicate success or failure instead of just passing errorCode on event of a failure?

Client(s) can then use the statusCode to make deterministic logic flow.

[xiang90]

@conikeec Http status code is different. Is it enough for your usage?

[conikeec]

I am currently using HTTP codes the terminate flow.
Was wondering if it might be ideal to tack on a statusCode on successful returns as well?
Thoughts?

[xiang90]

@conikeec
The current work flow of etcd is
query store -> generate response
if response is not null, return response and http 200
or generate error message and http fail code.

First, I feel return response status code is a little bit duplicate with http status code.
Second if we use {statusCode: <code> {error json/ response json} }, we need to decode twice.

[conikeec]

Got it .. Agree with you ...
Thanks for clarifying.
Please close ...

[xiang90]

@conikeec If you have any questions, just open an issue. PR and issues are always welcomed.