Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1879
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
Cool, thanks!
On Thu, Jan 12, 2017 at 1:13 AM, Mina Lee wrote:
> Hi Ashwin,
>
> we still have some issues that need to be handled before release,
> hopefully most of them are in review process which will take 2-3 more days.
> I am going to start release vote next week, so I
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1873
@epahomov Thanks for the contribution.
I'm trying to understand what cause this problem, because
`zeppelin-zengine` shouldn't be a dependency of any interpreter and `/lib`
directory
GitHub user cloverhearts opened a pull request:
https://github.com/apache/zeppelin/pull/1896
implementation test case for connect to exists interpreter process
### What is this PR for?
We need test case for remote interpreter process ( connect to exists
process)
###
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1884
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1858
---
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
GitHub user khalidhuseynov opened a pull request:
https://github.com/apache/zeppelin/pull/1898
[TBD] set cron job executor to current user by default
### What is this PR for?
currently when executing cron job, backend doesn't know who initiated cron
job (with subsequent save)
Github user OopsOutOfMemory commented on the issue:
https://github.com/apache/zeppelin/pull/1891
@Leemoonsoo @jongyoul Any comments for this PR ?
---
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 Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1831
Thanks @1ambda for the fix. Thanks @zjffdu for reviewing and verifying.
It looks good to me, while it provides more consistent behavior between
`PysparkInterpreter` and
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1842
@AhyoungRyu Thanks for the review. Great to see High chart working nicely.
A lot more improvements on Helium menu will be required, like search page,
grouping packages by type, package
Github user OopsOutOfMemory commented on the issue:
https://github.com/apache/zeppelin/pull/1891
I'm not sure, this PR is intent to fix the dead lock issue.
---
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 jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1891
Does this PR resolve flaky test that current master encounters?
---
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 jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1890
@minahlee I think `-Pr` doesn't mean anything because users cannot run R
interpreter since `-Psparkr` is enabled. How about removing `-Pr` in a script?
---
If your project is set up for it, you
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1861
merging if no more comment
---
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
GitHub user robbinspg opened a pull request:
https://github.com/apache/zeppelin/pull/1894
[ZEPPELIN-1560] avoid generating minus sign in package name
### What is this PR for?
using Object.hashCode() as part of the REPL wrapper class name can cause a
compilation error as
Github user OopsOutOfMemory commented on the issue:
https://github.com/apache/zeppelin/pull/1891
Flaky test may be another concurrency issue in scheduler execute jobs.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
GitHub user khalidhuseynov opened a pull request:
https://github.com/apache/zeppelin/pull/1895
[HOTFIX] Improve stability of sync when get fails
### What is this PR for?
This is to improve the stability of sync mechanism when `get` from some
backend storage fails (e.g. corrupt
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1842
@Leemoonsoo Thanks! I just suggested to have some default message like
other pages (e.g. localhost:8080/#/interpreter -> there is "Manage interpreters
settings. You can create / edit / remove
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1894
@robbinspg Great fix!
CI failure looks not related.
LGTM and merge to master, branch-0.7, branch-0.6 if no more comments!
---
If your project is set up for it, you can reply to
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1868
LGTM and merge to master if 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 have
20 matches
Mail list logo