Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2213
Merge into master if there are no more comments!
---
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 th
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2213
LGTM
---
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
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2213
@jongyoul Yup, will open a PR for that soon.
@Leemoonsoo Thanks. Updated again :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2213
[this
section](https://github.com/apache/zeppelin/blob/master/docs/install/virtual_machine.md#how-to-build--run-zeppelin)
need to be updated, too.
---
If your project is set up for it, you ca
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2213
@AhyoungRyu I think you can remove '-Pyarn', too. Can you handle it? You'd
better handle it with another PR.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2213
@felixcheung Thanks for pointing it out. Right it makes sense.
I changed all `py4j.version` in `spark/pom.xml` and
`spark-dependencies/pom.xml` to `spark.py4j.version`:
ce431584dc77408104b
