[jira] [Created] (ZEPPELIN-4007) Travis CI is broken for branch-0.8

2019-02-13 Thread Jeff Zhang (JIRA) 
Jeff Zhang created ZEPPELIN-4007:


 Summary: Travis CI is broken for branch-0.8
 Key: ZEPPELIN-4007
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4007
 Project: Zeppelin
  Issue Type: Bug
Reporter: Jeff Zhang






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] felixcheung commented on a change in pull request #3306: [ZEPPELIN-4001] zeppelin-interpreter-integration is ignored due to wrong folder structure

2019-02-13 Thread GitBox 
felixcheung commented on a change in pull request #3306: [ZEPPELIN-4001] 
zeppelin-interpreter-integration is ignored due to wrong folder structure
URL: https://github.com/apache/zeppelin/pull/3306#discussion_r256712783
 
 

 ##
 File path: .travis.yml
 ##
 @@ -37,9 +37,13 @@ addons:
 - r-source
 - sourceline: 'deb http://cran.rstudio.com/bin/linux/ubuntu trusty/'
   key_url: 
'keyserver.ubuntu.com/pks/lookup?op=get=0x51716619E084DAB9'
+- r-packages-trusty
+- mysql-5.7-trusty
 packages:
 - r-base
 - r-base-dev
+- mysql-server
+- mysql-client
 
 Review comment:
   why is this needed?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] felixcheung commented on a change in pull request #3306: [ZEPPELIN-4001] zeppelin-interpreter-integration is ignored due to wrong folder structure

2019-02-13 Thread GitBox 
felixcheung commented on a change in pull request #3306: [ZEPPELIN-4001] 
zeppelin-interpreter-integration is ignored due to wrong folder structure
URL: https://github.com/apache/zeppelin/pull/3306#discussion_r256712964
 
 

 ##
 File path: 
spark/interpreter/src/main/java/org/apache/zeppelin/spark/SparkVersion.java
 ##
 @@ -86,7 +86,7 @@ public boolean isSpark2() {
   }
 
   public boolean isSecretSocketSupported() {
-return this.newerThanEquals(SPARK_2_3_1);
+return this.newerThanEquals(SPARK_2_3_1) || 
this.equals(SparkVersion.fromVersionString("2.1.2"));
 
 Review comment:
   I don't think we should hardcode this? why not newerThanEquals(SPARK_2_1_2)?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] felixcheung commented on a change in pull request #3306: [ZEPPELIN-4001] zeppelin-interpreter-integration is ignored due to wrong folder structure

2019-02-13 Thread GitBox 
felixcheung commented on a change in pull request #3306: [ZEPPELIN-4001] 
zeppelin-interpreter-integration is ignored due to wrong folder structure
URL: https://github.com/apache/zeppelin/pull/3306#discussion_r256713344
 
 

 ##
 File path: .travis.yml
 ##
 @@ -87,35 +91,43 @@ matrix:
   dist: trusty
   env: PYTHON="3" SPARKR="true" SCALA_VER="2.10" PROFILE="-Pscala-2.10" 
BUILD_FLAG="install -DskipTests -DskipRat" TEST_FLAG="test -DskipRat" 
MODULES="-pl $(echo 
.,zeppelin-interpreter,zeppelin-interpreter-api,${INTERPRETERS} | sed 
's/!//g')" TEST_PROJECTS=""
 
-# Run ZeppelinSparkClusterTest & SparkIntegrationTest in one build would 
exceed the time limitation of travis, so running them separately
+# Run Spark integration test and unit test separately for each spark 
version
 
-# Integration test of spark interpreter with different spark versions 
under python2, only run ZeppelinSparkClusterTest. Also run spark unit test of 
spark 2.4.0 in this build. And run JdbcIntegrationTest here as well.
+# ZeppelinSparkClusterTest24, SparkIntegrationTest24, JdbcIntegrationTest, 
Unit test of Spark 2.4
 - sudo: required
   jdk: "oraclejdk8"
   dist: trusty
-  env: BUILD_PLUGINS="true" PYTHON="2" SCALA_VER="2.11" 
PROFILE="-Pspark-2.4 -Pscala-2.11 -Phadoop2 -Pintegration" SPARKR="true" 
BUILD_FLAG="install -DskipTests -DskipRat -am" TEST_FLAG="test -DskipRat -am" 
MODULES="-pl 
zeppelin-interpreter-integration,jdbc,spark/interpreter,spark/spark-dependencies"
 
TEST_PROJECTS="-Dtest=ZeppelinSparkClusterTest,JdbcIntegrationTest,org.apache.zeppelin.spark.*
 -DfailIfNoTests=false"
