Github user khalidhuseynov commented on the issue:
https://github.com/apache/zeppelin/pull/2374
@zjffdu the persistence policy is saving on run and almost on any note
action. originally i introduced this feature globally on base class, however
after some discussion above, introducing it for certain classes seems to be
more reasonable since remote saves are costlier than local ones. regarding the
questions:
* when it's set to false there's only `Commit` button as before (make
revision) instead of `Save & Commit` (save and make revision) as below
* yeah i agree that `commit` itself implies save. currently it's used in
Zeppelin to denote creation of revision/checkpoint. So the idea was that in
normal mode everything is saved automatically and you can `commit` current
version whenever you want and with this feature enabled (only in S3 and
ZHubRepo for now) you can `Save & Commit`.
* persist on run is also another idea that could work, and would be nice to
know opinion of more people on that. generally in that case save would be
dependent on run, and `commit` would stay as before. @1ambda @Leemoonsoo what
do you think about that?
* i'll add documentation for it, regarding losing data since i changed
local storage not to have this feature, it'll alway be saved locally and only
for remote storages it could be mentioned in docs.
let me know what you think on these points, thanks
---
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
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
