Github user minahlee commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/313#issuecomment-159523282
@piyush-mukati any update on this PR? I found one bug related to spark
interpreter jvm memory setting, and this feature will be useful to handle this
bug. D
Github user piyush-mukati closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/313
---
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
Github user piyush-mukati commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/313#issuecomment-153967992
Hi,
Sorry for the Delay. i have created the JIRA
https://issues.apache.org/jira/browse/ZEPPELIN-393.
---
If your project is set up for it, you
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/313#issuecomment-145230582
@piyush-mukati Thanks for great contribution.
It's always good idea to create a JIRA issue for it. One good reason to
have JIRA issue is, Zeppelin gen
Github user piyush-mukati commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/313#issuecomment-141644030
This change will enable flexibility to configure the memory for each
interpreter.
---
If your project is set up for it, you can reply to this email
GitHub user piyush-mukati opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/313
Zeppelin jvm mem options specific to intp
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/piyush-mukati/incubator-zeppelin mas
