Github user astroshim commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/972
@cloverhearts Thank you for your explanation. You mean that the
"LastResponseUnixTime" is for getting notebook information of lastest updated.
---
If your project is set up for it,
Github user cloverhearts commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/972
Updated text for test scenario.
@astroshim
lastResponseUnixTime value is update data area key.
to query the Future updates based on LastResponseUnixTime value,
Github user cloverhearts commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/972
@astroshim
http://127.0.0.1:8080/api/notebook/jobmanager/(get unixtime at before step)
for example
http://127.0.0.1:8080/api/notebook/jobmanager/
(get
Github user astroshim commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/972
It's working nicely.
but Is the correct behavior that the lastResponseUnixTime is increased
whenever call the curl?
Then i can't understand what's the purpose of step 3. Could
Github user cloverhearts commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/972
Update text for 'How should this be tested' and add json data comment.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user cloverhearts commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/972
@jongyoul I've changed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
