Re: Non-Uniform opErrstr output in all gluster --xml commands

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 08/05/2015 02:58 PM, Avra Sengupta wrote:
> Hi,
> 
> As reported in https://bugzilla.redhat.com/show_bug.cgi?id=1218732, in
> the event where there is no opErrstr, some gluster commands'(like
> snapshot status, volume status etc.) xml output shows
> "<opErrstr>(null)</opErrstr>", while other commands show just
> "<opErrstr/>". This non-uniform output is troublesome for people who
> parse this.
> 
> IMHO showing "<opErrstr>(null)</opErrstr>" is much more descriptive. I
> would like to propose making sure all commands follow this uniform
> approach, instead of displaying just "<opErrstr/>".
Makes sense to me as long as its uniform. However the existing ones
which follow "<opErrstr/>" need change in parsing logic :(
> 
> Regards,
> Avra
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel@xxxxxxxxxxx
> http://www.gluster.org/mailman/listinfo/gluster-devel

-- 
~Atin
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel



[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux