Create and edit notebooks
Right-click any notebook in the Big Data Tools window to open the context menu for the basic operations with the notebook. You can also use the following shortcuts:
|Move to trash||Delete|
You can create a new notebook on the target server (remote notebook) or in the current DataGrip project (local notebook).
Create a remote notebook
In the Big Data Tools window, right-click any of the configured servers or a folder and select from the context menu or press Alt+Insert.
In the Create note dialog, enter the name of the notebook. You can use the
/symbol to create a notebook within a folder. Click OK.
The newly added notebook appears in the Big Data Tools window.
In DataGrip, you can create notebooks that are stored locally.
Create a local notebook
In the Project tool window, select the project root, press Alt+Insert, and select Zeppelin Notebook.
In the Create Zeppelin Notebook dialog, enter the notebook name and press Enter.
The newly added local notebook appears in the Project tool window.
Once you create a notebook, it opens in the editor. The newly added notebook has one executable paragraph marked with the
sql next the delimiter to enable SQL coding.
Press Enter and start editing your notebook right away.
Any time you need to add more paragraphs or delete the current paragraph, just press Alt+Enter and select the required action:
You are not limited to adding only SQL code paragraphs. For example, to add any markdown code, just add
md right after the delimiter.
Note, that you don't need to save your edits. Auto-saving is triggered by various events, for example, closing a notebook or a project, or quitting the IDE.
Manage interpreter bindings
Once you have added code to your notebook, you're ready to execute it and analyze the data. However, you can customize the interpreters used to execute paragraphs by the target server.
On the notebook editor toolbar, click .
In the Interpreter Bindings dialog, use the arrow buttons to alter the priority of an interpreter. You can also deselect an interpreter and explicitly disable it or restart any interpreter when, for example, the corresponding session got expired.