+  env: BUILD_PLUGINS="true" PYTHON="2" SCALA_VER="2.11" 
PROFILE="-Pspark-2.4 -Pscala-2.11 -Phadoop2 -Pintegration" SPARKR="true" 
BUILD_FLAG="install -DskipTests -DskipRat -am" TEST_FLAG="test -DskipRat -am" 
MODULES="-pl 
zeppelin-interpreter-integration,jdbc,zeppelin-web,spark/spark-dependencies" 
TEST_PROJECTS="-Dtest=ZeppelinSparkClusterTest24,SparkIntegrationTest24,JdbcIntegrationTest,org.apache.zeppelin.spark.*
 -DfailIfNoTests=false"
 
-# Integration test of spark interpreter with different spark versions 
under python3, only run SparkIntegrationTestPt1. Also run spark unit test of 
spark 2.3 in this build.
+# ZeppelinSparkClusterTest23, SparkIntegrationTest23, Unit test of Spark 
2.3
 - sudo: required
   jdk: "oraclejdk8"
   dist: trusty
-  env: BUILD_PLUGINS="true" PYTHON="3" SCALA_VER="2.11" 
PROFILE="-Pspark-2.3 -Pscala-2.11 -Phadoop2 -Pintegration" SPARKR="true" 
BUILD_FLAG="install -DskipTests -DskipRat -am" TEST_FLAG="test -DskipRat -am" 
MODULES="-pl 
zeppelin-interpreter-integration,spark/interpreter,spark/spark-dependencies" 
TEST_PROJECTS="-Dtest=SparkIntegrationTestPt1,org.apache.zeppelin.spark.* 
-DfailIfNoTests=false"
+  env: BUILD_PLUGINS="true" PYTHON="2" SCALA_VER="2.11" 
PROFILE="-Pspark-2.3 -Pscala-2.11 -Phadoop2 -Pintegration" SPARKR="true" 
BUILD_FLAG="install -DskipTests -DskipRat -am" TEST_FLAG="test -DskipRat -am" 
MODULES="-pl 
zeppelin-interpreter-integration,zeppelin-web,spark/spark-dependencies" 
TEST_PROJECTS="-Dtest=ZeppelinSparkClusterTest23,SparkIntegrationTest23,org.apache.zeppelin.spark.*
 -DfailIfNoTests=false"
 
-# Integration test of spark interpreter with different spark versions 
under python3, only run SparkIntegrationTestPt2. Also run spark unit test of 
spark 2.2 in this build.
+# ZeppelinSparkClusterTest22, SparkIntegrationTest22, Unit test of Spark 
2.2
 - sudo: required
   jdk: "oraclejdk8"
   dist: trusty
-  env: BUILD_PLUGINS="true" PYTHON="3" SCALA_VER="2.10" 
PROFILE="-Pspark-2.2 -Phadoop2 -Pscala-2.10 -Pintegration" SPARKR="true" 
BUILD_FLAG="install -DskipTests -DskipRat -am" TEST_FLAG="test -DskipRat -am" 
MODULES="-pl 
zeppelin-interpreter-integration,spark/interpreter,spark/spark-dependencies" 
TEST_PROJECTS="-Dtest=SparkIntegrationTestPt2,org.apache.zeppelin.spark.* 
-DfailIfNoTests=false"
+  env: BUILD_PLUGINS="true" PYTHON="3" SCALA_VER="2.11" 
PROFILE="-Pspark-2.2 -Pscala-2.11 -Phadoop2 -Pintegration" SPARKR="true" 
BUILD_FLAG="install -DskipTests -DskipRat -am" TEST_FLAG="test -DskipRat -am" 
MODULES="-pl 
zeppelin-interpreter-integration,zeppelin-web,spark/spark-dependencies" 
TEST_PROJECTS="-Dtest=ZeppelinSparkClusterTest22,SparkIntegrationTest22,org.apache.zeppelin.spark.*
 -DfailIfNoTests=false"
 
-# Test spark module for 2.1 with scala 2.10
-- jdk: "oraclejdk8"
+# ZeppelinSparkClusterTest21, SparkIntegrationTest21, Unit test of Spark 
2.1
+- sudo: required
+  jdk: "oraclejdk8"
   dist: trusty
-  env: PYTHON="2" SCALA_VER="2.10" PROFILE="-Pspark-2.1 -Phadoop2 
-Pscala-2.10" SPARKR="true" BUILD_FLAG="install -DskipTests -DskipRat -am" 
TEST_FLAG="test -DskipRat -am" MODULES="-pl 
spark/interpreter,spark/spark-dependencies" 
TEST_PROJECTS="-Dtest=org.apache.zeppelin.spark.*,org.apache.zeppelin.rinterpreter.*,org.apache.spark.api.r.*

