Alok created ZEPPELIN-3872:
------------------------------
Summary: Notebook REST API should return timestamp related
information in UTC or Unix Epoch
Key: ZEPPELIN-3872
URL: https://issues.apache.org/jira/browse/ZEPPELIN-3872
Project: Zeppelin
Issue Type: Bug
Components: rest-api
Reporter: Alok
Fix For: 0.7.4, 0.8.1
Notebook related REST APIs return timestamp information in local timezone.
(i.e. timezone of the host machine running the zeppelin server where the
notebook's session is active).
[https://zeppelin.apache.org/docs/0.7.0/rest-api/rest-notebook.html]
Timestamp information in the return payload of most of the GET APIs is all
local time.
Example -
# [http://[zeppelin-server]:[zeppelin-port]/api/notebook/[noteId]
|http://[zeppelin-server][zeppelin-port]/]"dateCreated": "Feb 10, 2015 1:53:02
AM", "dateStarted": "Jul 3, 2015 1:43:17 PM", "dateFinished": "Jul 3, 2015
1:43:23 PM", "dateUpdated": "Jul 2, 2015 1:43:23 PM"
#
[http://[zeppelin-server]:[zeppelin-port]/api/notebook/[noteId]/paragraph/[paragraphId]
|http://[zeppelin-server][zeppelin-port]/]"dateUpdated": "Jul 2, 2015 1:43:23
PM"
Any consumer of the Rest APIs has no way to know how to interpret this
timestamp information since it is purely local time information of the Zeppelin
host. There is no mention of a timezone - that would have allowed the consumer
to possibly interpret the timestamp in whatever timezone it needs.
The correct and industry standard way to do this would be to return the
timestamp information for all the Zeppelin Notebook Rest APIs as either
# *UTC time*
or
# *Unix EPOCH time* (in milliseconds)
This allows consumers to easily interpret the timestamp information and convert
it to whatever timezone they need it in.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
