Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/789#issuecomment-201968581
@elbamos Note that, every comments in PullRequest already being broadcasted
to developer mailing list.
If you have any other subject to discuss ab
Github user elbamos commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/789#issuecomment-201965711
I meant the developer mailing list for Zeppelin. We can continue the
discussion there in the presence of others.
> On Mar 26, 2016, at 8:51 PM, Lee
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/789#issuecomment-201964685
@elbamos
If the 'community' you mean is not a Zeppelin community, please understand
that I don't discuss / review the code contribution anywhere Zeppe
Github user elbamos commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/789#issuecomment-201953405
No - if I have to do that, I think it will have to go to the community, so
instead of wasting my time let's just discuss it there.
> On Mar 26, 2016
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/789#issuecomment-201949330
@elbamos Can you provide link to your explanation in multiple forums? i
didn't see any.
---
If your project is set up for it, you can reply to this email
Github user elbamos commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/789#issuecomment-201949274
I've explained this several times already in multiple forums. If you don't
want to accept it, then you should raise the issue on the developers list so
the c
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/742
---
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 fea
Github user doanduyhai commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/742#issuecomment-201930893
@deepakas as soon as this PR will be merged, you can start playing with it
by building the master yourself
---
If your project is set up for it, you can
Github user deepakas commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/742#issuecomment-201929498
Is this feature going to available in 0.6 snapshot soon. I am using the
click button example from the doc and z.run("20160326-184416_217725826" )
zijunyang created ZEPPELIN-764:
--
Summary: Set invalid Note Permissions will make notebook unreadable
Key: ZEPPELIN-764
URL: https://issues.apache.org/jira/browse/ZEPPELIN-764
Project: Zeppelin
I
Hi all,
I am trying to look into above mentioned issue[1].
I am just trying to familiar with zeppelin back end implementation. Also I
went through the interpreter API documentation. [2]
As far as I understood, we have to have an specific way to identify the
interpreter, which we need to get the id
zijunyang created ZEPPELIN-763:
--
Summary: Shiro authentication for Apache Zeppelin don't word
Key: ZEPPELIN-763
URL: https://issues.apache.org/jira/browse/ZEPPELIN-763
Project: Zeppelin
Issue Ty
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/789#issuecomment-201871771
@elbamos
> No -echarles is right. The current preference system is terribly
confusing and often inconsistent. It is a source of user complaint.
Github user elbamos commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/789#issuecomment-201866799
No -echarles is right. The current preference system is terribly confusing
and often inconsistent. It is a source of user complaint.
This PR in its c
14 matches
Mail list logo
