GitHub user cypark1 opened a pull request: https://github.com/apache/zeppelin/pull/3251
test2 ### What is this PR for? A few sentences describing the overall goals of the pull request's commits. First time? Check out the contributing guide - https://zeppelin.apache.org/contribution/contributions.html ### What type of PR is it? [Bug Fix | Improvement | Feature | Documentation | Hot Fix | Refactoring] ### Todos * [ ] - Task ### What is the Jira issue? * Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/ * Put link here, and add [ZEPPELIN-*Jira number*] in PR title, eg. [ZEPPELIN-533] ### How should this be tested? * First time? Setup Travis CI as described on https://zeppelin.apache.org/contribution/contributions.html#continuous-integration * Strongly recommended: add automated unit tests for any new or changed behavior * Outline any manual steps to test the PR here. ### Screenshots (if appropriate) ### Questions: * Does the licenses files need update? * Is there breaking changes for older versions? * Does this needs documentation? You can merge this pull request into a Git repository by running: $ git pull https://github.com/cypark1/zeppelin_test master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/3251.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3251 ---- commit 150d60e945014d1c4d4c63805340b2bf6c663701 Author: cypark1 <45478729+cypark1@...> Date: 2018-12-03T08:48:30Z test.text test commit 34743124518aa39b3e2a2136df25dfa291ad2652 Author: cypark1 <45478729+cypark1@...> Date: 2018-12-05T01:50:24Z Merge pull request #1 from cypark1/cypark1-patch-1 test.text ---- ---