You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by lresende <gi...@git.apache.org> on 2016/02/25 05:49:11 UTC
[GitHub] incubator-zeppelin pull request: [ZEPPELIN-605] Add support for Sc...
GitHub user lresende opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/747
[ZEPPELIN-605] Add support for Scala 2.11
Enable Zeppelin to be built with both Scala 2.10
and Scala 2.11, mostly to start supporting interpreters
that are moving to Scala 2.11 only such as Spark.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lresende/incubator-zeppelin scala-210-211
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-zeppelin/pull/747.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 #747
----
commit 69f755bac133c05de979154b96cd2c27bc69fc8b
Author: Luciano Resende <lr...@apache.org>
Date: 2016-02-25T04:46:46Z
[ZEPPELIN-605] Add support for Scala 2.11
Enable Zeppelin to be built with both Scala 2.10
and Scala 2.11, mostly to start supporting interpreters
that are moving to Scala 2.11 only such as Spark.
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-zeppelin issue #747: [ZEPPELIN-605][WIP] Add support for Scala 2.1...
Posted by lresende <gi...@git.apache.org>.
Github user lresende commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/747
@Leemoonsoo @felixcheung Any ideas what might be causing these build issues in [TravisCI](https://s3.amazonaws.com/archive.travis-ci.org/jobs/133750597/log.txt) ?
[INFO] Running 'npm install --color=false' in /home/travis/build/apache/incubator-zeppelin/zeppelin-web
[ERROR] npm WARN package.json zeppelin-web@0.0.0 No license field.
[ERROR] npm WARN deprecated graceful-fs@2.0.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
[ERROR] npm WARN deprecated lodash@1.0.2: lodash@<3.0.0 is no longer maintained. Upgrade to lodash@^4.0.0.
[ERROR] npm WARN deprecated graceful-fs@3.0.8: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
[ERROR] npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
[ERROR] npm WARN deprecated CSSselect@0.7.0: the module is now available as 'css-select'
[ERROR] npm WARN deprecated CSSwhat@0.4.7: the module is now available as 'css-what'
[ERROR] npm WARN optional dep failed, continuing fsevents@1.0.12
[INFO]
[INFO] > phantomjs@1.9.20 install /home/travis/build/apache/incubator-zeppelin/zeppelin-web/node_modules/karma-phantomjs-launcher/node_modules/phantomjs
[INFO] > node install.js
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-zeppelin pull request: [ZEPPELIN-605][WIP] Add support f...
Posted by adeandrade <gi...@git.apache.org>.
Github user adeandrade commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/747#issuecomment-219221250
@karup1990 Yes, it is. Did you rebase with master? I think it works if you don't. @felixcheung suggests the problem is being fixed in #868. I'm waiting for that PR to be merged to try again. If it doesn't work then I'll fall back to your suggestion. 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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-zeppelin pull request: [ZEPPELIN-605][WIP] Add support f...
Posted by karup1990 <gi...@git.apache.org>.
Github user karup1990 commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/747#issuecomment-219219344
@adeandrade is ur spark binary compiled with scala-2.11, else it will continue to use the repl classes from scala-2.10(https://issues.apache.org/jira/browse/SPARK-1812 ) and you would hit the exception.
I was able to consume this PR and use Zeppelin with spark 1.5 compiled with scala-2.11.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-zeppelin pull request: [ZEPPELIN-605][WIP] Add support f...
Posted by lresende <gi...@git.apache.org>.
Github user lresende commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/747#issuecomment-210890683
The current status of this PR is that it's working ok with Scala 2.10 and Scala 2.11, I need to try to have one source for both versions of scala, and also rebase to pickup the most recent projects added to trunk
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-zeppelin pull request: [ZEPPELIN-605][WIP] Add support f...
Posted by lresende <gi...@git.apache.org>.
Github user lresende commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/747#issuecomment-219236241
Sorry to not be so responsive here, I was busy with conferences, etc... but should be able to devote some time to this again.
This should work if you don't rebase, otherwise we need to update the new modules such as R extensions to properly work on Scala 2.11. Note that one way or another, you probably need to build Spark and Flink with Scala 2.11 and make sure you use maven "install" and not only "package".
If folks are eager to try it, i can try to rebase, while I work on the final version of this PR, which will try to merge the two scala 2.10 and 2.11 into one code, using some reflection magic.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-zeppelin pull request: [ZEPPELIN-605][WIP] Add support f...
Posted by adeandrade <gi...@git.apache.org>.
Github user adeandrade commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/747#issuecomment-218599923
Hi @lresende, I rebased the PR and created a package with:
`mvn clean package -Pbuild-distr -Pscala-2.11 -Pspark-1.6 -Phadoop-2.6 -Pyarn -Ppyspark -Dscala-2.11 -DskipTests -Dcheckstyle.skip=true clean install`
But I still don't have access to a SparkContext instance:
> java.lang.NoSuchMethodException: scala.tools.nsc.interpreter.ILoop$ILoopInterpreter.classServerUri()
at java.lang.Class.getMethod(Class.java:1786)
at org.apache.zeppelin.spark.SparkInterpreter.createSparkContext(SparkInterpreter.java:276)
at org.apache.zeppelin.spark.SparkInterpreter.getSparkContext(SparkInterpreter.java:150)
at org.apache.zeppelin.spark.SparkInterpreter.open(SparkInterpreter.java:518)
at org.apache.zeppelin.interpreter.ClassloaderInterpreter.open(ClassloaderInterpreter.java:74)
at org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:68)
at org.apache.zeppelin.interpreter.LazyOpenInterpreter.interpret(LazyOpenInterpreter.java:92)
at org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:345)
at org.apache.zeppelin.scheduler.Job.run(Job.java:176)
at org.apache.zeppelin.scheduler.FIFOScheduler$1.run(FIFOScheduler.java:139)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
Any ideas?
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-zeppelin issue #747: [ZEPPELIN-605][WIP] Add support for Scala 2.1...
Posted by felixcheung <gi...@git.apache.org>.
Github user felixcheung commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/747
it looks like error with NPM?
```
[ERROR] npm ERR! Linux 3.13.0-40-generic
[ERROR] npm ERR! argv "/home/travis/build/apache/incubator-zeppelin/zeppelin-web/node/node" "/home/travis/build/apache/incubator-zeppelin/zeppelin-web/node/node_modules/npm/bin/npm-cli.js" "install" "--color=false"
[ERROR] npm ERR! node v0.12.13
[ERROR] npm ERR! npm v2.15.0
[ERROR]
[ERROR] npm ERR! shasum check failed for /tmp/npm-10098-08b17b7f/registry.npmjs.org/multiparty/-/multiparty-2.2.0.tgz
[ERROR] npm ERR! Expected: a567c2af000ad22dc8f2a653d91978ae1f5316f4
[ERROR] npm ERR! Actual: 2f4894420f76a8277eeaf59a8c94ca43623484bd
[ERROR] npm ERR! From: https://registry.npmjs.org/multiparty/-/multiparty-2.2.0.tgz
[ERROR] npm ERR!
[ERROR] npm ERR! If you need help, you may report this error at:
[ERROR] npm ERR! <https://github.com/npm/npm/issues>
[ERROR] npm ERR! Linux 3.13.0-40-generic
[ERROR] npm ERR! argv "/home/travis/build/apache/incubator-zeppelin/zeppelin-web/node/node" "/home/travis/build/apache/incubator-zeppelin/zeppelin-web/node/node_modules/npm/bin/npm-cli.js" "install" "--color=false"
[ERROR] npm ERR! node v0.12.13
[ERROR] npm ERR! npm v2.15.0
[ERROR] npm ERR! code ECONNRESET
[ERROR] npm ERR! errno ECONNRESET
[ERROR] npm ERR! syscall read
[ERROR]
[ERROR] npm ERR! network read ECONNRESET
[ERROR] npm ERR! network This is most likely not a problem with npm itself
[ERROR] npm ERR! network and is related to network connectivity.
[ERROR] npm ERR! network In most cases you are behind a proxy or have bad network settings.
[ERROR] npm ERR! network
[ERROR] npm ERR! network If you are behind a proxy, please make sure that the
[ERROR] npm ERR! network 'proxy' config is set properly. See: 'npm help config'
[ERROR] npm ERR! Linux 3.13.0-40-generic
[ERROR] npm ERR! argv "/home/travis/build/apache/incubator-zeppelin/zeppelin-web/node/node" "/home/travis/build/apache/incubator-zeppelin/zeppelin-web/node/node_modules/npm/bin/npm-cli.js" "install" "--color=false"
[ERROR] npm ERR! node v0.12.13
[ERROR] npm ERR! npm v2.15.0
[ERROR] npm ERR! code ECONNRESET
[ERROR] npm ERR! errno ECONNRESET
[ERROR] npm ERR! syscall read
[ERROR]
[ERROR] npm ERR! network read ECONNRESET
[ERROR] npm ERR! network This is most likely not a problem with npm itself
[ERROR] npm ERR! network and is related to network connectivity.
[ERROR] npm ERR! network In most cases you are behind a proxy or have bad network settings.
[ERROR] npm ERR! network
[ERROR] npm ERR! network If you are behind a proxy, please make sure that the
[ERROR] npm ERR! network 'proxy' config is set properly. See: 'npm help config'
[ERROR] npm ERR! Linux 3.13.0-40-generic
[ERROR] npm ERR! argv "/home/travis/build/apache/incubator-zeppelin/zeppelin-web/node/node" "/home/travis/build/apache/incubator-zeppelin/zeppelin-web/node/node_modules/npm/bin/npm-cli.js" "install" "--color=false"
[ERROR] npm ERR! node v0.12.13
[ERROR] npm ERR! npm v2.15.0
[ERROR] npm ERR! code ECONNRESET
[ERROR] npm ERR! errno ECONNRESET
[ERROR] npm ERR! syscall read
[ERROR]
[ERROR] npm ERR! network read ECONNRESET
[ERROR] npm ERR! network This is most likely not a problem with npm itself
[ERROR] npm ERR! network and is related to network connectivity.
[ERROR] npm ERR! network In most cases you are behind a proxy or have bad network settings.
[ERROR] npm ERR! network
[ERROR] npm ERR! network If you are behind a proxy, please make sure that the
[ERROR] npm ERR! network 'proxy' config is set properly. See: 'npm help config'
[ERROR] npm ERR! Linux 3.13.0-40-generic
[ERROR] npm ERR! argv "/home/travis/build/apache/incubator-zeppelin/zeppelin-web/node/node" "/home/travis/build/apache/incubator-zeppelin/zeppelin-web/node/node_modules/npm/bin/npm-cli.js" "install" "--color=false"
[ERROR] npm ERR! node v0.12.13
[ERROR] npm ERR! npm v2.15.0
[ERROR] npm ERR! code ECONNRESET
[ERROR] npm ERR! errno ECONNRESET
[ERROR] npm ERR! syscall read
[ERROR]
[ERROR] npm ERR! network read ECONNRESET
[ERROR] npm ERR! network This is most likely not a problem with npm itself
[ERROR] npm ERR! network and is related to network connectivity.
[ERROR] npm ERR! network In most cases you are behind a proxy or have bad network settings.
[ERROR] npm ERR! network
[ERROR] npm ERR! network If you are behind a proxy, please make sure that the
[ERROR] npm ERR! network 'proxy' config is set properly. See: 'npm help config'
[ERROR] npm ERR! Linux 3.13.0-40-generic
[ERROR] npm ERR! argv "/home/travis/build/apache/incubator-zeppelin/zeppelin-web/node/node" "/home/travis/build/apache/incubator-zeppelin/zeppelin-web/node/node_modules/npm/bin/npm-cli.js" "install" "--color=false"
[ERROR] npm ERR! node v0.12.13
[ERROR] npm ERR! npm v2.15.0
[ERROR] npm ERR! code ECONNRESET
[ERROR] npm ERR! errno ECONNRESET
[ERROR] npm ERR! syscall read
[ERROR]
[ERROR] npm ERR! network read ECONNRESET
[ERROR] npm ERR! network This is most likely not a problem with npm itself
[ERROR] npm ERR! network and is related to network connectivity.
[ERROR] npm ERR! network In most cases you are behind a proxy or have bad network settings.
[ERROR] npm ERR! network
[ERROR] npm ERR! network If you are behind a proxy, please make sure that the
[ERROR] npm ERR! network 'proxy' config is set properly. See: 'npm help config'
[ERROR]
[ERROR] npm ERR! Please include the following file with any support request:
[ERROR] npm ERR! /home/travis/build/apache/incubator-zeppelin/zeppelin-web/npm-debug.log
[INFO]
```
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-zeppelin issue #747: [ZEPPELIN-605][WIP] Add support for Scala 2.1...
Posted by Leemoonsoo <gi...@git.apache.org>.
Github user Leemoonsoo commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/747
I think it's temporary failing. npm ERR will disappear when trigger CI again
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-zeppelin pull request: [ZEPPELIN-605][WIP] Add support f...
Posted by felixcheung <gi...@git.apache.org>.
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/747#issuecomment-218909086
@adeandrade this seems to be a breaking change in Spark 2.0, also being fixed in #868
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-zeppelin issue #747: [ZEPPELIN-605][WIP] Add support for Scala 2.1...
Posted by Leemoonsoo <gi...@git.apache.org>.
Github user Leemoonsoo commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/747
Still working in progress, created a pullrequest to this branch, https://github.com/lresende/incubator-zeppelin/pull/1 which is trying to merge 2.10 and 2.11 code using reflection
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-zeppelin issue #747: [ZEPPELIN-605][WIP] Add support for Scala 2.1...
Posted by pabloa <gi...@git.apache.org>.
Github user pabloa commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/747
Hello @lresende,
I tried your pull request and I am getting some NPE. Notebooks are not stored either. I tried the branch scala-210-211-NEW and I am getting compilation errors.
Do you have some estimated time about getting a testable version of Zeppelin under 2.11? I will be happy to test it and report 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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---