[ZEPPELIN-2790] Storing Notebooks and Configs on database

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Herval Freire
• Created: 17/Jul/17 21:38
• Updated: 29/Aug/18 22:45

Description

At Twitter, we run mostly all of our services following the 12-factor approach (https://12factor.net/). Zeppelin is one of the few exceptions we can't really containerize, since:

• it stores notebook data on local disk
• it stores configuration on disk

One option we considered is migrating the whole thing to git (with remote pushes). The issue, then, becomes concurrency. So the saner option we're left with is using a database backend to store that information. In the interest of time to build / easier compatibility with the JSON mode, what we're considering is basically storing some metadata + a JSON "blob" on your database of choice (configurable w/ jdbc driver).

We didn't start commiting resources to building this yet - I'd like to probe the opensource community's interest on this, as well as any remarks, suggestions or no-gos you'd have in mind.

Please advise!

Issue Links

• relates to: ZEPPELIN-2742 Unify Zeppelin's Config Storage