[GitHub] zeppelin issue #1393: [ZEPPELIN-1142] Zeppelin allows two users to simultane...
Github user kavinkumarks commented on the issue: https://github.com/apache/zeppelin/pull/1393 Could someone else have a look at this and merge if everything is okay? Thanks, Kavin MailTo: kavin.ku...@imaginea.com --- 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 #1420: [ZEPPELIN-1421] Fix dead link in docs/README.md
Github user kavinkumarks commented on the issue: https://github.com/apache/zeppelin/pull/1420 @AhyoungRyu the changes look good! Thanks, Kavin MailTo: kavin.ku...@imaginea.com --- 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 #1424: [ZEPPELIN-1426] User aware storage sync
GitHub user khalidhuseynov opened a pull request: https://github.com/apache/zeppelin/pull/1424 [ZEPPELIN-1426] User aware storage sync ### What is this PR for? This is to make storage layer sync function aware of the user ### What type of PR is it? Improvement ### Todos * [x] - change function and test ### What is the Jira issue? [ZEPPELIN-1426](https://issues.apache.org/jira/browse/ZEPPELIN-1426) ### How should this be tested? corresponding storage layer tests should pass ### 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/khalidhuseynov/incubator-zeppelin storage/sync-with-subject Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1424.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 #1424 commit 7cc84557327306e572cdb035dae904a4139abbc2 Author: Khalid Huseynov Date: 2016-09-12T05:41:01Z propagate subject to sync() --- 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-1426) Pass subject user to storage sync mechanism
Khalid Huseynov created ZEPPELIN-1426: - Summary: Pass subject user to storage sync mechanism Key: ZEPPELIN-1426 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1426 Project: Zeppelin Issue Type: Improvement Components: zeppelin-zengine Reporter: Khalid Huseynov Fix For: 0.7.0 Although storage layer is aware of user (subject), the sync mechanism was unaware of it so far. So we need to propagate subject there as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] zeppelin pull request #1404: ZEPPELIN-1411. UDF with pyspark not working - o...
GitHub user zjffdu reopened a pull request: https://github.com/apache/zeppelin/pull/1404 ZEPPELIN-1411. UDF with pyspark not working - object has no attribute 'parseDataType' ### What is this PR for? The root cause is that SQLContext's signature changes in spark 2.0. Spark 1.6 ``` def __init__(self, sparkContext, sqlContext=None): ``` Spark 2.0 ``` def __init__(self, sparkContext, sparkSession=None, jsqlContext=None): ``` So we need to create SQLContext using named parameters, otherwise it would take intp.getSQLContext() as sparkSession which cause the issue. ### What type of PR is it? [Bug Fix] ### Todos * [ ] - Task ### What is the Jira issue? * https://issues.apache.org/jira/browse/ZEPPELIN-1411 ### How should this be tested? Tested using the example code in ZEPPELIN-1411. ### Screenshots (if appropriate) ![image](https://cloud.githubusercontent.com/assets/164491/18260139/9bd702c0-741d-11e6-8b23-946c38a794c3.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/zjffdu/zeppelin ZEPPELIN-1411 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1404.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 #1404 commit ae12ea03737d943ee20ac6398346852046c260d4 Author: Jeff Zhang Date: 2016-09-06T02:26:05Z ZEPPELIN-1411. UDF with pyspark not working - object has no attribute 'parseDataType' commit 632f1481c8ec6c9bc818e77f2663f0980be4446b Author: Jeff Zhang Date: 2016-09-09T06:21:37Z add unit test --- 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 #1404: ZEPPELIN-1411. UDF with pyspark not working - o...
Github user zjffdu closed the pull request at: https://github.com/apache/zeppelin/pull/1404 --- 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 #1423: ZEPPELIN-1425. sparkr.zip is not distributed to execut...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/1423 @Leemoonsoo Please help 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 pull request #1423: ZEPPELIN-1425. sparkr.zip is not distributed to...
GitHub user zjffdu opened a pull request: https://github.com/apache/zeppelin/pull/1423 ZEPPELIN-1425. sparkr.zip is not distributed to executors ### What is this PR for? sparkr.zip is not distrubuted to executor, so any sparkR job that requrie R daemon in executor will fail. This PR would add sparkr.zip into `spark.yarn.dist.archives`. ### What type of PR is it? [Bug Fix] ### Todos * [ ] - Task ### What is the Jira issue? * https://issues.apache.org/jira/browse/ZEPPELIN-1425 ### How should this be tested? Run the following code ``` %spark.r df <- createDataFrame(sqlContext, mtcars) showDF(df) ``` ### Screenshots (if appropriate) ![image](https://cloud.githubusercontent.com/assets/164491/18423112/6f7a75de-78d4-11e6-9d0b-ab05d41e3bfb.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/zjffdu/zeppelin ZEPPELIN-1425 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1423.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 #1423 commit 145a8dcf54fd325bdbc49568fcd69b73987ee516 Author: Jeff Zhang Date: 2016-09-12T01:51:06Z ZEPPELIN-1425. sparkr.zip is not distributed to executors --- 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-1425) sparkr.zip is not distributed to executors
Jeff Zhang created ZEPPELIN-1425: Summary: sparkr.zip is not distributed to executors Key: ZEPPELIN-1425 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1425 Project: Zeppelin Issue Type: Bug Affects Versions: 0.6.1 Reporter: Jeff Zhang Assignee: Jeff Zhang So if R daemon is required in executor, the R script will fail. How to reproduce it {code} df <- createDataFrame(sqlContext, mtcars) showDF(df) {code} Exception in executor side: {noformat} 10:16:20,024 INFO org.apache.spark.storage.memory.MemoryStore:54 - Block broadcast_1 stored as values in memory (estimated size 14.2 KB, free 366.3 MB) 10:16:21,018 INFO org.apache.spark.api.r.BufferedStreamThread:54 - Fatal error: cannot open file '/Users/jzhang/Temp/hadoop_tmp/nm-local-dir/usercache/jzhang/appcache/application_1473129941656_0037/container_1473129941656_0037_01_02/sparkr/SparkR/worker/daemon.R': No such file or directory 10:16:31,023 ERROR org.apache.spark.executor.Executor:91 - Exception in task 0.2 in stage 1.0 (TID 3) java.net.SocketTimeoutException: Accept timed out at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:404) at java.net.ServerSocket.implAccept(ServerSocket.java:545) at java.net.ServerSocket.accept(ServerSocket.java:513) at org.apache.spark.api.r.RRunner$.createRWorker(RRunner.scala:367) at org.apache.spark.api.r.RRunner.compute(RRunner.scala:69) at org.apache.spark.api.r.BaseRRDD.compute(RRDD.scala:49) {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] zeppelin pull request #1359: [ZEPPELIN-966] job manager change information c...
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/1359 --- 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 #1358: [ZEPPELIN-1365] Error of Zeppelin Application in devel...
Github user astroshim commented on the issue: https://github.com/apache/zeppelin/pull/1358 Sorry maybe it's my mistake to set jira version. --- 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-1424) ZeppelinContext.show() fails to display Datasets of custom classes
Sami Jaktholm created ZEPPELIN-1424: --- Summary: ZeppelinContext.show() fails to display Datasets of custom classes Key: ZEPPELIN-1424 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1424 Project: Zeppelin Issue Type: Bug Affects Versions: 0.7.0 Environment: Spark 2.0.0 Reporter: Sami Jaktholm Run the following code in Zeppelin Spark interpreter: {code:java} case class Test(key: String, value: String) val data = spark.createDataset(Seq( Test("k1", "v1"), Test("k2", "v2") )) z.show(data) {code} ...and you get the following exception: {noformat} org.apache.zeppelin.interpreter.InterpreterException: java.lang.NoSuchMethodException: Test.isNullAt(int) at org.apache.zeppelin.spark.ZeppelinContext.showDF(ZeppelinContext.java:271) at org.apache.zeppelin.spark.ZeppelinContext.show(ZeppelinContext.java:191) at org.apache.zeppelin.spark.ZeppelinContext.show(ZeppelinContext.java:153) ... 46 elided Caused by: java.lang.NoSuchMethodException: Test.isNullAt(int) at java.lang.Class.getMethod(Class.java:1786) at org.apache.zeppelin.spark.ZeppelinContext.showDF(ZeppelinContext.java:254) ... 48 more {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)