Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1636
@khalidhuseynov LGTM. Will merge if there are no more discussions.
---
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
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1636
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/1636
@khalidhuseynov I see, then the change is looks good to me.
---
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
Github user khalidhuseynov commented on the issue:
https://github.com/apache/zeppelin/pull/1636
@AhyoungRyu actually I meant it for all three cases (standalone, yarn,
mesos) and mistakenly added it only for standalone. So I changed it now and
added small note for each case. let me
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1636
Could you also update the `yarn` docker file path to
`$ZEPPELIN_HOME/scripts/docker/spark-cluster-managers/spark_yarn_cluster` ?
---
If your project is set up for it, you can reply to this
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1636
The PR title says "Add note on configuration of **spark-yarn mode** on
docker",
> **Note 2:** `sparkmaster` hostname used to run docker containers below
should be defined in your
