"Key Not Found" error removed in v3

[Gunakk]

HI there,

I installed etcd v2 and etcd v3.4.0. Did etcdctl get for a non existing key in both. Got "Key not found" error in v2 and but, in v3 there isn't any response. May I know why this change was introduced ?

Thanks,
Guna

[ptabor]

I don't know, but I would guess the motivation was to allow safer usage in scripting, like:

MY_KEY=$(etcdctl get mykey)

But, personally I would expect at least exit_code ~= 0 if no key matching the requirements was found.

@xiang90 What do you think about such contribution to: https://github.com/etcd-io/etcd/blob/master/etcdctl/ctlv3/command/get_command.go ? For backward compatibility it would need to be an opt-in flag.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions.

[xiang90]

But, personally I would expect at least exit_code ~= 0 if no key matching the requirements was found.

This should be better.

The motivation is to keep the stdout clean and consistent. So we do not print out "key not found" to stdout anymore in v3.

[ptabor]

Thank you @xiang90.
BTW: I approved similar (error-code) related contribution in: #12829

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions.