Hi, If you see NotebookRepo [1], which is notebook storage layer abstraction in Zeppelin, you'll find there's actually no limitations on how Note is stored.
i.e. Underlying storage system (file, db, etc), How they structured (directory, filename, rows in db, etc), Format of Note (json, etc), all they're actually depends on NotebookRepo implementation. So if any NotebookRepo implementation can be reconfigured on the fly, then user can just click refresh notebook button to load new notebook. Zeppelin doesn't provide any facilities to reconfigure NotebookRepo on the fly at the moment. Therefore either improve Zeppelin and make some way to reconfigure NotebookRepo (like reconfiguring Interpreter), or NotebookRepo implementation have it's own way of reconfiguring (monitor a configuration file, and so on) Hope this helps. Thanks, moon [1] https://github.com/apache/zeppelin/blob/master/zeppelin-zengine/src/main/java/org/apache/zeppelin/notebook/repo/NotebookRepo.java On Thu, Sep 22, 2016 at 12:28 PM Ian Maloney <rachmaninovquar...@gmail.com> wrote: > > Hi, > > We're looking into using Zeppelin for some of our projects. I've noticed > that the way the directories are setup, is not conducive to version control > for multiple projects. > > Is it on the roadmap for Zeppelin to have the ability to utilize > subdirectories and persist them on disk as opposed to just a list of all > notebooks by their IDs? > > Is there a way to point Zeppelin to a new directory of notebooks without > stopping the instance and editing a shell script? > >
