mirror of
https://github.com/apache/zeppelin
synced 2026-05-24 09:38:26 +00:00
### What is this PR for? As more and more document pages are added, it's really hard to find specific pages. So I added searching feature to Zeppelin documentation site([jekyll](https://jekyllrb.com/) based site) using [lunr.js](http://lunrjs.com/). - **How does it work?** I created [`search_data.json`](6e02423f54/docs/search_data.json) which is used for docs info template. `lunr.js` combines all of the text from all of the docs in `docs/` into `_site/search_data.json`. It looks like below.  All the info are comes from [Jekyll YAML front matter](https://jekyllrb.com/docs/frontmatter/) variables. (i.e. title, group, description.. that's why I rewrote all docs' title and description.) [search.js](6e02423f54/docs/assets/themes/zeppelin/js/search.js) will do this job using this data! ### What type of PR is it? Improvement & Feature ### Todos * [x] - Keep consistency for all docs pages' `Title` * [x] - Add some overview sentences to all docs pages' `Description` section (this will be used as the result preview) * [x] - Add apache license header to all docs page (some pages are missing the license header currently) * [x] - Add LICENSE for `lunr.min.js` ### What is the Jira issue? [ZEPPELIN-1219](https://issues.apache.org/jira/browse/ZEPPELIN-1219) ### How should this be tested? 1. Apply this patch and build `ZEPPELIN_HOME/docs` dir -> please see [docs/README.md#build-documentation](https://github.com/apache/zeppelin/tree/master/docs#build-documentation) 2. Click `search` icon in navbar and go to `search.html` page 3. Type anything you want to search in the search bar (i.e. type `python`, `spark`, `dynamic` ... ) ### Screenshots (if appropriate)   ### Questions: * Does the licenses files need update? Yes, for `lunr.min.js` * Is there breaking changes for older versions? no * Does this needs documentation? no Author: AhyoungRyu <fbdkdud93@hanmail.net> Closes #1266 from AhyoungRyu/ZEPPELIN-1219 and squashes the following commits:7ec8854[AhyoungRyu] Modify 'no result' sentence91b71a7[AhyoungRyu] Remove Apache license header since JSON doesn't allow comment34afd5d[AhyoungRyu] Add Apache license header to search_data.json6784282[AhyoungRyu] Minor search page UI update0389d28[AhyoungRyu] Make index.md not to be searched9f1ba42[AhyoungRyu] Disable enterkey press & change iconbd4956a[AhyoungRyu] Add docs.js & search.js to exclude list in pom.xml624b051[AhyoungRyu] Add Apache license header to search.js1381152[AhyoungRyu] Fix search result skipping issue6e775f5[AhyoungRyu] Make pleasecontribute.md not to be searchedee11136[AhyoungRyu] Fix some typosfa01299[AhyoungRyu] Refine 'description' in some docs as @bzz suggestedda0cff9[AhyoungRyu] Exclude lunr.min.js36ba7f1[AhyoungRyu] Add lunr.min.js license infof6a05a6[AhyoungRyu] Apply css style for the search results68eb997[AhyoungRyu] Attach 'Apache Zeppelin ZEPPELIN_VERSION Documentation: ' to titled908c37[AhyoungRyu] Add searching pagea951fa6[AhyoungRyu] Add search icon to navbar0688a79[AhyoungRyu] Keep consistency all docs' front matter for the right search result040f532[AhyoungRyu] Add template for storing docs info based on jekyll front matter0705bd6[AhyoungRyu] Add js files: lunr.min.js & search.js
160 lines
5.9 KiB
Markdown
160 lines
5.9 KiB
Markdown
---
|
|
layout: page
|
|
title: "Explore Apache Zeppelin UI"
|
|
description: "If you are new to Apache Zeppelin, this document will guide you about the basic components of Zeppelin one by one."
|
|
group: quickstart
|
|
---
|
|
<!--
|
|
Licensed under the Apache License, Version 2.0 (the "License");
|
|
you may not use this file except in compliance with the License.
|
|
You may obtain a copy of the License at
|
|
|
|
http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
Unless required by applicable law or agreed to in writing, software
|
|
distributed under the License is distributed on an "AS IS" BASIS,
|
|
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
See the License for the specific language governing permissions and
|
|
limitations under the License.
|
|
-->
|
|
{% include JB/setup %}
|
|
|
|
# Explore Apache Zeppelin UI
|
|
|
|
<div id="toc"></div>
|
|
|
|
## Main home
|
|
|
|
The first time you connect to Zeppelin, you'll land at the main page similar to the below screen capture.
|
|
|
|
<img src="../assets/themes/zeppelin/img/ui-img/homepage.png" />
|
|
|
|
On the left of the page are listed all existing notes. Those notes are stored by default in the `$ZEPPELIN_HOME/notebook` folder.
|
|
|
|
You can filter them by name using the input text form. You can also create a new note, refresh the list of existing notes
|
|
(in case you manually copy them into the `$ZEPPELIN_HOME/notebook` folder) and import a note.
|
|
|
|
<img src="../assets/themes/zeppelin/img/ui-img/notes_management.png" width="230px" />
|
|
|
|
When clicking on `Import Note` link, a new dialog open. From there you can import your note from local disk or from a remote location
|
|
if you provide the URL.
|
|
|
|
<img src="../assets/themes/zeppelin/img/ui-img/note_import_dialog.png" />
|
|
|
|
By default, the name of the imported note is the same as the original note but you can override it by providing a new name.
|
|
|
|
<br />
|
|
## Menus
|
|
|
|
### Notebook
|
|
|
|
The `Notebook` menu proposes almost the same features as the note management section in the home page. From the drop-down menu you can:
|
|
|
|
1. Open a selected note
|
|
2. Filter node by name
|
|
3. Create a new note
|
|
|
|
<img src="../assets/themes/zeppelin/img/ui-img/notebook_menu.png" width="170px" />
|
|
|
|
### Settings
|
|
This menu gives you access to settings and displays information about Zeppelin. User name is set to `anonymous` if you use default shiro configuration. If you want to set up authentification, see [Shiro authentication](../security/shiroauthentication.html).
|
|
|
|
<img src="../assets/themes/zeppelin/img/ui-img/settings_menu.png" width="170px" />
|
|
|
|
|
|
#### About Zeppelin
|
|
|
|
You can check Zeppelin version in this menu.
|
|
|
|
<img src="../assets/themes/zeppelin/img/ui-img/about_menu.png" width="450px" />
|
|
|
|
#### Interpreter
|
|
|
|
In this menu you can:
|
|
|
|
1. Configure existing **interpreter instance**
|
|
2. Add/remove **interpreter instances**
|
|
|
|
<img src="../assets/themes/zeppelin/img/ui-img/interpreter_menu.png" />
|
|
|
|
#### Credential
|
|
|
|
This menu allows you to save credentials for data sources which are passed to interpreters.
|
|
|
|
<img src="../assets/themes/zeppelin/img/ui-img/credential_menu.png" />
|
|
|
|
#### Configuration
|
|
|
|
This menu displays all the Zeppelin configuration that are set in the config file `$ZEPPELIN_HOME/conf/zeppelin-site.xml`
|
|
|
|
<img src="../assets/themes/zeppelin/img/ui-img/configuration_menu.png" />
|
|
|
|
|
|
<br />
|
|
## Note Layout
|
|
|
|
Each Zeppelin note is composed of 1 .. N paragraphs. The note can be viewed as a paragraph container.
|
|
|
|
<img src="../assets/themes/zeppelin/img/ui-img/note_paragraph_layout.png" />
|
|
|
|
### Paragraph
|
|
|
|
Each paragraph consists of 2 sections: `code section` where you put your source code and `result section` where you can see the result of the code execution.
|
|
|
|
<img src="../assets/themes/zeppelin/img/ui-img/paragraph_layout.png" />
|
|
|
|
On the top-right corner of each paragraph there are some commands to:
|
|
|
|
* execute the paragraph code
|
|
* hide/show `code section`
|
|
* hide/show `result section`
|
|
* configure the paragraph
|
|
|
|
To configure the paragraph, just click on the gear icon:
|
|
|
|
<img src="../assets/themes/zeppelin/img/ui-img/paragraph_configuration_dialog.png" width="180px" />
|
|
|
|
From this dialog, you can (in descending order):
|
|
|
|
* find the **paragraph id** ( **20150924-163507_134879501** )
|
|
* control paragraph width. Since Zeppelin is using the grid system of **Twitter Bootstrap**, each paragraph width can be changed from 1 to 12
|
|
* move the paragraph 1 level up
|
|
* move the paragraph 1 level down
|
|
* create a new paragraph
|
|
* change paragraph title
|
|
* show/hide line number in the `code section`
|
|
* disable the run button for this paragraph
|
|
* export the current paragraph as an **iframe** and open the **iframe** in a new window
|
|
* clear the `result section`
|
|
* delete the current paragraph
|
|
|
|
### Note toolbar
|
|
|
|
At the top of the note, you can find a toolbar which exposes command buttons as well as configuration, security and display options.
|
|
|
|
<img src="../assets/themes/zeppelin/img/ui-img/note_toolbar.png" />
|
|
|
|
On the far right is displayed the note name, just click on it to reveal the input form and update it.
|
|
|
|
In the middle of the toolbar you can find the command buttons:
|
|
|
|
* execute all the paragraphs **sequentially**, in their display order
|
|
* hide/show `code section` of all paragraphs
|
|
* hide/show `result section` of all paragraphs
|
|
* clear the `result section` of all paragraphs
|
|
* clone the current note
|
|
* export the current note to a JSON file. _Please note that the `code section` and `result section` of all paragraphs will be exported. If you have heavy data in the `result section` of some paragraphs, it is recommended to clean them before exporting
|
|
* commit the current node content
|
|
* delete the note
|
|
* schedule the execution of **all paragraph** using a CRON syntax
|
|
|
|
<img src="../assets/themes/zeppelin/img/ui-img/note_commands.png" width="300px"/>
|
|
|
|
On the right of the note tool bar you can find configuration icons:
|
|
|
|
* display all the keyboard shorcuts
|
|
* configure the interpreters binding to the current note
|
|
* configure the note permissions
|
|
* switch the node display mode between `default`, `simple` and `report`
|
|
|
|
<img src="../assets/themes/zeppelin/img/ui-img/note_configuration.png" width="180px"/>
|