Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/687#issuecomment-180880662
Merge if there're 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
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/684#issuecomment-180880233
Could you try merge current master branch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/688#issuecomment-180881869
Could this test also cover new paragraph by clicking button between
paragraphs?
---
If your project is set up for it, you can reply to this email and
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/695
---
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
On Thu, Feb 04, 2016 at 10:50:10AM -0800, Mina Lee wrote:
> I think Zeppelin meets the requirements for graduation.
>
> Zeppelin community is growing fast and getting more diverse. Number of
> contributors has increased more than 7 times and three new committers are
> admitted since Zeppelin
Github user minahlee commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/685#issuecomment-180837936
My bad. I just pushed a fix.
---
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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/700#issuecomment-180837842
shouldn't it be git: instead of http:?
git://git.apache.org/incubator-zeppelin.git
---
If your project is set up for it, you can reply to this
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/152#issuecomment-180840046
any update on this? @Madhuka this would be very cool to have
---
If your project is set up for it, you can reply to this email and have your
reply
Felix Cheung created ZEPPELIN-662:
-
Summary: HBase interpreter should support CDH favor of HBase
Key: ZEPPELIN-662
URL: https://issues.apache.org/jira/browse/ZEPPELIN-662
Project: Zeppelin
Github user vgmartinez commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/667#issuecomment-180845559
Ok...I fix
---
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
Hi Prasad,
I also have similar opinion like Moon on the storing the permission.
However your design so far looks reasonably good though.
Here are my few comments/suggestions -
1. I do agree with you that Interpreter Authorization is complex. But the
examples you have provided, if I'm not
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/699#issuecomment-180837301
looks good - it seems we have some duplications here, perhaps @markncooper
you would like to refactor this after #695 is merged to a util method?
---
Hi tog,
There was another discussion not long time ago:
http://apache-zeppelin-users-incubating-mailing-list.75479.x6.nabble.com/Data-Visualization-Map-td2144.html
Overall the PR needs to be rebased, and also remove the data validation
from it.
Madhuka answered on the mailing list not long ago,
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/695#issuecomment-180837044
looks good
---
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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/661#issuecomment-180839625
Thanks, please fix and we should merge this unless anyone has more comment.
---
If your project is set up for it, you can reply to this email and have
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/657#issuecomment-180842637
Right apologies. I'll try to do tonight.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user sourav-mazumder commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/681#issuecomment-180820970
Hi Prasad,
I also have similar opinion like Moon on the storing the permission.
However your design so far looks reasonably good though.
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/667#issuecomment-180839918
property key not matching a valid profile is probably a fix would be great
to make separately - would you be interested in that, @vgmartinez ?
let's
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/675
---
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
Github user doanduyhai commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/657#issuecomment-180839735
Can anyone have a look at this PR ? It's pending for quite a while
---
If your project is set up for it, you can reply to this email and have your
reply
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/657#issuecomment-180945137
Tested, I suppose this is for embedded/included spark only.
Merging if no comment.
---
If your project is set up for it, you can reply to this email
Github user doanduyhai commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/657#issuecomment-180964282
Thanks @felixcheung for testing
---
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
GitHub user felixcheung opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/701
HBase interpreter should support CDH favor of HBase
### What is this PR for?
Allow HBase interpreter to be built with vendor repo artifects
### What type of PR is it?
GitHub user echarles opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/702
R and SparkR Support [WIP]
### What is this PR for?
Implement R and SpakR Intepreter as part of the Spark Interpreter Group. It
also implements R and Scala binding (in both
Github user echarles commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/702#issuecomment-180962488
CLI fails for profiles 1.3, 1.2 and 1.1 with `object r is not a member of
package org.apache.spark.api` which is normal as SparkR was introduced in 1.4.
Hi
Could someone help me to understand what is the problem with this PR?
It has been open for quite some time and I have some interest in seing
going through so I am ready to help.
Cheers
Guillaume
GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/700
ZEPPELIN-657: Change the official location of Zeppelin in the documentation
### What is this PR for?
Lately, an official location of Zeppelin was changed from
Ahyoung created ZEPPELIN-661:
Summary: Add documentation for Shiro security to Zeppelin website
Key: ZEPPELIN-661
URL: https://issues.apache.org/jira/browse/ZEPPELIN-661
Project: Zeppelin
Issue
28 matches
Mail list logo
