You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by GitBox <gi...@apache.org> on 2020/03/10 11:55:40 UTC

[GitHub] [hadoop-ozone] elek commented on issue #618: HDDS-2911. Fix lastUsed and stateEnterTime value in container info is not human friendly

elek commented on issue #618: HDDS-2911. Fix lastUsed and stateEnterTime value in container info is not human friendly
URL: https://github.com/apache/hadoop-ozone/pull/618#issuecomment-597047183
 
 
   > In this case, can we display it as string in CLI ouput, and keep the long value internally.
   
   +1 It seems to be to more flexible option. Keep the long value for protobuf (we can keep even the nanosec) but print out in a human readable form...
   
   We can also change the Java type (and not the protobuf type) to a proper java8 Time object (like `Instant`). That is more meaningful and might be printed out properly by the current default JSON serializer...

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org