Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Historical Disk Usage Report - date format in excel/csv

avatar
Contributor

Hello -

When I view the Historical Disk Usage report in CM for daily or weekly or monthly, the values displayed look like dates:    2017-02  or 2017-05-02.

 

However, when I download the report to excel or csv, the date column has values like:   1491020099000

 

Just wondering what that format is and how i can covert back to a date.

 

thanks

1 ACCEPTED SOLUTION

avatar
Contributor

Hi all ...

 

According to Cloudera support the date value

  "...is an epoch timestamp includes milliseconds, which makes the the timestamp three digits longer than the date converter expects. You can either remove the last three characters using a substring function, or insert a period before the millisecond digits. Either of these commands will provide the correct timestamp for 1491020099000: date --date='@1491020099' date --date='@1491020099.000'"

 

So...if anyone else needs to know!

 

...douglas

View solution in original post

1 REPLY 1

avatar
Contributor

Hi all ...

 

According to Cloudera support the date value

  "...is an epoch timestamp includes milliseconds, which makes the the timestamp three digits longer than the date converter expects. You can either remove the last three characters using a substring function, or insert a period before the millisecond digits. Either of these commands will provide the correct timestamp for 1491020099000: date --date='@1491020099' date --date='@1491020099.000'"

 

So...if anyone else needs to know!

 

...douglas