Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1398
Merging into master 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 project does not
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1398
@zjffdu It's okay :) 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
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1398
Sorry @AhyoungRyu I didn't notice you PR is based on my branch and thought
you will merge to master directly.
---
If your project is set up for it, you can reply to this email and have your
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1398
@zjffdu Did you close this PR on purpose?
---
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
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1398
@zjffdu Thank you for updating Spark interpreter docs. Looks great I think
ð
While I look through current Spark documentation page to review this PR, I
found some typos, grammar errors
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1398
\cc @Leemoonsoo @AhyoungRyu
---
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
