[GitHub] zeppelin issue #1637: [ZEPPELIN-1665 : WIP] Z.run with external note executa...
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1637
add feature for `z.runNote("noteID")`
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin issue #1606: [ZEPPELIN-777] Math formula support
Github user giaosudau commented on the issue: https://github.com/apache/zeppelin/pull/1606 I build a distribution from source code but it's failed because of missing /jax /extesions/ Did you guys test this case? How to fix it? Thanks. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1638: [ZEPPELIN-1666] DON'T share mutable deps, optio...
GitHub user 1ambda reopened a pull request: https://github.com/apache/zeppelin/pull/1638 [ZEPPELIN-1666] DON'T share mutable deps, options between interpreters in each group (bug) ### What is this PR for? Every interpreter shares their `List` and `InterpreterOption` object with other interpreters in the same group since these objects are mutable and just returned from `InterpreterSettingRef` in InterpreterFactory. I attached GIF ### What type of PR is it? [Bug Fix] ### Todos Nothing ### What is the Jira issue? [ZEPPELIN-1666](https://issues.apache.org/jira/browse/ZEPPELIN-1666) ### How should this be tested? I included unit test for it in `InterpreterRestApiTest` ### Screenshots (if appropriate)  ### Questions: * Does the licenses files need update? - NO * Is there breaking changes for older versions? - NO * Does this needs documentation? - NO You can merge this pull request into a Git repository by running: $ git pull https://github.com/1ambda/zeppelin fix/do-not-share-deps-in-same-group Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1638.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 #1638 commit 931bf784899f9443489d903b32863b4042defeea Author: 1ambda <1am...@gmail.com> Date: 2016-11-15T07:58:21Z test: Add failing test commit f594a4ada885738abc14f6aad37ab4ec7241208e Author: 1ambda <1am...@gmail.com> Date: 2016-11-15T09:17:10Z fix: Return immutable objects commit da6656f47b08ab2b29eb5875ee3c7e29ae3081e7 Author: 1ambda <1am...@gmail.com> Date: 2016-11-15T12:59:56Z fix: mutable object problems in InterpreterSetting By filling InterpreterSetting object by newly created objects commit 337ae7f005efa34f00adab266d7fefc302fcb3a5 Author: 1ambda <1am...@gmail.com> Date: 2016-11-15T13:09:00Z style: Reindent using zeppelin's checkstyle xml commit f2ddeba90ff655131a6d2069073889950bfbd07c Author: 1ambda <1am...@gmail.com> Date: 2016-11-16T10:11:57Z fix: Set DEBUG log level in DependencyResolver --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1638: [ZEPPELIN-1666] DON'T share mutable deps, optio...
Github user 1ambda closed the pull request at: https://github.com/apache/zeppelin/pull/1638 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1659: [ZEPPELIN-1667] Fix maven options while updatin...
GitHub user 1ambda reopened a pull request: https://github.com/apache/zeppelin/pull/1659 [ZEPPELIN-1667] Fix maven options while updating node, npm packages ### What is this PR for? Update maven plugin, node vesion, npm package and fix tests to make #1639 pass CI ### What is the Jira issue? Sub issue of #1639 ### Questions: Does the licenses files need update? NO Is there breaking changes for older versions? YES (front-end build tool usage changed) Does this needs documentation? YES (front-end build tool usage changed) You can merge this pull request into a Git repository by running: $ git pull https://github.com/1ambda/zeppelin pr/1639 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1659.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 #1659 commit f65cb5e54f94cc34be54293db635f2b8e8d13407 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T07:47:42Z chore: Update frontend plugin version commit b6631c41970f176d99325e4cd07a14d69f7687c0 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T08:05:21Z chore: Add test, build task to npm commit d7753a18bfc91b1d3af592ee36f48c6e033864b9 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T12:37:26Z fix(web): npm tasks in pom.xml commit b86e8bdf7092fd65e1996a9b281085224772cbec Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T13:21:57Z chore: Update assembly plugin version commit 48e3f04f699c6b9ef748d9e940bfde92b56e1f20 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T13:24:43Z chore: Set maven option using mavenrc commit 8975a8291c38d975cef99a4388bbf60a4d79869f Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T13:27:53Z chore: fix travis maven option commit ebfb16391a5ea7c6c98dac50ca3bc7b22f6c1d05 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T13:38:10Z chore: Remove bower install root option commit 44e16af92246bd34dcb72c92d274663d90549715 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T13:44:55Z chore: Update node, npm version to avoid proxy error commit 23dd663d05ffb3ad70773f341406bf99551128c8 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T13:50:53Z fix: Restore bower install option commit b163567151962bfddb6c00507dc59319c2c83f01 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T14:19:13Z chore: Add slient option to bower (show error only) commit bba95b521d616ce46ba1d4df7cb5185dd49cfa0f Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T14:31:40Z chore: Update karma, phantom related package version commit 6b69e6190d21d884c20e74efe8c6eee5e4b34722 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T14:58:43Z test: fix test for jasmine-core 2.x ref - http://stackoverflow.com/questions/27680933/jasmine-have-createspy-return-mock-object commit dc426b396d2e5ba90d8e51fcd2009b3f503f1b7e Author: 1ambda <1am...@gmail.com> Date: 2016-11-21T02:42:36Z fix: Caching npm, bower, node directories commit 484dd1b5e416b48cf9d17393e9295a0fe49ac4a3 Author: 1ambda <1am...@gmail.com> Date: 2016-11-21T03:05:53Z fix: Print warn, error log only while packing commit 0a7504b9f72143436e4d88b520265d09d6838bb9 Author: 1ambda <1am...@gmail.com> Date: 2016-11-21T03:07:28Z fix: Remove useless script --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1659: [ZEPPELIN-1667] Fix maven options while updatin...
Github user 1ambda closed the pull request at: https://github.com/apache/zeppelin/pull/1659 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1638: [ZEPPELIN-1666] DON'T share mutable deps, optio...
GitHub user 1ambda reopened a pull request: https://github.com/apache/zeppelin/pull/1638 [ZEPPELIN-1666] DON'T share mutable deps, options between interpreters in each group (bug) ### What is this PR for? Every interpreter shares their `List` and `InterpreterOption` object with other interpreters in the same group since these objects are mutable and just returned from `InterpreterSettingRef` in InterpreterFactory. I attached GIF ### What type of PR is it? [Bug Fix] ### Todos Nothing ### What is the Jira issue? [ZEPPELIN-1666](https://issues.apache.org/jira/browse/ZEPPELIN-1666) ### How should this be tested? I included unit test for it in `InterpreterRestApiTest` ### Screenshots (if appropriate)  ### Questions: * Does the licenses files need update? - NO * Is there breaking changes for older versions? - NO * Does this needs documentation? - NO You can merge this pull request into a Git repository by running: $ git pull https://github.com/1ambda/zeppelin fix/do-not-share-deps-in-same-group Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1638.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 #1638 commit 931bf784899f9443489d903b32863b4042defeea Author: 1ambda <1am...@gmail.com> Date: 2016-11-15T07:58:21Z test: Add failing test commit f594a4ada885738abc14f6aad37ab4ec7241208e Author: 1ambda <1am...@gmail.com> Date: 2016-11-15T09:17:10Z fix: Return immutable objects commit da6656f47b08ab2b29eb5875ee3c7e29ae3081e7 Author: 1ambda <1am...@gmail.com> Date: 2016-11-15T12:59:56Z fix: mutable object problems in InterpreterSetting By filling InterpreterSetting object by newly created objects commit 337ae7f005efa34f00adab266d7fefc302fcb3a5 Author: 1ambda <1am...@gmail.com> Date: 2016-11-15T13:09:00Z style: Reindent using zeppelin's checkstyle xml commit f2ddeba90ff655131a6d2069073889950bfbd07c Author: 1ambda <1am...@gmail.com> Date: 2016-11-16T10:11:57Z fix: Set DEBUG log level in DependencyResolver --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1659: [ZEPPELIN-1667] Fix maven options while updatin...
GitHub user 1ambda reopened a pull request: https://github.com/apache/zeppelin/pull/1659 [ZEPPELIN-1667] Fix maven options while updating node, npm packages ### What is this PR for? Update maven plugin, node vesion, npm package and fix tests to make #1639 pass CI ### What is the Jira issue? Sub issue of #1639 ### Questions: Does the licenses files need update? NO Is there breaking changes for older versions? YES (front-end build tool usage changed) Does this needs documentation? YES (front-end build tool usage changed) You can merge this pull request into a Git repository by running: $ git pull https://github.com/1ambda/zeppelin pr/1639 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1659.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 #1659 commit f65cb5e54f94cc34be54293db635f2b8e8d13407 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T07:47:42Z chore: Update frontend plugin version commit b6631c41970f176d99325e4cd07a14d69f7687c0 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T08:05:21Z chore: Add test, build task to npm commit d7753a18bfc91b1d3af592ee36f48c6e033864b9 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T12:37:26Z fix(web): npm tasks in pom.xml commit b86e8bdf7092fd65e1996a9b281085224772cbec Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T13:21:57Z chore: Update assembly plugin version commit 48e3f04f699c6b9ef748d9e940bfde92b56e1f20 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T13:24:43Z chore: Set maven option using mavenrc commit 8975a8291c38d975cef99a4388bbf60a4d79869f Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T13:27:53Z chore: fix travis maven option commit ebfb16391a5ea7c6c98dac50ca3bc7b22f6c1d05 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T13:38:10Z chore: Remove bower install root option commit 44e16af92246bd34dcb72c92d274663d90549715 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T13:44:55Z chore: Update node, npm version to avoid proxy error commit 23dd663d05ffb3ad70773f341406bf99551128c8 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T13:50:53Z fix: Restore bower install option commit b163567151962bfddb6c00507dc59319c2c83f01 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T14:19:13Z chore: Add slient option to bower (show error only) commit bba95b521d616ce46ba1d4df7cb5185dd49cfa0f Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T14:31:40Z chore: Update karma, phantom related package version commit 6b69e6190d21d884c20e74efe8c6eee5e4b34722 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T14:58:43Z test: fix test for jasmine-core 2.x ref - http://stackoverflow.com/questions/27680933/jasmine-have-createspy-return-mock-object commit dc426b396d2e5ba90d8e51fcd2009b3f503f1b7e Author: 1ambda <1am...@gmail.com> Date: 2016-11-21T02:42:36Z fix: Caching npm, bower, node directories commit 484dd1b5e416b48cf9d17393e9295a0fe49ac4a3 Author: 1ambda <1am...@gmail.com> Date: 2016-11-21T03:05:53Z fix: Print warn, error log only while packing commit 0a7504b9f72143436e4d88b520265d09d6838bb9 Author: 1ambda <1am...@gmail.com> Date: 2016-11-21T03:07:28Z fix: Remove useless script --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1638: [ZEPPELIN-1666] DON'T share mutable deps, optio...
Github user 1ambda closed the pull request at: https://github.com/apache/zeppelin/pull/1638 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1659: [ZEPPELIN-1667] Fix maven options while updatin...
Github user 1ambda closed the pull request at: https://github.com/apache/zeppelin/pull/1659 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1638: [ZEPPELIN-1666] DON'T share mutable deps, optio...
Github user 1ambda closed the pull request at: https://github.com/apache/zeppelin/pull/1638 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1638: [ZEPPELIN-1666] DON'T share mutable deps, optio...
GitHub user 1ambda reopened a pull request: https://github.com/apache/zeppelin/pull/1638 [ZEPPELIN-1666] DON'T share mutable deps, options between interpreters in each group (bug) ### What is this PR for? Every interpreter shares their `List` and `InterpreterOption` object with other interpreters in the same group since these objects are mutable and just returned from `InterpreterSettingRef` in InterpreterFactory. I attached GIF ### What type of PR is it? [Bug Fix] ### Todos Nothing ### What is the Jira issue? [ZEPPELIN-1666](https://issues.apache.org/jira/browse/ZEPPELIN-1666) ### How should this be tested? I included unit test for it in `InterpreterRestApiTest` ### Screenshots (if appropriate)  ### Questions: * Does the licenses files need update? - NO * Is there breaking changes for older versions? - NO * Does this needs documentation? - NO You can merge this pull request into a Git repository by running: $ git pull https://github.com/1ambda/zeppelin fix/do-not-share-deps-in-same-group Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1638.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 #1638 commit 931bf784899f9443489d903b32863b4042defeea Author: 1ambda <1am...@gmail.com> Date: 2016-11-15T07:58:21Z test: Add failing test commit f594a4ada885738abc14f6aad37ab4ec7241208e Author: 1ambda <1am...@gmail.com> Date: 2016-11-15T09:17:10Z fix: Return immutable objects commit da6656f47b08ab2b29eb5875ee3c7e29ae3081e7 Author: 1ambda <1am...@gmail.com> Date: 2016-11-15T12:59:56Z fix: mutable object problems in InterpreterSetting By filling InterpreterSetting object by newly created objects commit 337ae7f005efa34f00adab266d7fefc302fcb3a5 Author: 1ambda <1am...@gmail.com> Date: 2016-11-15T13:09:00Z style: Reindent using zeppelin's checkstyle xml commit f2ddeba90ff655131a6d2069073889950bfbd07c Author: 1ambda <1am...@gmail.com> Date: 2016-11-16T10:11:57Z fix: Set DEBUG log level in DependencyResolver --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1659: [ZEPPELIN-1667] Fix maven options while updating node,...
Github user 1ambda commented on the issue: https://github.com/apache/zeppelin/pull/1659 https://travis-ci.org/apache/zeppelin/builds/177545019 (before caching bower, npm, node dc426b3) https://cloud.githubusercontent.com/assets/4968473/20469221/a188bc5e-afe1-11e6-9a8f-1cc9636e4421.png";> --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1659: [ZEPPELIN-1667] Fix maven options while updatin...
Github user 1ambda closed the pull request at: https://github.com/apache/zeppelin/pull/1659 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1659: [ZEPPELIN-1667] Fix maven options while updatin...
GitHub user 1ambda reopened a pull request: https://github.com/apache/zeppelin/pull/1659 [ZEPPELIN-1667] Fix maven options while updating node, npm packages ### What is this PR for? Update maven plugin, node vesion, npm package and fix tests to make #1639 pass CI ### What is the Jira issue? Sub issue of #1639 ### Questions: Does the licenses files need update? NO Is there breaking changes for older versions? YES (front-end build tool usage changed) Does this needs documentation? YES (front-end build tool usage changed) You can merge this pull request into a Git repository by running: $ git pull https://github.com/1ambda/zeppelin pr/1639 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1659.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 #1659 commit ef32be0d8178d1eaafb40c5223c3b40375608a01 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T07:47:42Z chore: Update frontend plugin version commit a5d43df6921ce556292e73415611dca9d4fdcda5 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T08:05:21Z chore: Add test, build task to npm commit 11e9b003cc530f24b182ba8ace44180e612fa38a Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T12:30:08Z chore: Set maven options commit 6b12125fd773d73cff6f2455ef2b08fa8750b9da Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T12:37:26Z fix(web): npm tasks in pom.xml commit 8efd32db0fbb7d62b689bf9b8acbbb4cce61fa37 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T12:49:26Z fix(web): Set maven PerrGen option commit 244f7c5ef3c5e5c2a2cc6db85dceee1704fd64c3 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T13:21:57Z chore: Update assembly plugin version commit 3daf4238d919d1a077e00afcfa87dfdbdef7efa2 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T13:24:43Z chore: Set maven option using mavenrc commit f2a85145e22e9298d886038e9c10107e7492376e Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T13:27:53Z chore: fix travis maven option commit 548336c28e907efb8ffab621ad023b04132e9fb5 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T13:38:10Z chore: Remove bower install root option commit 4fcc48b3a1c8928a91223f597f39c36b8674d64b Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T13:44:55Z chore: Update node, npm version to avoid proxy error commit a6d10990da52f31aa0b9fb371bd4d72b21f47e16 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T13:50:53Z fix: Restore bower install option commit 3ca7372bc804f4da26269b7e2b3d39f02f429339 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T14:19:13Z chore: Add slient option to bower (show error only) commit 216db8751f6027dae07b3a4c06378a804d834bac Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T14:31:40Z chore: Update karma, phantom related package version commit f0f7dc72b422e400ddcd2815f78ec6742162e809 Author: 1ambda <1am...@gmail.com> Date: 2016-11-19T14:58:43Z test: fix test for jasmine-core 2.x ref - http://stackoverflow.com/questions/27680933/jasmine-have-createspy-return-mock-object --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1656: Fix Yarn configuration of Spark2.0
Github user astroshim closed the pull request at: https://github.com/apache/zeppelin/pull/1656 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1656: Fix Yarn configuration of Spark2.0
GitHub user astroshim reopened a pull request: https://github.com/apache/zeppelin/pull/1656 Fix Yarn configuration of Spark2.0 ### What is this PR for? `yarn-client` is deprecated since Spark 2.0, so SparkInterpreter also support `yarn` as `application master`. ### What type of PR is it? Bug Fix | Improvement ### How should this be tested? Run spark paragraph with Spark2.0 + yarn. ### Questions: * Does the licenses files need update? no * Is there breaking changes for older versions? no * Does this needs documentation? no You can merge this pull request into a Git repository by running: $ git pull https://github.com/astroshim/zeppelin fix/yarn-spark2.0 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1656.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 #1656 commit a4f3fa3742fa1aad6fa2ec698c29aac752cb9ca6 Author: astroshim Date: 2016-11-18T14:07:04Z fix spark2.0 connection error with EMR commit 93f7f9c20e62121eef88ca8d172892b670c6af16 Author: astroshim Date: 2016-11-18T14:58:37Z update spark conf commit b225dd4cb1e8fe6250d162792b8a0d3c9bdf7dac Author: astroshim Date: 2016-11-18T15:54:06Z add master yarn commit 4374ce0310e760b52938240411c6b67f4ba1d300 Author: astroshim Date: 2016-11-19T11:44:42Z fix spark configuration --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1661: [ZEPPELIN-1605] zeppelin-interpreter: don't pub...
GitHub user minahlee opened a pull request: https://github.com/apache/zeppelin/pull/1661 [ZEPPELIN-1605] zeppelin-interpreter: don't publish shaded JAR on maven central ### What is this PR for? * Instead of creating fat jar for zeppelin-interpreter, place zeppelin-interpreter.jar and dependencies under `lib/interpreter` directory and add it to classpath of zeppelin-server and interpreter. (removed maven-shade-plugin) * Exclude some dependencies from `zeppelin-zengine` which cause conflicts with `zeppelin-interpreter`'s dependency * Exclude configuration files(`credential.json`, `notebook-authorization.json`, `shiro.ini`) from binary package. ### What type of PR is it? Improvement ### What is the Jira issue? [ZEPPELIN-1605](https://issues.apache.org/jira/browse/ZEPPELIN-1605) ### Screenshots (if appropriate) ### Questions: * Does the licenses files need update? no * Is there breaking changes for older versions? no * Does this needs documentation? no You can merge this pull request into a Git repository by running: $ git pull https://github.com/minahlee/zeppelin ZEPPELIN-1605 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1661.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 #1661 commit 283f2065228c372ed9ff4b5e5d49817f520ed31f Author: Mina Lee Date: 2016-11-21T00:12:06Z package zeppelin-interpreter jar without dependency --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (ZEPPELIN-1687) Use ZEPPELIN_INTP_CLASSPATH for interpreter classpath in interpreter.cmd
Mina Lee created ZEPPELIN-1687: -- Summary: Use ZEPPELIN_INTP_CLASSPATH for interpreter classpath in interpreter.cmd Key: ZEPPELIN-1687 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1687 Project: Zeppelin Issue Type: Bug Affects Versions: 0.6.2 Reporter: Mina Lee Assignee: Mina Lee Fix For: 0.7.0 https://github.com/apache/zeppelin/pull/1228 changed ZEPPELIN_CLASSPATH to ZEPPELIN_INTP_CLASSPATH but the change has been made only for interpreter.sh not interpreter.cmd. Should apply same change to interpreter.cmd for consistent support for linux and window. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZEPPELIN-1686) Keyboard shortcut for clear paragraph output
Lee moon soo created ZEPPELIN-1686: -- Summary: Keyboard shortcut for clear paragraph output Key: ZEPPELIN-1686 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1686 Project: Zeppelin Issue Type: Improvement Reporter: Lee moon soo Priority: Minor Attachments: screenshot-1.png Each paragraph menu, "Clear output" clear the output of the paragraph. It would be convenient keyboard shortcut is supported for this feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] zeppelin pull request #1614: ZEPPELIN-1472 - Create new LdapRealm based on A...
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/1614 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1660: [WIP][ZEPPELIN-1594] Personalized mode
GitHub user jongyoul opened a pull request: https://github.com/apache/zeppelin/pull/1660 [WIP][ZEPPELIN-1594] Personalized mode ### What is this PR for? Support personalized mode in multi user environments. ### What type of PR is it? [Feature] ### Todos * [x] - Add the method to send the result to specific user * [ ] - Add the UI to toggle "personlized mode" in a note ### What is the Jira issue? * https://issues.apache.org/jira/browse/ZEPPELIN-1594 ### How should this be tested? 1. Apply this patch 2. Enable shiro 3. note.config.personalizedMode = true in a note.json to be tested ### Screenshots (if appropriate) ### Questions: * Does the licenses files need update? No * Is there breaking changes for older versions? No * Does this needs documentation? Yes This covers the first Todo only. @cloverhearts @1ambda Can you help me implement in a front-side? You can merge this pull request into a Git repository by running: $ git pull https://github.com/jongyoul/zeppelin ZEPPELIN-1594 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1660.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 #1660 commit f23e4f34d07c18405d3a7b05d8903dd5c1973354 Author: Jongyoul Lee Date: 2016-11-20T22:01:30Z Added the logic to check if personalized mode turns on or not Added the method to send note update to specific user --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1653: Relative path on windows getAbsolutePath() and ...
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/1653 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1605: [ZEPPELIN-1622] Remove %dep interpreter depreca...
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/1605 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1648: [ZEPPELIN-1673] Reduce CI log size and make it ...
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/1648 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1655: [ZEPPELIN-1684] Add GET /interpreter/setting/id...
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/1655 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1630: [ZEPPELIN-1629] Enable renaming folder from the main p...
Github user tae-jun commented on the issue: https://github.com/apache/zeppelin/pull/1630 I guess CI fails because it only recompiles changed files. (since build time is too short)  It should be about 30min. Is there any way to compile the whole project again? I ran CI on [my own repository](https://travis-ci.org/tae-jun/zeppelin). It failed on some profiles because of Ignite interpreter. (what is relevance between Ignite interpreter and my PR? ð) But it passed on other profiles whereas every profile failed on this repository. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1630: [ZEPPELIN-1629] Enable renaming folder from the main p...
Github user tae-jun commented on the issue: https://github.com/apache/zeppelin/pull/1630 @AhyoungRyu I fixed what you mentioned ð Please review. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1582: [ZEPPELIN-1604] Add Neo4j interpreter and Network visu...
Github user conker84 commented on the issue: https://github.com/apache/zeppelin/pull/1582 Hi @Leemoonsoo i have just published the code refactored as from #1529 I will look forward to your feedback! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1614: ZEPPELIN-1472 - Create new LdapRealm based on A...
GitHub user gss2002 reopened a pull request:
https://github.com/apache/zeppelin/pull/1614
ZEPPELIN-1472 - Create new LdapRealm based on Apache Knox LdapRealm:
Provides LdapRealm Functionality similar to Apache Knox
### What is this PR for?
ZEPPELIN-1472 - Create new LdapRealm based on Apache Knox LdapRealm:
Provides LdapRealm Functionality similar to what Apache Knox provides. This is
critical as in large enterprise environments Active Directory Global Catalogs
are used for lookup with samAccountName and using a DN Template is not an
option as their are multiple OUs. Also searching on "userPrincipalName" is
risky in an AD environment since the explicit UPN vs Implicit UPN can be
different this is definitely the case with environments using Office 365. And
the LDAP userPrincipalName attribute is the explicit UPN which can be defined
by the directory administrator to any value and it can be duplicated.
SamAccountName is unique per domain and Microsoft states best practice is to
not allow duplicate samAccountName's across the forest.
In addition to the above changes I have adjusted and moved the
LdapGroupRealm and ActiveDirectoryGroupRealm into the org.apache.zeppelin.realm
package structure to make all Realm's consistent.
The LdapRealm class also works with role to group mapping for usage within
Zeppelin for notebook authorization.
I have adjusted SecurityUtils to use ClassName vs realmName in determining
what to use as you may have companies that decide to use their own custom
realmname in shiro.ini and may not realize you cannot so using className is
much safer.
Example - SecurityUtils
String name = realm.getClass().getName();
if (name.equals("org.apache.shiro.realm.text.IniRealm")) {
allRoles = ((IniRealm) realm).getIni().get("roles");
break;
} else if (name.equals("org.apache.zeppelin.realm.LdapRealm")) {
allRoles = ((LdapRealm) realm).getListRoles();
break;
}
Example - SecurityRestApi:
String name = realm.getClass().getName();
if (LOG.isDebugEnabled()) {
LOG.debug("RealmClass.getName: " + name);
}
if (name.equals("org.apache.shiro.realm.text.IniRealm")) {
usersList.addAll(getUserListObj.getUserList((IniRealm) realm));
rolesList.addAll(getUserListObj.getRolesList((IniRealm) realm));
} else if
(name.equals("org.apache.zeppelin.realm.LdapGroupRealm")) {
usersList.addAll(getUserListObj.getUserList((JndiLdapRealm)
realm, searchText));
} else if (name.equals("org.apache.zeppelin.realm.LdapRealm")) {
usersList.addAll(getUserListObj.getUserList((LdapRealm) realm,
searchText));
rolesList.addAll(getUserListObj.getRolesList((LdapRealm)
realm));
} else if
(name.equals("org.apache.zeppelin.realm.ActiveDirectoryGroupRealm")) {
usersList.addAll(getUserListObj.getUserList((ActiveDirectoryGroupRealm) realm,
searchText));
} else if (name.equals("org.apache.shiro.realm.jdbc.JdbcRealm")) {
usersList.addAll(getUserListObj.getUserList((JdbcRealm) realm));
}
Please see feedback from previous PRs related to this JIRA:
https://github.com/apache/zeppelin/pull/1513
### What type of PR is it?
[Improvement]
### Todos
* [ ] - Task
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1472
### How should this be tested?
Update shiro.ini to use configuration similar to below:
# Sample LDAP configuration, for user Authentication, currently tested for
single Realm
[main]
ldapADGCRealm = org.apache.zeppelin.realm.LdapRealm
ldapADGCRealm.contextFactory.systemUsername =
CN=hdplookup,OU=hadoop,DC=hdpusr,DC=senia,DC=org
ldapADGCRealm.contextFactory.systemPassword = ldapBindPassword
ldapADGCRealm.searchBase = dc=hdpusr,dc=senia,dc=org
ldapADGCRealm.userSearchBase = dc=hdpusr,dc=senia,dc=org
ldapADGCRealm.groupSearchBase = dc=hdpusr,dc=senia,dc=org
ldapADGCRealm.authorizationEnabled = true
ldapADGCRealm.contextFactory.url = ldap://seniadc1.hdpusr.senia.org:3268
ldapADGCRealm.userSearchAttributeName = sAMAccountName
ldapADGCRealm.contextFactory.authenticationMechanism = simple
ldapADGCRealm.groupObjectClass = group
ldapADGCRealm.memberAttribute = member
ldapADGCRealm.rolesByGroup = hdpeng: admin, \
hadoopusers: user
securityManager.realms = $ldapADGCRealm
sessionManager = org.apache.shiro.web.session.mgt.DefaultWebSessionManager
### If caching of user is required then uncomment below lines
#cacheManager = org.apache.shiro.cache.MemoryConstrainedCacheManager
#securityManager.cacheManager = $
[GitHub] zeppelin pull request #1614: ZEPPELIN-1472 - Create new LdapRealm based on A...
Github user gss2002 closed the pull request at: https://github.com/apache/zeppelin/pull/1614 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1614: ZEPPELIN-1472 - Create new LdapRealm based on A...
GitHub user gss2002 reopened a pull request:
https://github.com/apache/zeppelin/pull/1614
ZEPPELIN-1472 - Create new LdapRealm based on Apache Knox LdapRealm:
Provides LdapRealm Functionality similar to Apache Knox
### What is this PR for?
ZEPPELIN-1472 - Create new LdapRealm based on Apache Knox LdapRealm:
Provides LdapRealm Functionality similar to what Apache Knox provides. This is
critical as in large enterprise environments Active Directory Global Catalogs
are used for lookup with samAccountName and using a DN Template is not an
option as their are multiple OUs. Also searching on "userPrincipalName" is
risky in an AD environment since the explicit UPN vs Implicit UPN can be
different this is definitely the case with environments using Office 365. And
the LDAP userPrincipalName attribute is the explicit UPN which can be defined
by the directory administrator to any value and it can be duplicated.
SamAccountName is unique per domain and Microsoft states best practice is to
not allow duplicate samAccountName's across the forest.
In addition to the above changes I have adjusted and moved the
LdapGroupRealm and ActiveDirectoryGroupRealm into the org.apache.zeppelin.realm
package structure to make all Realm's consistent.
The LdapRealm class also works with role to group mapping for usage within
Zeppelin for notebook authorization.
I have adjusted SecurityUtils to use ClassName vs realmName in determining
what to use as you may have companies that decide to use their own custom
realmname in shiro.ini and may not realize you cannot so using className is
much safer.
Example - SecurityUtils
String name = realm.getClass().getName();
if (name.equals("org.apache.shiro.realm.text.IniRealm")) {
allRoles = ((IniRealm) realm).getIni().get("roles");
break;
} else if (name.equals("org.apache.zeppelin.realm.LdapRealm")) {
allRoles = ((LdapRealm) realm).getListRoles();
break;
}
Example - SecurityRestApi:
String name = realm.getClass().getName();
if (LOG.isDebugEnabled()) {
LOG.debug("RealmClass.getName: " + name);
}
if (name.equals("org.apache.shiro.realm.text.IniRealm")) {
usersList.addAll(getUserListObj.getUserList((IniRealm) realm));
rolesList.addAll(getUserListObj.getRolesList((IniRealm) realm));
} else if
(name.equals("org.apache.zeppelin.realm.LdapGroupRealm")) {
usersList.addAll(getUserListObj.getUserList((JndiLdapRealm)
realm, searchText));
} else if (name.equals("org.apache.zeppelin.realm.LdapRealm")) {
usersList.addAll(getUserListObj.getUserList((LdapRealm) realm,
searchText));
rolesList.addAll(getUserListObj.getRolesList((LdapRealm)
realm));
} else if
(name.equals("org.apache.zeppelin.realm.ActiveDirectoryGroupRealm")) {
usersList.addAll(getUserListObj.getUserList((ActiveDirectoryGroupRealm) realm,
searchText));
} else if (name.equals("org.apache.shiro.realm.jdbc.JdbcRealm")) {
usersList.addAll(getUserListObj.getUserList((JdbcRealm) realm));
}
Please see feedback from previous PRs related to this JIRA:
https://github.com/apache/zeppelin/pull/1513
### What type of PR is it?
[Improvement]
### Todos
* [ ] - Task
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1472
### How should this be tested?
Update shiro.ini to use configuration similar to below:
# Sample LDAP configuration, for user Authentication, currently tested for
single Realm
[main]
ldapADGCRealm = org.apache.zeppelin.realm.LdapRealm
ldapADGCRealm.contextFactory.systemUsername =
CN=hdplookup,OU=hadoop,DC=hdpusr,DC=senia,DC=org
ldapADGCRealm.contextFactory.systemPassword = ldapBindPassword
ldapADGCRealm.searchBase = dc=hdpusr,dc=senia,dc=org
ldapADGCRealm.userSearchBase = dc=hdpusr,dc=senia,dc=org
ldapADGCRealm.groupSearchBase = dc=hdpusr,dc=senia,dc=org
ldapADGCRealm.authorizationEnabled = true
ldapADGCRealm.contextFactory.url = ldap://seniadc1.hdpusr.senia.org:3268
ldapADGCRealm.userSearchAttributeName = sAMAccountName
ldapADGCRealm.contextFactory.authenticationMechanism = simple
ldapADGCRealm.groupObjectClass = group
ldapADGCRealm.memberAttribute = member
ldapADGCRealm.rolesByGroup = hdpeng: admin, \
hadoopusers: user
securityManager.realms = $ldapADGCRealm
sessionManager = org.apache.shiro.web.session.mgt.DefaultWebSessionManager
### If caching of user is required then uncomment below lines
#cacheManager = org.apache.shiro.cache.MemoryConstrainedCacheManager
#securityManager.cacheManager = $
[GitHub] zeppelin issue #1614: ZEPPELIN-1472 - Create new LdapRealm based on Apache K...
Github user gss2002 commented on the issue:
https://github.com/apache/zeppelin/pull/1614
Going to close and re-open to re kick the tests. These tests have been
flaky I dont think the error is related to the patch...
15:38:55,459 ERROR org.apache.zeppelin.AbstractZeppelinIT:136 - Exception
in ParagraphActionsIT while testEditOnDoubleClick
org.openqa.selenium.ElementNotVisibleException: Element is not currently
visible and so may not be interacted with
Command duration or timeout: 30.04 seconds
Build info: version: '2.48.2', revision:
'41bccdd10cf2c0560f637404c2d96164b67d9d67', time: '2015-10-09 13:08:06'
System info: host: 'testing-docker-60ee1fc8-0996-4929-93bf-f3f4ab1d7d4e',
ip: '172.17.0.8', os.name: 'Linux', os.arch: 'amd64', os.version:
'4.4.0-47-generic', java.version: '1.7.0_76'
Session ID: e568225a-5433-4a6e-b11a-85faf279113b
Driver info: org.openqa.selenium.firefox.FirefoxDriver
Capabilities [{platform=LINUX, acceptSslCerts=true, javascriptEnabled=true,
cssSelectorsEnabled=true, databaseEnabled=true, browserName=firefox,
handlesAlerts=true, nativeEvents=false, webStorageEnabled=true,
rotatable=false, locationContextEnabled=true, applicationCacheEnabled=true,
takesScreenshot=true, version=31.0}]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at
org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:206)
at
org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:158)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:647)
at
org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:326)
at
org.openqa.selenium.remote.RemoteWebElement.sendKeys(RemoteWebElement.java:121)
at
org.apache.zeppelin.integration.ParagraphActionsIT.testEditOnDoubleClick(ParagraphActionsIT.java:443)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin pull request #1614: ZEPPELIN-1472 - Create new LdapRealm based on A...
Github user gss2002 closed the pull request at: https://github.com/apache/zeppelin/pull/1614 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1630: [ZEPPELIN-1629] Enable renaming folder from the main p...
Github user tae-jun commented on the issue: https://github.com/apache/zeppelin/pull/1630 @AhyoungRyu Thanks! I also think `notebook` is a little bit weird :) I merged your PR thanks. This change will affect other insufficient privileges error messages as well: * Insufficient privileges to `read` ~~notebook~~ * Insufficient privileges to `update` ~~notebook~~ * Insufficient privileges to `remove` ~~notebook~~ * Insufficient privileges to `write` ~~notebook~~ * Insufficient privileges to `clear output` ~~notebook~~ I prefer removing `notebook`. What do you think guys? If anyone has a concern about this, please tell. And about CI, I suffered from that error when I tried to compile only one project (e.g. `zeppelin-server`). Since `zeppelin-server` depends on `zeppelin-interpreter` and `zeppelin-zengine`, I had to build two dependencies and `install` them on local maven repo, which can be done with `mvn clean package install -DskipTests`. If not, when it tries to compile `zeppelin-server`, it cannot find symbols of `zeppelin-zengine` and goes to fail. However, I'm not sure that CI only recompiles changed files. I will look into it, and tell you if I get some more information. (CI was green before ð) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1630: [ZEPPELIN-1629] Enable renaming folder from the main p...
Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/1630 @tae-jun And one more thing, it would be better to keep consistency between `Note` and `Notebook`(combination of several notes). I pushed one commit to your branch, could you please take a look https://github.com/tae-jun/zeppelin/pull/1? It will be shown when user rename the folder(I removed `notebook`): https://cloud.githubusercontent.com/assets/10060731/20461892/d857a00e-af0c-11e6-92de-095215062fdd.png";> And then user rename the note: https://cloud.githubusercontent.com/assets/10060731/20461895/efdaa4b0-af0c-11e6-904c-667f6bcc82cc.png";> And also when user create a note, I changed `Example: NoteDir1/Notebook1` -> `NoteDir1/Note1` https://cloud.githubusercontent.com/assets/10060731/20461899/04f7cd78-af0d-11e6-97a8-825b1fec1932.png";> --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1630: [ZEPPELIN-1629] Enable renaming folder from the main p...
Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/1630 @tae-jun It works well when I tried to rename folder name. And I think It's good idea to let user know which notes that he don't have permission exactly. Thanks :) But currently CI is failed with below compilation error. Could you take a look again? ``` [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /home/travis/build/apache/zeppelin/zeppelin-server/src/main/java/org/apache/zeppelin/socket/NotebookServer.java:[774,5] cannot find symbol symbol: class Folder location: class org.apache.zeppelin.socket.NotebookServer [INFO] 1 error ``` --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
