Thanks Renjith & Anthony, I would cancel this RC and propose a new RC after
this is fixed.
Renjith Kamath 于2018年6月1日周五 下午5:58写道：
> I have a fix for this issue. Please review
> https://github.com/apache/zeppelin/pull/2996
>
> On Fri, Jun 1, 2018 at 11:14 AM, Anthony Corbacho <
> anthonycorba...@
Github user mebelousov commented on the issue:
https://github.com/apache/zeppelin/pull/2982
I have tested.
LGTM
---
Github user mebelousov commented on the issue:
https://github.com/apache/zeppelin/pull/2996
LGTM
---
Github user naveenkumargp commented on the issue:
https://github.com/apache/zeppelin/pull/2637
@matyix
yes we are very much interested on running Livy interpreter on K8s.
please let us know how we can proceed further.
regards
naveen
---
Github user bikassaha commented on the issue:
https://github.com/apache/zeppelin/pull/2974
Does "ready to run" mean code can be executed in the note?
---
Github user SivaKaviyappa commented on the issue:
https://github.com/apache/zeppelin/pull/2231
This is works for me on aws emr. I am on emr 5.13.0, livy 0.40 , spark
2.3.0. The important change one has to make is by default aws emr brings up
livy in yarn mode. So if you change that y
FlorianKuckelkorn created ZEPPELIN-3525:
---
Summary: Build Error - mvn clean package
Key: ZEPPELIN-3525
URL: https://issues.apache.org/jira/browse/ZEPPELIN-3525
Project: Zeppelin
Issue Ty
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2231
Thanks @SivaKaviyappa for confirming
---
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2986
Thanks @Leemoonsoo Any more comment ï¼
---
Github user sameer79 commented on the issue:
https://github.com/apache/zeppelin/pull/2974
@bikassaha "Yes," The interpreter has successfully restarted.
---
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/2996
LGTM!
Merging this to master and branch-0.8 if no more discussion.
---
Prabhjyot Singh created ZEPPELIN-3526:
-
Summary: Zeppelin auth mechanisms (LDAP or password based) should
be mutually exclusive
Key: ZEPPELIN-3526
URL: https://issues.apache.org/jira/browse/ZEPPELIN-3526
Thomas Decaux created ZEPPELIN-3527:
---
Summary: Upgrade log4j to log4j2
Key: ZEPPELIN-3527
URL: https://issues.apache.org/jira/browse/ZEPPELIN-3527
Project: Zeppelin
Issue Type: Wish
GitHub user prabhjyotsingh opened a pull request:
https://github.com/apache/zeppelin/pull/3003
[ZEPPELIN-3526] Zeppelin auth mechanisms (LDAP or password based) should be
mutually exclusive
### What is this PR for?
Problem:
When any external authentication (like LDAP/AD) is
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/3003
@Leemoonsoo @felixcheung @zjffdu can you help review this.
---
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/3003
LGTM, one suggestion is that I think it is time for us to do refactoring
for the authentication component, we should put it in one component and provide
interface to be used by other components. In
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/3003
Agreed we should definitely do something like zeppelin-plugins for
authentication components as well in Zeppelin-0.9
---
17 matches
Mail list logo
