geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jinmei Liao <>
Subject [DISCUSS] consistency of command result status
Date Wed, 08 Nov 2017 21:48:03 GMT
We noticed some discrepancies of result status when executing commands that
involves looking for a member/region/entry/gateway receiver/sender, namely
any entities. If the command failed to find the entity specified by the
command, it will output some messages like "xxx not found", but some
command would report this message as ERROR result and others would report
this as OK result. For example:

gfsh>describe region --name=notExist

Region : /notExist not found

gfsh>describe member --name=notExist

Member "notExist" not found

The first command will show as ERROR status (in red), while the second
command shows up as OK status (in black). We would like to propose changing
these kind of "not found" messages as all ERROR (user error) status. This
would involve some test changes as well.




  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message