zeppelin git commit: [ZEPPELIN-2431] Corrected deletion of notes by incorrect interpreter.json

Repository: zeppelin Updated Branches: refs/heads/master c8cd1cf50 -> 874403256 [ZEPPELIN-2431] Corrected deletion of notes by incorrect interpreter.json ## What is this PR for? We sometimes can not delete a note, or we will be accompanied by an NPE for deleting a note. This problem occurs

zeppelin git commit: ZEPPELIN-2407. Livy Interpreter always return plain text result

Repository: zeppelin Updated Branches: refs/heads/branch-0.7 b7171d195 -> d45fdf921 ZEPPELIN-2407. Livy Interpreter always return plain text result ### What is this PR for? It happens when zeppelin.livy.displayAppInfo is true. Straightforward fix. ### What type of PR is it? [Bug Fix] ### Tod

zeppelin git commit: ZEPPELIN-2224. Throw more meaningful exception when kerberos is enabled in livy interpreter

Repository: zeppelin Updated Branches: refs/heads/branch-0.7 c52c0aced -> b7171d195 ZEPPELIN-2224. Throw more meaningful exception when kerberos is enabled in livy interpreter ### What is this PR for? In kerberos enviroment, user would get the following exception is impersonation configurati

zeppelin git commit: ZEPPELIN-2261. Support to connect with livy through https

Repository: zeppelin Updated Branches: refs/heads/branch-0.7 59c1e1b0a -> c52c0aced ZEPPELIN-2261. Support to connect with livy through https ### What is this PR for? Livy server support https, but the currently livy interpreter doesn't support it. This PR is for for the supporting to connect

zeppelin git commit: ZEPPELIN-2151. Add integration test for livy cancel api

Repository: zeppelin Updated Branches: refs/heads/branch-0.7 b9bc2b810 -> 59c1e1b0a ZEPPELIN-2151. Add integration test for livy cancel api ### What is this PR for? Just add integration test for livy cancel api. Only do it for livy 0.3 as the cancel api is only available in livy 0.3 ### Wha

zeppelin git commit: ZEPPELIN-1595. Make ZeppelinContext extensible

Repository: zeppelin Updated Branches: refs/heads/master 0f1701da8 -> c8cd1cf50 ZEPPELIN-1595. Make ZeppelinContext extensible ### What is this PR for? For now, ZeppelinContext only support Spark Interpreter. I'd like to make it extensible, so that it can support other interpreters as well. F

zeppelin git commit: [HOTFIX] Add livy build in .travis

Repository: zeppelin Updated Branches: refs/heads/branch-0.7 c4cf06869 -> b9bc2b810 [HOTFIX] Add livy build in .travis livy integration test is ignored, this PR add livy integration test in travis [Hot Fix] * [ ] - Task * No jira created CI pass * Does the licenses files need update? No *

zeppelin git commit: ZEPPELIN-2079. Upgrade livy to 0.3 in livy interpreter

Repository: zeppelin Updated Branches: refs/heads/branch-0.7 f1064f62d -> c4cf06869 ZEPPELIN-2079. Upgrade livy to 0.3 in livy interpreter Upgrade livy to 0.3. * Add new tests for livy 0.3 * Add 2 livy build in travis. (livy 0.2 + spark 1.6.3 and livy 0.3 + spark 2.1.0, unfortunately livy 0.

zeppelin git commit: [HOTFIX] Add livy build in .travis

Repository: zeppelin Updated Branches: refs/heads/master 5cd806dc3 -> 0f1701da8 [HOTFIX] Add livy build in .travis ### What is this PR for? livy integration test is ignored, this PR add livy integration test in travis ### What type of PR is it? [Hot Fix] ### Todos * [ ] - Task ### What is