Github user kjmrknsn commented on the issue:
https://github.com/apache/zeppelin/pull/2676
@felixcheung @Leemoonsoo
Then, how about the following solution which fixes this and #2671 together?
* Add the `zeppelin.notebook.cron.secure` property to Zeppelin
Configuration.
* If `zeppelin.notebook.cron.secure` is set to `true`,
* A cron executing user cannot be set to other users than the login user
* If a cron schedule is set to a notebook, its owners and writers are
demoted to runners and the login user becomes its owner and writer.
---