[jira] [Created] (ZEPPELIN-4006) Restart Spark Interpreter programmatically

2019-02-13 Thread Ram (JIRA) 
Ram created ZEPPELIN-4006:
-

 Summary: Restart Spark Interpreter programmatically
 Key: ZEPPELIN-4006
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4006
 Project: Zeppelin
  Issue Type: Improvement
  Components: Interpreters
Affects Versions: 0.8.0
Reporter: Ram


We use Zeppelin in Isolated mode.

If a particular users Spark Context gets killed, there is no other way to 
restart the context other than restarting the Spark interpreter.

This affects other users as when restarting the spark interpreter kills other 
users applications as well.

Is there anyway a users spark context can be restarted for a particular user. 
For both %spark and %pyspark



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ZEPPELIN-4005) SparkRInterpreter is broken for spark 2.1.3 and 2.2.3

2019-02-13 Thread Jeff Zhang (JIRA) 
Jeff Zhang created ZEPPELIN-4005:


 Summary: SparkRInterpreter is broken for spark 2.1.3 and 2.2.3
 Key: ZEPPELIN-4005
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4005
 Project: Zeppelin
  Issue Type: New Feature
Affects Versions: 0.8.1, 0.9.0
Reporter: Jeff Zhang






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ZEPPELIN-4004) RemoteResource.invokeMethod() has broken

2019-02-13 Thread Lee moon soo (JIRA) 
Lee moon soo created ZEPPELIN-4004:
--

 Summary: RemoteResource.invokeMethod() has broken
 Key: ZEPPELIN-4004
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4004
 Project: Zeppelin
  Issue Type: Bug
Affects Versions: 0.8.1
Reporter: Lee moon soo
Assignee: Lee moon soo


RemoteResource is a representation of object in ResourcePool in Interpreter 
running on another process.

RemoteResource provides a invokeMethod() to call method of an object remotely, 
which is not working now.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ZEPPELIN-4003) Opening "[" bracket does not work

2019-02-13 Thread Henri Chabert (JIRA) 
Henri Chabert created ZEPPELIN-4003:
---

 Summary: Opening "[" bracket does not work
 Key: ZEPPELIN-4003
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4003
 Project: Zeppelin
  Issue Type: Bug
  Components: python-interpreter
Affects Versions: 0.8.1
Reporter: Henri Chabert


Hello team, 

 

I have a weird problem on Zeppelin notebook, I have just started to use it and 
I realized that the key "[" doesn't work while it works in every of my other 
apps, so it is not a problem with my keyboard. Even stranger, the key "]" 
works, which mean that it is not an issue about special characters.

 

Would you have any idea where this problem can come from please ?

 

Thanks



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ZEPPELIN-4002) Unable to resolve full interpreter

2019-02-13 Thread Demyan Mysakovets (JIRA) 
Demyan Mysakovets created ZEPPELIN-4002:
---

 Summary: Unable to resolve full interpreter
 Key: ZEPPELIN-4002
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4002
 Project: Zeppelin
  Issue Type: Bug
  Components: Interpreters
Affects Versions: 0.8.1, 0.8.0
Reporter: Demyan Mysakovets
 Attachments: screen1.png, screen2.png

Zeppelin is unable to resolve full interpreter name at the beginning of 
paragraph. It doesn't resolve anything after hyphen. This appears to happen in 
0.8.0 and 0.8.1 versions, in 0.7.3 everything works properly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] zjffdu opened a new pull request #3306: [ZEPPELIN-4001] zeppelin-interpreter-integration is ignored due to wrong folder structure

2019-02-13 Thread GitBox 
zjffdu opened a new pull request #3306: [ZEPPELIN-4001] 
zeppelin-interpreter-integration is ignored due to wrong folder structure
URL: https://github.com/apache/zeppelin/pull/3306
 
 
   ### What is this PR for?
   
   zeppelin-interpreter-integration is ignored due to wrong folder structure, 
that means all the integration of this module is ignored. This PR fix this 
issue, rename `zeppelin-interpreter-integration/src/main/test` to  
`zeppelin-interpreter-integration/src/test`. Besides that, this PR also fix 
some test case issues, especially split `ZeppelinSparkClusterTest` into 
`ZeppelinSparkClusterTestPt1` and `ZeppelinSparkClusterTestPt2` to avoid travis 
build timeout.
   
   
   ### What type of PR is it?
   [Bug Fix | Refactoring]
   
   ### Todos
   * [ ] - Task
   
   ### What is the Jira issue?
   * https://jira.apache.org/jira/browse/ZEPPELIN-4001
   
   ### How should this be tested?
   * CI 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
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services