Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2712
make sense, PR and jira title changed
---
I also worry about well-known password problem. We need to find a way of
generating password randomly at the first time to avoid potential risk, but
it’s not easy on our current shiro setting. Can someone have any good idea
to solve it?
On Sun, 24 Dec 2017 at 3:14 AM Felix Cheung
wrote:
> Authen
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2708
yes, I think
---
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2700
and we should probably check why RAT doesn't pick up the missing ASF header
for new files?
---
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2713
@Manituti hi - please close this - if you have a question please contact
u...@zeppelin.apache.org
---
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2712
shouldn't this PR say "config storage" instead of "storage layer"?
---
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2653
---
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2653
merged, thanks
---
Authentication by default is good but we should avoid having well known user /
password by default - it’s security risk.
From: Belousov Maksim Eduardovich
Sent: Thursday, December 21, 2017 12:30:57 AM
To: us...@zeppelin.apache.org
Cc: dev@zeppelin.apache.org
Subj
I’d suggest first, +1 on the PR to express your interests and support.
Then you could add reviewer directly on the PR.
But this is outside the scope of this thread.
From: Belousov Maksim Eduardovich
Sent: Wednesday, December 20, 2017 1:22:07 AM
To: dev@zeppelin.
10 matches
Mail list logo
