Github user johnnyws commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/796#issuecomment-206712630
JIRA created to deal with notebook name duplicates:
[ZEPPELIN-796](https://issues.apache.org/jira/browse/ZEPPELIN-796)
---
If your project is set up for it
Johnny W. created ZEPPELIN-796:
--
Summary: Duplicated notebook names should not be allowed
Key: ZEPPELIN-796
URL: https://issues.apache.org/jira/browse/ZEPPELIN-796
Project: Zeppelin
Issue Type:
Github user johnnyws commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/796#issuecomment-206711691
@felizbear did some refactoring, and ready for review. btw, I really
enjoyed using lodash
@bzz i did merge several times on this branch. do I need to reb
Comments:
Regarding #2: Language support. It would be great to see more Scala (once up
to speed with Scala I never wanted to look back at Java)
Regarding #3: Drop old SPARK support. Seems like low hanging fruit, low impact
& high reward.
Regarding #5: Configuration Files. We could take a queue
Github user ankurmitujjain commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/761#issuecomment-206706615
Open for review
Please let me know if any more changes required or features needs to be
added...
Thanks
Ankur
---
If your projec
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/745#issuecomment-206705438
The implementation itself looks good to me.
While this PR links 'dynamic form' and 'angular display system', I'd like
to discuss little bit about
Github user mudsam commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/823#issuecomment-206701324
As far as I can tell it would not be needed for the R interpreter from PR
208.
---
If your project is set up for it, you can reply to this email and have you
Need more caffeine, it’s PR 823, not 819, my bad..
/Johan
On 4/7/16, 12:08 AM, "MUEDSAM, JOHAN" wrote:
>Thanks moon, I created pull request #819 for this -
>https://github.com/apache/incubator-zeppelin/pull/819
>Unfortunately no Jira, realized I don't have an account and didn’t have time
Github user elbamos commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/823#issuecomment-206699570
The patch shouldn't be necessary for the R interpreter from PR 208 right?
---
If your project is set up for it, you can reply to this email and have your
rep
Thanks moon, I created pull request #819 for this -
https://github.com/apache/incubator-zeppelin/pull/819
Unfortunately no Jira, realized I don't have an account and didn’t have time to
set one up for now.
/Johan
On 4/6/16, 6:20 PM, "moon soo Lee" wrote:
>Hi Johan,
>
>Thanks for consider
GitHub user mudsam opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/823
Generate unique temporary files for Python and R Spark Interpreters.
### What is this PR for?
Generate unique temporary files for Python and R Spark interpreters using
java.io.File.cr
Roman, Henry thank you for advices,
Moon thank you for volunteering and preparing the Charter draft [1].
Although it was not very clean from the [2] that Charter better be included
in the community vote as well,
I feel very comfortable with current proposal and ask to count my vote
holding for wha
Thanks Roman for thoughtful guidance.
If it is not a big problem and PPMC agrees, I'd like to nominate myself.
About the duty of Chair, in addition to Roman's summary, I've read some
documents [1] [2] and they're really helpful to understand what it is.
Regarding Chair selection policy,
Chair of
Github user darionyaphet commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/605#issuecomment-206680628
Hi @Leemoonsoo It seem not effective .
I build Zeppelin using command :
` mvn package -Pspark-1.5 -Dspark.version=1.5.0 -Pyarn -Ppyspark
Github user corneadoug commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/804#issuecomment-206663670
Maybe the GIFs are not obvious enough :)
The PR is mainly trying to improve the rendering of the streaming
capability introduced in https://github
A few suggestions for the roadmap:
1. Increase unit test coverage. I suggest we set thresholds -- say, 70% for
0.6, 85% for 0.7, and aim for 95% before 1.0.
2. Language support. Right now, interpreters essentially have to be written
in Java, or at least have java wrappers. This is because th
This looks good to me. Still I think you need to decide on a Chair.
You will definitely have to do that before the vote goes to IPMC
and it is a good practice for community to vote on a complete
resolution rather than a part of it.
A few things that you probably know already, but I find useful
to
+1 (non-binding)
On 4/5/16, 2:30 AM, "moon soo Lee" wrote:
>Dear Community,
>
>Based on the positive discussion, I'm calling for the community VOTE
>to graduate Apache Zeppelin (incubating) to top level project (TLP).
>
>Please vote on the resolution pasted below.
>
>[ ] +1 Graduate Apache Zep
Hi
Thanks Henry and Roman for the advice.
I have created a draft
https://cwiki.apache.org/confluence/display/ZEPPELIN/Board+resolution+%28DRAFT%29+for+the+graduation.
Please take a look.
In the draft,
Project description and scope follows description in incubation status page
[1].
Includes all
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/818#issuecomment-206639157
This is fixes 2 CI https://travis-ci.org/bzz/incubator-zeppelin and
https://travis-ci.org/apache/incubator-zeppelin and is ready to be merged.
\cc @felix
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/819#issuecomment-206638366
@jersub could you elaborate on the purpose of this PR please?
AFAIK there were no plans to do any further Zeppelin releases from 0.5.6
branch
---
If your
On Wed, Apr 6, 2016 at 7:18 AM, Henry Saputra wrote:
> Hi Moon,
>
> Actually we should add proposed board resolution [1] in the Vote thread
> which include choosing the chair.
>
> [1] http://incubator.apache.org/guides/graduation.html#toplevel
That's a really good advice! Part of the graduation p
Hi Johan,
Thanks for considering the contribution.
Creating jira issue is not mandatory in this project. But it's always good
idea to open an JIRA issue for a pullrequest.
JIRA issue is not only a useful for the discussion but also useful to track
extra informations such as fix version. Moreover,
We’ve run into an issue where the Spark and R interpreters creates temporary
files with static names, /tmp/zeppelin_pyspark.py and /tmp/zeppelin_sparkr.R
respectively. The reason it doesn’t work for us is that we’re running multiple
instances on the same server (multi-user behind nginx reverse p
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/605#issuecomment-206500539
@darionyaphet 0.5.6 includes this patch
---
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 fireboy1919 opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/822
Resource pools api
### What is this PR for?
This is a step towards creating a REST endpoint from resource pools
https://issues.apache.org/jira/browse/ZEPPELIN-699
It al
Hi,
Thanks for the suggestion! It worked and I am able to run the tests now :)
I was trying to run a test in SparkInterpreter class
- emptyConfigurationVariablesOnlyForNonSparkProperties - just to see how
the logging is done since that seems be to what needs to be handled in JIRA
722 : ZEPPELIN-7
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/818#issuecomment-206450666
\cc @felixcheung for review
---
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
+1
On 4/5/16, 12:30 AM, "moon soo Lee" wrote:
>Dear Community,
>
>Based on the positive discussion, I'm calling for the community VOTE
>to graduate Apache Zeppelin (incubating) to top level project (TLP).
>
>Please vote on the resolution pasted below.
>
>[ ] +1 Graduate Apache Zeppelin from t
Thanks @bzz. I'm a little bit confused about where we are now - will one or
both interpreters work for people who download this now?
> On Apr 6, 2016, at 5:39 AM, b...@apache.org wrote:
>
> Repository: incubator-zeppelin
> Updated Branches:
> refs/heads/master fb8e77bfd -> 9cc7e4f40
>
>
> Re-
Github user ankurmitujjain commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/761#issuecomment-206432399
Travis seems to be hanged.. can anyone please look at it...
---
If your project is set up for it, you can reply to this email and have your
reply appe
Github user ankurmitujjain commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/761#issuecomment-206432257
Revert Done... Thanks :+1:
---
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 pr
Github user darionyaphet commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/605#issuecomment-206431589
This PR have apply in `0.5.6` ? `spark.yarn.isPython=true` must be set in
zeppline-env.sh
---
If your project is set up for it, you can reply to this
Github user corneadoug commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/761#issuecomment-206424099
You can do a `git reset --hard lastCommitYouWantInYourHistory` then `git
push -f` to rewrite
---
If your project is set up for it, you can reply to this
Github user ankurmitujjain commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/761#issuecomment-206410334
@r-kamath , I had not tested this, but I believe whatever amount of rows is
supported by Zeppelin it will be supporting, on Datatables forum I can see
Github user ankurmitujjain commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/761#issuecomment-206408111
Posting new screenshots for reference...
2016년 4월 6일 (수) 오후 10:49, Ankur Jain 님이 작성:
> Congratulations Prabhjyot
>
> -Original Message-
> From: Jongyoul Lee [mailto:jongy...@gmail.com]
> Sent: 06 April 2016 06:59 PM
> To: dev@zeppelin.incubator.apache.org
> Subject: Re: [ANNO
Congratulations Prabhjyot
-Original Message-
From: Jongyoul Lee [mailto:jongy...@gmail.com]
Sent: 06 April 2016 06:59 PM
To: dev@zeppelin.incubator.apache.org
Subject: Re: [ANNOUNCE] New Apache Zeppelin (incubating) Committer & PPMC -
Prabhjyot Singh
Congrats!
On Wed, Apr 6, 2016 at
Congrats!
On Wed, Apr 6, 2016 at 5:25 PM, Victor Manuel Garcia <
victor.gar...@beeva.com> wrote:
> Congratulations Prabhjyot.
>
> 2016-04-06 10:17 GMT+02:00 Alexander Bezzubov :
>
> > Thank you Felix, and welcome Prabhjyot - it's great to have you on board!
> >
> > --
> > Alex
> >
> > On Wed,
Github user ankurmitujjain commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/761#issuecomment-206346230
Can someone help me to push changes?
I am not able to resolve conflicts... So please guide me how I can push my
changes to this PR
---
If your pr
+1
---
Aurélien Hébert
Developer at Cityzen Data
On Wed, Apr 6, 2016 at 11:38 AM, Prabhjyot Singh
wrote:
> +1
>
> On 6 April 2016 at 15:02, Sherif Akoush wrote:
>
> > +1
> >
> > On Wed, Apr 6, 2016 at 8:58 AM, madhuka udantha
> > wrote:
> > > +1
> > >
> > > On Wed, Apr 6, 2016 at 12:47 PM, To
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/821
---
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 bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/821#issuecomment-206285461
Thanks for a prompt responce guys!
---
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 projec
Github user prabhjyotsingh commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/821#issuecomment-206272718
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 thi
Github user anthonycorbacho commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/821#issuecomment-206266345
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 th
GitHub user bzz opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/821
Fix 2 minor non-code style issues
### What is this PR for?
2 minor non-code style improvements.
HT @anthonycorbacho
### What type of PR is it?
Improvement
###
Github user doanduyhai commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/745#issuecomment-206262470
ping @Leemoonsoo
---
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 asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/820
---
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
+1
On 6 April 2016 at 15:02, Sherif Akoush wrote:
> +1
>
> On Wed, Apr 6, 2016 at 8:58 AM, madhuka udantha
> wrote:
> > +1
> >
> > On Wed, Apr 6, 2016 at 12:47 PM, Tom Barber
> wrote:
> >
> >> +1 binding
> >> On 6 Apr 2016 07:40, "Eric Charles" wrote:
> >>
> >> > [x] +1 (non-binding) Graduate
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/820#issuecomment-206260666
Thank you @khalidhuseynov !
Merging as this is a hotfix.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
+1
On Wed, Apr 6, 2016 at 8:58 AM, madhuka udantha
wrote:
> +1
>
> On Wed, Apr 6, 2016 at 12:47 PM, Tom Barber wrote:
>
>> +1 binding
>> On 6 Apr 2016 07:40, "Eric Charles" wrote:
>>
>> > [x] +1 (non-binding) Graduate Apache Zeppelin from the Incubator
>> >
>> > On 05/04/16 09:30, moon soo Lee
Hi Felix,
It seems like the code has been corrupted during I merging my code with the
newest pull.
I reset the master branch and then I was able to build successfully.
BR
On Tue, Apr 5, 2016 at 3:11 PM, Felix Cheung
wrote:
> Hmm.. What is the build command line you use to build?
>
>
>
>
>
>
>
Github user khalidhuseynov commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/820#issuecomment-206252915
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 thi
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/820#issuecomment-206221167
\cc @Leemoonsoo for review
---
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 n
GitHub user bzz opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/820
Re-apply #815 - resolve SparkR implementation conflict 815
### What is this PR for?
Somehow squashed merge commit for #815 -
fb8e77bfd7296a08106b44fd834e4cf0d6950a70 does not include 2 c
Congratulations Prabhjyot.
2016-04-06 10:17 GMT+02:00 Alexander Bezzubov :
> Thank you Felix, and welcome Prabhjyot - it's great to have you on board!
>
> --
> Alex
>
> On Wed, Apr 6, 2016 at 4:58 PM, Felix Cheung
> wrote:
>
> > Hi folks,
> >
> > The Apache Zeppelin (incubating) PPMC is happ
GitHub user jersub opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/819
Backport the NPM fix from master
### What is this PR for?
Fix the zeppelin-web build error
```
[ERROR] npm ERR! registry error parsing json
[ERROR] npm http 200 https:
Thank you Felix, and welcome Prabhjyot - it's great to have you on board!
--
Alex
On Wed, Apr 6, 2016 at 4:58 PM, Felix Cheung wrote:
> Hi folks,
>
> The Apache Zeppelin (incubating) PPMC is happy to welcome new PPMC member
> and committer:
>
> Prabhjyot Singh has been constantly involving the
Hi folks,
The Apache Zeppelin (incubating) PPMC is happy to welcome new PPMC member
and committer:
Prabhjyot Singh has been constantly involving the community since August
2015, providing various improvements and bug fixes.
We are very excited to have Prabhjyot join the project as PPMC and
commi
+1
On Wed, Apr 6, 2016 at 12:47 PM, Tom Barber wrote:
> +1 binding
> On 6 Apr 2016 07:40, "Eric Charles" wrote:
>
> > [x] +1 (non-binding) Graduate Apache Zeppelin from the Incubator
> >
> > On 05/04/16 09:30, moon soo Lee wrote:
> >
> >> Dear Community,
> >>
> >> Based on the positive discussi
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/796#issuecomment-206187328
@johnnyws thank you for explanation. I think there is value in this PR not
to changing the default behaviour that users already have for the 'root',
single-folde
Thank you Henry! A community vote thread is in progress [1].
--
Alex
1. https://s.apache.org/Fhl0
On Wed, Apr 6, 2016 at 3:45 PM, Henry Saputra
wrote:
> Oh wait, this is just DISCUSS thread =P
> Sorry.
>
> I am glad the community has grown and following the Apache way. Looking
> forward to t
GitHub user bzz opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/818
ZEPPELIN-783: fix Spark download on CI
### What is this PR for?
Fix Spark download on CI
### What type of PR is it?
Hot Fix
### What is the Jira issue?
[ZEPPELIN
+1 binding
On 6 Apr 2016 07:40, "Eric Charles" wrote:
> [x] +1 (non-binding) Graduate Apache Zeppelin from the Incubator
>
> On 05/04/16 09:30, moon soo Lee wrote:
>
>> Dear Community,
>>
>> Based on the positive discussion, I'm calling for the community VOTE
>> to graduate Apache Zeppelin (incub
If the interpreters get moved out of the spark interpretergroup, they won't be
able to access spark.
> On Apr 6, 2016, at 2:49 AM, Eric Charles wrote:
>
> C) sounds also logical to me. It follows closer the implementation.
>
>> On 05/04/16 20:58, Jeff Steinmetz wrote:
>> I actually was thinkin
Alexander Bezzubov created ZEPPELIN-795:
---
Summary: Update ./dev/merge_zeppelin_pr.py to sign commits with
GPG key
Key: ZEPPELIN-795
URL: https://issues.apache.org/jira/browse/ZEPPELIN-795
Projec
darion yaphet created ZEPPELIN-794:
--
Summary: Zeppelin Disconnect
Key: ZEPPELIN-794
URL: https://issues.apache.org/jira/browse/ZEPPELIN-794
Project: Zeppelin
Issue Type: Bug
Compo
71 matches
Mail list logo
