[GitHub] zeppelin issue #2372: [ZEPPELIN-2581] Shell ansi codes
Github user DrIgor commented on the issue: https://github.com/apache/zeppelin/pull/2372 I am not sure If themes should be shell interpreter feature. Maybe we can provide themes for every interpreter's text output? highlight.js should be used for input, not output. Output already contains information about colors and text styles --- 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 #2376: Branch 0.7
Github user soralee commented on the issue: https://github.com/apache/zeppelin/pull/2376 Hi, @simulight. If you want to improve zeppelin about your idea, could you create a JIRA ticket? And, this branch is fault. could you close this PR, please? --- 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 #2369: [ZEPPELIN-2591] Show user info in spark job descriptio...
Github user karuppayya commented on the issue: https://github.com/apache/zeppelin/pull/2369 @felixcheung Thanks for the feedback. Not sure if i got your question. I will try to elaborate more on the change The userinfo will give a picture of what is run/being run by whom and its duration, in the spark application.(Currently, we display **zeppelin**) The spark web UI will list all jobs, with this user information. --- 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 #2376: Branch 0.7
GitHub user simulight opened a pull request: https://github.com/apache/zeppelin/pull/2376 Branch 0.7 request for supporting insert iframe of one paragraph to the other paragraph, this is very useful to increase the reusement and integration of paragraphs . You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/zeppelin branch-0.7 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/2376.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 #2376 commit d91b310cbb985eac1e12ab9528a3be9e8e1b834c Author: Prabhjyot SinghDate: 2017-01-07T12:37:00Z [ZEPPELIN-1906] Use multiple InterpreterResult for displaying multiple JDBC queries ### What is this PR for? Use multiple InterpreterResult for displaying multiple JDBC queries. IMO since other sql editors allows to execute multiple sql separated with ";" and ours display mechanism being more powerful, hence, it should also allow the same. ### What type of PR is it? [Improvement] ### What is the Jira issue? * [ZEPPELIN-1906](https://issues.apache.org/jira/browse/ZEPPELIN-1906) ### How should this be tested? Try running following in a paragraph (with Postgres setting) and check for output. ``` %jdbc create table test_temp_table (id int); select column_name, data_type, character_maximum_length from INFORMATION_SCHEMA.COLUMNS where table_name = 'test_temp_table'; SELECT table_name FROM information_schema.tables WHERE table_schema = 'public'; drop table test_temp_table; SELECT table_name FROM information_schema.tables WHERE table_schema = 'public'; ``` ### Screenshots (if appropriate) ### Questions: * Does the licenses files need update? N/A * Is there breaking changes for older versions? N/A * Does this needs documentation? N/A Author: Prabhjyot Singh Closes #1845 from prabhjyotsingh/ZEPPELIN-1906 and squashes the following commits: b27352a [Prabhjyot Singh] on error show previous output. f9fd5c6 [Prabhjyot Singh] allow last query to be without ";" b3e742e [Prabhjyot Singh] fixing checkstyle-fail-build ac4663d [Prabhjyot Singh] add block comment f3da37f [Prabhjyot Singh] replace regex with slightly better logic. e6727b5 [Prabhjyot Singh] add testcase for spliting sql. c096e76 [Prabhjyot Singh] remove extra empty lines e675190 [Prabhjyot Singh] user same connection instead of creating new everytime f5ab796 [Prabhjyot Singh] Use multiple InterpreterResult for displaying multiple JDBC queries (cherry picked from commit 8464971c7aab0734f96d0a5a11d842b8e595324a) Signed-off-by: Prabhjyot Singh commit b8637f5e5fa4aab8859e6bc90fa7886ba9157b24 Author: Alexander Shoshin Date: 2017-01-11T08:45:31Z [ZEPPELIN-1787] Add an example of Flink Notebook ### What is this PR for? This PR will add an example of batch processing with Flink to Zeppelin tutorial notebooks. There are no any Flink notebooks in the tutorial at the moment. ### What type of PR is it? Improvement ### What is the Jira issue? [ZEPPELIN-1787](https://issues.apache.org/jira/browse/ZEPPELIN-1787) ### How should this be tested? You should open `Using Flink for batch processing` notebook from the `Zeppelin Tutorial` folder and run all paragraphs one by one ### Questions: * Does the licenses files need update? - **no** * Is there breaking changes for older versions? - **no** * Does this needs documentation? - **no** Author: Alexander Shoshin Closes #1758 from AlexanderShoshin/ZEPPELIN-1787 and squashes the following commits: 83cbffb [Alexander Shoshin] remove localhost url 5255e17 [Alexander Shoshin] Merge branch 'master' into ZEPPELIN-1787 0b9df56 [Alexander Shoshin] add a link for this notebook to Zeppelin documentation 593c47d [Alexander Shoshin] convert notebook to 0.7.0 format 9013620 [Alexander Shoshin] convert notebook to 0.6.2 format fe2a39e [Alexander Shoshin] add download instruction, change "wget" to "curl" f64b60a [Alexander Shoshin] [ZEPPELIN-1787] Add an example of Flink Notebook (cherry picked from commit 0da08d1d726129f6b684c99b1af8802907475d8a) Signed-off-by: ahyoungryu commit 6a15e7bf30876005b79f7593e02d5a4dc9f691d2 Author: Jeff Zhang Date: 2017-01-11T07:22:19Z ZEPPELIN-1867. Update document for pig interpreter and add one sample note ### What is this PR for? * Minor update for pig interpreter * Add one sample
[GitHub] zeppelin issue #2375: [ZEPPELIN-2527] Use thin (normal) cursor.
Github user 1ambda commented on the issue: https://github.com/apache/zeppelin/pull/2375 @zjffdu Could you help review this? --- 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-2600) Auto complete for available magics. (interpreter names)
Hoon Park created ZEPPELIN-2600: --- Summary: Auto complete for available magics. (interpreter names) Key: ZEPPELIN-2600 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2600 Project: Zeppelin Issue Type: Improvement Components: front-end Reporter: Hoon Park Auto complete for available magics. (interpreter names) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] zeppelin pull request #2375: [ZEPPELIN-2527] Use thin (normal) cursor.
GitHub user 1ambda opened a pull request: https://github.com/apache/zeppelin/pull/2375 [ZEPPELIN-2527] Use thin (normal) cursor. ### What is this PR for? Previously, it's hard to recognize where (**before or after**) the cursor is since it's too thick. See the attached GIFs for comparison. These key bindings are still supported in the default mode. - `CTRL + P`, `CTRL+N`: go to next / previous line - `CTRL + F`, `CTRL+B`: go to next / previous letter - `CTRL + A`, `CTRL+E`: go to the beginning / end of the line ### What type of PR is it? [Improvement] ### Todos * [x] - Use default mode instead of emacs * [x] - Bind `CTRL + P` for OSX. ### What is the Jira issue? [ZEPPELIN-2527](https://issues.apache.org/jira/browse/ZEPPELIN-2527) ### How should this be tested? 1. Build: `mvn clean package -DskipTests;` 2. Open a paragraph. 2. Check the cursor ### Screenshots (if appropriate) Before ![image](https://cloud.githubusercontent.com/assets/4968473/26563706/0b2c9846-4511-11e7-9667-da4c28321429.png) ![2527_before](https://cloud.githubusercontent.com/assets/4968473/26563687/b7133c88-4510-11e7-9acc-0baea08f29fc.gif) After ![image](https://cloud.githubusercontent.com/assets/4968473/26563705/ff5809ce-4510-11e7-8697-831e90e9d5a2.png) ![2527_after](https://cloud.githubusercontent.com/assets/4968473/26563690/c1bcd982-4510-11e7-9032-eb5c4a28e976.gif) ### 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/1ambda/zeppelin ZEPPELIN-2527/cursor-in-editor-is-too-thick Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/2375.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 #2375 commit 069714580fcac676fba937a81fff5f96a4e9 Author: 1ambda <1am...@gmail.com> Date: 2017-05-29T23:09:28Z fix: Use default mode --- 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 #2371: [ZEPPELIN-2596] Improving documentation page
Github user 1ambda closed the pull request at: https://github.com/apache/zeppelin/pull/2371 --- 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 #2371: [ZEPPELIN-2596] Improving documentation page
GitHub user 1ambda reopened a pull request: https://github.com/apache/zeppelin/pull/2371 [ZEPPELIN-2596] Improving documentation page ### What is this PR for? Improving documentation page. Please check *TODO* and *Screenshots* sections for detail. The motivation is described in [the JIRA ticket](https://issues.apache.org/jira/browse/ZEPPELIN-2583) and discussion is ongoing on the mailing list. ### What type of PR is it? [Improvement | Documentation] ### Todos * [x] - improved the navbar style * [x] - improved the main page * [x] - re-organized content structure * [x] - added tutorial pages: `spark_with_zeppelin.md`, `python_with_zeppelin.md`, `sql_with_zeppelin.md` for overview * [x] - added `multi_user_support.md` page to provide overview * [x] - added the empty `interpreter_binding_mode` page. This will be handed in the different issue: [ZEPPELIN-2582](https://issues.apache.org/jira/browse/ZEPPELIN-2582) * [x] - added the empty `trouble_shooting` page. This can be filled in the following PRs. * [x] - added the empty `useful_developer_tools` page. This can be filled in the following PRs. ### What is the Jira issue? [ZEPPELIN-2596](https://issues.apache.org/jira/browse/ZEPPELIN-2596) ### How should this be tested? 1. checkout 2. `cd docs` 3. `bundle install` (make sure that you have ruby 2.1.0+ and bundle) 4. `bundle exec jekyll serve --watch` 5. open `localhost:4000` ### Screenshots (if appropriate) better navbar: before ![2596_before_nav](https://cloud.githubusercontent.com/assets/4968473/26542353/89004e7a-4494-11e7-89c0-28d608f5f375.gif) better navbar: after ![2596_after_nav](https://cloud.githubusercontent.com/assets/4968473/26542356/8bfb7b90-4494-11e7-9979-0bcaef8ba97b.gif) improved main page: before ![2596_before_main](https://cloud.githubusercontent.com/assets/4968473/26542358/8f35b0be-4494-11e7-8a6c-e74ec52fc384.gif) improved main page: after ![2596_after_main](https://cloud.githubusercontent.com/assets/4968473/26542366/93b333c8-4494-11e7-981f-3f7b4545868f.gif) organized content structure: before ![2596_before_content](https://cloud.githubusercontent.com/assets/4968473/26542398/ad81ac26-4494-11e7-9a17-70dff41396fb.gif) organized content structure: after ![2596_after_content](https://cloud.githubusercontent.com/assets/4968473/26542403/b0a42ad2-4494-11e7-8bd3-8a5bd194c6af.gif) ### Questions: * Does the licenses files need update? - NO * Is there breaking changes for older versions? - NO * Does this needs documentation? - related with docs You can merge this pull request into a Git repository by running: $ git pull https://github.com/1ambda/zeppelin updating-version-doc Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/2371.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 #2371 commit bb44cc5419785433fb5170334293862322864d68 Author: 1ambda <1am...@gmail.com> Date: 2017-05-25T02:22:51Z commit commit a5d4b4167c0bd6cacff2de63388c3dd7bbac0da6 Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T01:21:42Z feat: Style collapsed nav for mobile browser commit a89be9dc1bb39420f65509a7a929fb712373a1db Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T01:24:52Z fix: Add RL padding for mobile browser commit 1d55a60715f6e5148ca7d9fe088a12754f9488f9 Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T01:29:02Z fix: Better image display in index.md commit 50aad6ba09dc1aa52f12c8969ec7aa1061a3c79f Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T05:13:44Z feat: Hide version in navbar when md commit 111bdbaf0eeb94ef64f068b2195e00e09bc593bb Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T05:40:20Z feat: Update doc section names commit dc58dcdc5b975f330cd23faf331c58a955a0952a Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T06:15:03Z fix: doens't display navbar version in small commit ccfb100920c37ef4bc60209a718c257803499ff3 Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T08:26:01Z feat: Change URLs in nav, index commit b75903aefcd90bfc55a90fe4a569e1bb6394fb31 Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T08:46:43Z fix: Add missing links commit fd2e6c7d33976e8b8c0cd591470db5162083a364 Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T09:02:25Z feat: rename /quickstart commit 6b393a93eb96a1d199fd456ec7637a1d33ab9fbe Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T13:02:20Z feat: Add docs/usage commit 97aea24860a741647f55cb1a18a31b63eca67a8b Author: 1ambda <1am...@gmail.com> Date:
[GitHub] zeppelin pull request #2371: [ZEPPELIN-2596] Improving documentation page
GitHub user 1ambda reopened a pull request: https://github.com/apache/zeppelin/pull/2371 [ZEPPELIN-2596] Improving documentation page ### What is this PR for? Improving documentation page. Please check *TODO* and *Screenshots* sections for detail. The motivation is described in [the JIRA ticket](https://issues.apache.org/jira/browse/ZEPPELIN-2583) and discussion is ongoing on the mailing list. ### What type of PR is it? [Improvement | Documentation] ### Todos * [x] - improved the navbar style * [x] - improved the main page * [x] - re-organized content structure * [x] - added tutorial pages: `spark_with_zeppelin.md`, `python_with_zeppelin.md`, `sql_with_zeppelin.md` for overview * [x] - added `multi_user_support.md` page to provide overview * [x] - added the empty `interpreter_binding_mode` page. This will be handed in the different issue: [ZEPPELIN-2582](https://issues.apache.org/jira/browse/ZEPPELIN-2582) * [x] - added the empty `trouble_shooting` page. This can be filled in the following PRs. * [x] - added the empty `useful_developer_tools` page. This can be filled in the following PRs. ### What is the Jira issue? [ZEPPELIN-2596](https://issues.apache.org/jira/browse/ZEPPELIN-2596) ### How should this be tested? 1. checkout 2. `cd docs` 3. `bundle install` (make sure that you have ruby 2.1.0+ and bundle) 4. `bundle exec jekyll serve --watch` 5. open `localhost:4000` ### Screenshots (if appropriate) better navbar: before ![2596_before_nav](https://cloud.githubusercontent.com/assets/4968473/26542353/89004e7a-4494-11e7-89c0-28d608f5f375.gif) better navbar: after ![2596_after_nav](https://cloud.githubusercontent.com/assets/4968473/26542356/8bfb7b90-4494-11e7-9979-0bcaef8ba97b.gif) improved main page: before ![2596_before_main](https://cloud.githubusercontent.com/assets/4968473/26542358/8f35b0be-4494-11e7-8a6c-e74ec52fc384.gif) improved main page: after ![2596_after_main](https://cloud.githubusercontent.com/assets/4968473/26542366/93b333c8-4494-11e7-981f-3f7b4545868f.gif) organized content structure: before ![2596_before_content](https://cloud.githubusercontent.com/assets/4968473/26542398/ad81ac26-4494-11e7-9a17-70dff41396fb.gif) organized content structure: after ![2596_after_content](https://cloud.githubusercontent.com/assets/4968473/26542403/b0a42ad2-4494-11e7-8bd3-8a5bd194c6af.gif) ### Questions: * Does the licenses files need update? - NO * Is there breaking changes for older versions? - NO * Does this needs documentation? - related with docs You can merge this pull request into a Git repository by running: $ git pull https://github.com/1ambda/zeppelin updating-version-doc Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/2371.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 #2371 commit bb44cc5419785433fb5170334293862322864d68 Author: 1ambda <1am...@gmail.com> Date: 2017-05-25T02:22:51Z commit commit a5d4b4167c0bd6cacff2de63388c3dd7bbac0da6 Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T01:21:42Z feat: Style collapsed nav for mobile browser commit a89be9dc1bb39420f65509a7a929fb712373a1db Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T01:24:52Z fix: Add RL padding for mobile browser commit 1d55a60715f6e5148ca7d9fe088a12754f9488f9 Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T01:29:02Z fix: Better image display in index.md commit 50aad6ba09dc1aa52f12c8969ec7aa1061a3c79f Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T05:13:44Z feat: Hide version in navbar when md commit 111bdbaf0eeb94ef64f068b2195e00e09bc593bb Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T05:40:20Z feat: Update doc section names commit dc58dcdc5b975f330cd23faf331c58a955a0952a Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T06:15:03Z fix: doens't display navbar version in small commit ccfb100920c37ef4bc60209a718c257803499ff3 Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T08:26:01Z feat: Change URLs in nav, index commit b75903aefcd90bfc55a90fe4a569e1bb6394fb31 Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T08:46:43Z fix: Add missing links commit fd2e6c7d33976e8b8c0cd591470db5162083a364 Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T09:02:25Z feat: rename /quickstart commit 6b393a93eb96a1d199fd456ec7637a1d33ab9fbe Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T13:02:20Z feat: Add docs/usage commit 97aea24860a741647f55cb1a18a31b63eca67a8b Author: 1ambda <1am...@gmail.com> Date:
[GitHub] zeppelin pull request #2371: [ZEPPELIN-2596] Improving documentation page
Github user 1ambda closed the pull request at: https://github.com/apache/zeppelin/pull/2371 --- 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. ---
Re: Permission denied: user=zeppelin while using %spark.pyspark interpreter in AWS EMR cluster
Seems to be with hdfs ACL - does the service user Zeppelin have access to your storage? From: BigData ConsultantSent: Friday, May 26, 2017 10:56:31 PM To: dev@zeppelin.apache.org; us...@zeppelin.apache.org Subject: Permission denied: user=zeppelin while using %spark.pyspark interpreter in AWS EMR cluster Hi Team, I have created pyspark structure streaming program and trying to execute in the Zeppelin notebook, I am getting the following error: Py4JJavaError: An error occurred while calling o191.start. : org.apache.hadoop.security.AccessControlException: Permission denied: user=zeppelin, access=WRITE, inode="/mnt/tmp/temporary-e0cf0f09-a6f4-44d6-9a72-324660085608/metadata":hdfs:hadoop:drwxr-xr-x I am using Zeppelin Notebook Version 0.7.1 in AWS EMR cluster. Help would be much appreciated. *Full stacktrace:* Traceback (most recent call last): File "/tmp/zeppelin_pyspark-8165971491474576109.py", line 349, in raise Exception(traceback.format_exc()) Exception: Traceback (most recent call last): File "/tmp/zeppelin_pyspark-8165971491474576109.py", line 342, in exec(code) File "", line 5, in File "/usr/lib/spark/python/pyspark/sql/streaming.py", line 816, in start return self._sq(self._jwrite.start()) File "/usr/lib/spark/python/lib/py4j-0.10.4-src.zip/py4j/java_gateway.py", line 1133, in __call__ answer, self.gateway_client, self.target_id, self.name) File "/usr/lib/spark/python/pyspark/sql/utils.py", line 63, in deco return f(*a, **kw) File "/usr/lib/spark/python/lib/py4j-0.10.4-src.zip/py4j/protocol.py", line 319, in get_return_value format(target_id, ".", name), value) Py4JJavaError: An error occurred while calling o191.start. : org.apache.hadoop.security.AccessControlException: Permission denied: user=zeppelin, access=WRITE, inode="/mnt/tmp/temporary-e0cf0f09-a6f4-44d6-9a72-324660085608/metadata":hdfs:hadoop:drwxr-xr-x at org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:320) at org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:292) at org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:213) at org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:190) at org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1728) at org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1712) at org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkAncestorAccess(FSDirectory.java:1695) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFileInternal(FSNamesystem.java:2515) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFileInt(FSNamesystem.java:2450) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFile(FSNamesystem.java:2334) at org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.create(NameNodeRpcServer.java:624) at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.create(ClientNamenodeProtocolServerSideTranslatorPB.java:397) at org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java) at org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616) at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:982) at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2049) at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2045) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:422) at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1698) at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2045) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106) at org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:73) at org.apache.hadoop.hdfs.DFSOutputStream.newStreamForCreate(DFSOutputStream.java:1653) at org.apache.hadoop.hdfs.DFSClient.create(DFSClient.java:1689) at org.apache.hadoop.hdfs.DFSClient.create(DFSClient.java:1624) at org.apache.hadoop.hdfs.DistributedFileSystem$7.doCall(DistributedFileSystem.java:448) at org.apache.hadoop.hdfs.DistributedFileSystem$7.doCall(DistributedFileSystem.java:444) at org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81) at org.apache.hadoop.hdfs.DistributedFileSystem.create(DistributedFileSystem.java:459) at
[GitHub] zeppelin issue #2372: [ZEPPELIN-2581] Shell ansi codes
Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/2372 Cool! I'd love the dark theme, but I don't think we should force this onto users? --- 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 #2371: [ZEPPELIN-2596] Improving documentation page
Github user 1ambda commented on the issue: https://github.com/apache/zeppelin/pull/2371 Thanks! @AhyoungRyu :) --- 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 #2372: [ZEPPELIN-2581] Shell ansi codes
Github user 1ambda commented on the issue: https://github.com/apache/zeppelin/pull/2372 Can we apply some theme to the output? For example, Solarized dark theme + shell syntax highlight. ![image](https://cloud.githubusercontent.com/assets/4968473/26560133/0d800262-44ef-11e7-879f-5f46e0317f57.png) AFAIK, we are using highlight.js https://github.com/apache/zeppelin/blob/master/zeppelin-web/bower.json#L27 --- 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 #2354: Allow group/role based authentication using LdapRealm ...
Github user khalidhuseynov commented on the issue: https://github.com/apache/zeppelin/pull/2354 Hi @FRosner, I think best way would be to help review and test #932 first. i was going to do it as well, but didn't get much time recently. thanks for help, and i'll check it this week too. --- 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 #2374: [ZEPPELIN-2593] Add storage settings to persist...
GitHub user khalidhuseynov opened a pull request: https://github.com/apache/zeppelin/pull/2374 [ZEPPELIN-2593] Add storage settings to persist on commit ### What is this PR for? adding settings to storage layer to let user choose to persist continuously or only on commits ### What type of PR is it? Improvement | Feature ### Todos * [x] - add initial flow * [ ] - address for each storage class ### What is the Jira issue? [ZEPPELIN-2593](https://issues.apache.org/jira/browse/ZEPPELIN-2593) ### How should this be tested? TBD ### Screenshots (if appropriate) TBD ### 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/khalidhuseynov/zeppelin feat/ZEPPELIN-2593 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/2374.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 #2374 commit a8cccf6e6cf5b92d8d7e142bd4909b5a15e087a5 Author: Khalid HuseynovDate: 2017-05-29T07:48:06Z initial impl through env commit fa6a60f40929b3682d3e790545e07220c3a1acbf Author: Khalid Huseynov Date: 2017-05-29T16:45:52Z add setting from UI initial --- 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 #2371: [ZEPPELIN-2596] Improving documentation page
Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/2371 Cool! --- 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 #2373: [ZEPPELIN-2598] Securing Zeppelin with OpenID C...
GitHub user andreaTP opened a pull request: https://github.com/apache/zeppelin/pull/2373 [ZEPPELIN-2598] Securing Zeppelin with OpenID Connect ### What is this PR for? Integrating Open ID connect login into Zeppelin leveraging Shiro(already present) and Pac4J( that needs to be in the classpath). Modifications done here should not affect any existing mechanisms but simply integrates and enable new once. ### What type of PR is it? [Improvement] ### What is the Jira issue? [ZEPPELIN-2598] ### 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/nokia/zeppelin keycloak Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/2373.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 #2373 commit 4ce91213eedf7c6b9eee1339290fbff1818989bd Author: andreaDate: 2017-05-16T16:33:41Z Enabling authentication with OpenId connect --- 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-2598) Securing Zeppelin with OpenID Connect
Andrea Peruffo created ZEPPELIN-2598: Summary: Securing Zeppelin with OpenID Connect Key: ZEPPELIN-2598 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2598 Project: Zeppelin Issue Type: Improvement Reporter: Andrea Peruffo Priority: Minor We want to enable user to login to all applications on the cluster using the same mechanism. In this case OpenID Connect is the choice and it plugs (almost) smoothly with shiro thanks to Pac4J project. This will also open the road to other authentication mechanisms to be plugged in. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] zeppelin pull request #2372: [ZEPPELIN-2581] Shell ansi codes
GitHub user DrIgor opened a pull request: https://github.com/apache/zeppelin/pull/2372 [ZEPPELIN-2581] Shell ansi codes ### What is this PR for? Support ANSI escape codes for colors in shell interpreter output ### What type of PR is it? [Improvement] ### What is the Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-2581 ### Screenshots (if appropriate) ![image](https://cloud.githubusercontent.com/assets/2759002/26547220/90c162f2-4476-11e7-9fa4-4b023c1a415f.png) ### 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/DrIgor/zeppelin shell-ansi-codes Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/2372.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 #2372 commit 0804a3228c0aeec7e44d588168794d291bdbf25f Author: Igor DrozdovDate: 2017-05-26T10:58:53Z Support ANSI colors in shell outputs commit 28f5ec53d863d731f7c0d7745bc40b7ea68facb2 Author: Igor Drozdov Date: 2017-05-29T07:53:50Z Provide output in tests --- 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-2597) improving Main Hompage (zeppelin.apache.org)
Sora Lee created ZEPPELIN-2597: -- Summary: improving Main Hompage (zeppelin.apache.org) Key: ZEPPELIN-2597 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2597 Project: Zeppelin Issue Type: Sub-task Reporter: Sora Lee Assignee: Sora Lee -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] zeppelin issue #2354: Allow group/role based authentication using LdapRealm ...
Github user FRosner commented on the issue: https://github.com/apache/zeppelin/pull/2354 Hi @khalidhuseynov! Thanks for looking into it. Is there a way to support you? --- 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 #2371: [ZEPPELIN-2596] Improving documentation page
GitHub user 1ambda opened a pull request: https://github.com/apache/zeppelin/pull/2371 [ZEPPELIN-2596] Improving documentation page ### What is this PR for? Improving documentation page. Please check *TODO* and *Screenshots* sections for detail. The motivation is described in [the JIRA ticket](https://issues.apache.org/jira/browse/ZEPPELIN-2583) and discussion is ongoing on the mailing list. ### What type of PR is it? [Improvement | Documentation] ### Todos * [x] - improved the navbar style * [x] - improved the main page * [x] - re-organized content structure * [x] - added tutorial pages: `spark_with_zeppelin.md`, `python_with_zeppelin.md`, `sql_with_zeppelin.md` for overview * [x] - added `multi_user_support.md` page to provide overview * [x] - added the empty `interpreter_binding_mode` page. This will be handed in the different issue: [ZEPPELIN-2582](https://issues.apache.org/jira/browse/ZEPPELIN-2582) ### What is the Jira issue? [ZEPPELIN-2596](https://issues.apache.org/jira/browse/ZEPPELIN-2596) ### How should this be tested? 1. checkout 2. `cd docs` 3. `bundle install` (make sure that you have ruby 2.1.0+ and bundle) 4. `bundle exec jekyll serve --watch` 5. open `localhost:4000` ### Screenshots (if appropriate) better navbar: before ![2596_before_nav](https://cloud.githubusercontent.com/assets/4968473/26542353/89004e7a-4494-11e7-89c0-28d608f5f375.gif) better navbar: after ![2596_after_nav](https://cloud.githubusercontent.com/assets/4968473/26542356/8bfb7b90-4494-11e7-9979-0bcaef8ba97b.gif) improved main page: before ![2596_before_main](https://cloud.githubusercontent.com/assets/4968473/26542358/8f35b0be-4494-11e7-8a6c-e74ec52fc384.gif) improved main page: after ![2596_after_main](https://cloud.githubusercontent.com/assets/4968473/26542366/93b333c8-4494-11e7-981f-3f7b4545868f.gif) organized content structure: before ![2596_before_content](https://cloud.githubusercontent.com/assets/4968473/26542398/ad81ac26-4494-11e7-9a17-70dff41396fb.gif) organized content structure: after ![2596_after_content](https://cloud.githubusercontent.com/assets/4968473/26542403/b0a42ad2-4494-11e7-8bd3-8a5bd194c6af.gif) ### Questions: * Does the licenses files need update? - NO * Is there breaking changes for older versions? - NO * Does this needs documentation? - related with docs You can merge this pull request into a Git repository by running: $ git pull https://github.com/1ambda/zeppelin updating-version-doc Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/2371.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 #2371 commit bb44cc5419785433fb5170334293862322864d68 Author: 1ambda <1am...@gmail.com> Date: 2017-05-25T02:22:51Z commit commit a5d4b4167c0bd6cacff2de63388c3dd7bbac0da6 Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T01:21:42Z feat: Style collapsed nav for mobile browser commit a89be9dc1bb39420f65509a7a929fb712373a1db Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T01:24:52Z fix: Add RL padding for mobile browser commit 1d55a60715f6e5148ca7d9fe088a12754f9488f9 Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T01:29:02Z fix: Better image display in index.md commit 50aad6ba09dc1aa52f12c8969ec7aa1061a3c79f Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T05:13:44Z feat: Hide version in navbar when md commit 111bdbaf0eeb94ef64f068b2195e00e09bc593bb Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T05:40:20Z feat: Update doc section names commit dc58dcdc5b975f330cd23faf331c58a955a0952a Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T06:15:03Z fix: doens't display navbar version in small commit ccfb100920c37ef4bc60209a718c257803499ff3 Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T08:26:01Z feat: Change URLs in nav, index commit b75903aefcd90bfc55a90fe4a569e1bb6394fb31 Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T08:46:43Z fix: Add missing links commit fd2e6c7d33976e8b8c0cd591470db5162083a364 Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T09:02:25Z feat: rename /quickstart commit 6b393a93eb96a1d199fd456ec7637a1d33ab9fbe Author: 1ambda <1am...@gmail.com> Date: 2017-05-26T13:02:20Z feat: Add docs/usage commit 97aea24860a741647f55cb1a18a31b63eca67a8b Author: 1ambda <1am...@gmail.com> Date: 2017-05-27T01:03:40Z fix: URLs in quickstart commit 8b079a06614c09d064d60cdd4749f0ab4e9c0428 Author: 1ambda <1am...@gmail.com> Date: 2017-05-27T01:03:52Z fix: URLs in setup commit
[jira] [Created] (ZEPPELIN-2596) Improving Documentation Page
Hoon Park created ZEPPELIN-2596: --- Summary: Improving Documentation Page Key: ZEPPELIN-2596 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2596 Project: Zeppelin Issue Type: Sub-task Components: documentation Reporter: Hoon Park Fix For: 0.8.0 sub-issue of ZEPPELIN-2583 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] zeppelin issue #2370: change the spark version of dockerfile
Github user 1ambda commented on the issue: https://github.com/apache/zeppelin/pull/2370 Hi @sven0726, Thanks for the contribution. I added a comment. - This pr is not related with CI, but if you want to modify code you need to setup travis CI for your zeppelin fork. --- 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 #2370: change the spark version of dockerfile
GitHub user sven0726 opened a pull request: https://github.com/apache/zeppelin/pull/2370 change the spark version of dockerfile ### 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? Outline the 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/sven0726/zeppelin master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/2370.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 #2370 --- 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. ---