Inconsistent behavior when handling various error states

[MartinPodval]

This topic https://github.com/coreos/etcd/blob/master/Documentation/errorcode.md defines a set of possible error codes which can etcd server return to your request. The server returns both http status code and json body as well. The server does it even in error states.

On the other hand EtcdKeyResponseHandler parses only some http status codes into EtcdException body.

This means that when I send a request to get not existing key, the etcd client returns EtcdException with error code 101. Contrary to this behavior, when I send a request using prevExist=false and the request fails, a new Exception is thrown containing message "412 Precondition Failed". I need to parse the text using HttpResponseStatus.parseLine in this case to discover what happen.

I would suggest to throw an EtcdException with proper error code in all cases when possible.

[jurmous]

You are right. It also seems that newer etcds respond with some different http codes in some situations. I will adapt code to always try to make an etcd exception.

[jurmous]

Released in 2.2.0. Thanks for reporting the issue in!