[GitHub] zeppelin issue #1880: ZEPPELIN-1918. Fix build with Spark 2.1.0

Github user ejono commented on the issue: https://github.com/apache/zeppelin/pull/1880 @felixcheung, yes, I was referring to PySparkInterpreterTest.testCompletion, which I thought may have been broken in the new Spark 2.1 Travis CI profile because it was broken for that profile but

[GitHub] zeppelin issue #1880: ZEPPELIN-1918. Fix build with Spark 2.1.0

Github user ejono commented on the issue: https://github.com/apache/zeppelin/pull/1880 @zjffdu, ok, thanks for confirming that it's just a flaky test. It seemed like it could have been related, but I did not dig into it. Have you gotten the test to pass when using Spark

[GitHub] zeppelin issue #1880: ZEPPELIN-1918. Fix build with Spark 2.1.0

Github user ejono commented on the issue: https://github.com/apache/zeppelin/pull/1880 @zjffdu, I did see your follow-up commit but was already testing from that commit. I'm not sure what was wrong. Wasn't the CI (which hit the same exact error) also building from that com

[GitHub] zeppelin issue #1880: ZEPPELIN-1918. Fix build with Spark 2.1.0

Github user ejono commented on the issue: https://github.com/apache/zeppelin/pull/1880 I built with "./dev/change_scala_version.sh 2.11; mvn clean package -Pscala-2.11 -Pspark-2.1" and see the same test failure that Travis saw for the new 2.1.0 build (https://travis-ci.

[GitHub] zeppelin issue #1787: ZEPPELIN-1815. Support Spark 2.1

Github user ejono commented on the issue: https://github.com/apache/zeppelin/pull/1787 Sorry, I was not able to work on this over the past few days. Thank you very much for fixing it, @zjffdu! --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] zeppelin issue #1787: ZEPPELIN-1815. Support Spark 2.1

Github user ejono commented on the issue: https://github.com/apache/zeppelin/pull/1787 Thanks for confirming. The fix would not be too difficult, but yes, I'm puzzled as to why the CI isn't broken, so maybe we need to figure that out first. --- If your project is set up f

[GitHub] zeppelin issue #1787: ZEPPELIN-1815. Support Spark 2.1

Github user ejono commented on the issue: https://github.com/apache/zeppelin/pull/1787 Answering my own questions: I still haven't found a definitive answer to whether or not Java classes may take advantage of default parameter values defined in Scala classes, but

[GitHub] zeppelin issue #1787: ZEPPELIN-1815. Support Spark 2.1

Github user ejono commented on the issue: https://github.com/apache/zeppelin/pull/1787 When I compile Zeppelin (from master, including this change) against Spark 2.1.0, I hit the following error: [ERROR] /Volumes/Amazon/oss-workspace/src/zeppelin/spark/src/main/java/org