Github user corneadoug commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/389#issuecomment-157302094
I'm a bit late for the party,
However I would prefer the ``isReadOnly()`` part in zeppelin-web to be
handled as a DataFactory instead of storing it in
Github user jongyoul commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/435#issuecomment-157299624
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 this feat
Github user jongyoul commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/389#issuecomment-157299400
@Leemoonsoo I think we should take a care of a style of `import *`. What do
you think of it? This looks minor for now but it needs to keep it.
---
If your
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/430#issuecomment-157279509
Merging #430 and #431 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 GitH
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/439#issuecomment-157278977
I think the last CI fail is irrelevant.
Looks good to me.
---
If your project is set up for it, you can reply to this email and have your
reply appea
GitHub user prabhjyotsingh opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/441
ZEPPELIN-293 notebook execution results leaking to dashboard page
Original PR https://github.com/apache/incubator-zeppelin/pull/293
When we run a paragraph, and without it
Github user prabhjyotsingh closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/293
---
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
Github user prabhjyotsingh commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/293#issuecomment-157274482
Doing a new PR now, and closing this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
GitHub user corneadoug opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/440
ZEPPELIN-426 - Allowing new paragraph under the last one
Adding a paragraph under the last one of the notebook was not allowed.
I tested a lot of different cases:
* While runni
Github user corneadoug commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/440#issuecomment-157262507
Ready for tests/reviews
---
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 do
Github user corneadoug commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/436#issuecomment-157248651
Merging if there is 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 corneadoug commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/293#issuecomment-157248559
@Leemoonsoo if you still have that branch locally, could you do a new PR?
---
If your project is set up for it, you can reply to this email and have your
Github user corneadoug commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/390#issuecomment-157247769
Just changed the scope of this PR, it is now ready to be merged.
Code coverage is still there, although the report path changed from inside
``zeppelin-
Github user blrunner commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/439#issuecomment-157246146
I made two CI builds and one of them succeeded as following:
https://travis-ci.org/apache/incubator-zeppelin/builds/91511236
---
If your project is set
CORNEAU Damien created ZEPPELIN-431:
---
Summary: Karma test result not showing
Key: ZEPPELIN-431
URL: https://issues.apache.org/jira/browse/ZEPPELIN-431
Project: Zeppelin
Issue Type: Bug
Github user corneadoug commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/438#issuecomment-157235467
Will merge if there is no more comments
---
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 corneadoug commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/438#issuecomment-157235437
@Leemoonsoo issue created here:
https://issues.apache.org/jira/browse/ZEPPELIN-430
---
If your project is set up for it, you can reply to this email a
CORNEAU Damien created ZEPPELIN-430:
---
Summary: Replace grunt-autoprefixer for frunt-postcss
Key: ZEPPELIN-430
URL: https://issues.apache.org/jira/browse/ZEPPELIN-430
Project: Zeppelin
Issue
Github user blrunner commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/439#issuecomment-15726
Hi @Leemoonsoo
Thank you for your quick feedback. I've just added some unit test cases.
The CI build will run soon. :)
---
If your project is set
Github user elbamos commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-157203411
The current push should resolve some issues with changes in the
Spark-Zeppelin interface that had created issues for users, as well as support
for 1.5.1.
Hey Pranav,
Did you make any progress on this?
--
Rohit
On Sunday, August 16, 2015, moon soo Lee wrote:
> Pranav, proposal looks awesome!
>
> I have a question and feedback,
>
> You said you tested 1,2 and 3. To create SparkIMain per notebook, you need
> information of notebook id. Did you get
Ah, I see. I hadn't noticed that your other voting email was for a
different list, and I didn't realize that there was a requirement for a
second level of voting for incubating projects. Thanks for the
clarification.
~ Jonathan
On Mon, Nov 16, 2015 at 12:19 PM, tog wrote:
> OK Moon Thanks for t
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/439#issuecomment-157184867
Thanks for nice upgrade.
CI looks like failing with the other reason, but could you try trigger CI?
close / reopen this PR will trigger the CI.
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-157180281
@elbamos Please do not blame people in your PR. That's out of your PR's
scope.
And I thought you and Felix both agreed to move forward, If you think
t
Are you all sure this is how we want to run an open source project?
I can say I wrote this code but it doesn't make it right.
When we contribute code to the open source community we prefer the better
good then our own private ego.
I have been working with the zeppelin project since its beginning a
Github user elbamos commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-157158373
To anyone who may be coming here from today's blog post and confused by
these comments about the current status:
The RInterpreter for zeppelin works
OK Moon Thanks for the information, I was not aware of that step.
Cheers
Guillaume
On Nov 16, 2015 8:10 PM, "moon soo Lee" wrote:
> Hi,
>
> I think it's my bad that not explaining well enough about the next step.
>
> While Zeppelin is in incubation, after vote passed in dev@zeppelin,
> another
>
Hi,
I think it's my bad that not explaining well enough about the next step.
While Zeppelin is in incubation, after vote passed in dev@zeppelin, another
vote is required in general@incubator with IPMC.
Here's related information about release process in incubation.
http://incubator.apache.org/in
Moon,
I think I may have the same confusion as Guillaume, as you posted a message
on this same thread a couple of days ago saying that the vote for RC3 has
passed already, and the email contained a link to
http://mail-archives.apache.org/mod_mbox/incubator-zeppelin-dev/201511.mbox/%3CCALf24sboheQd
Hi Kunal,
Thanks for using Zeppelin.
Currently, there're PR
https://github.com/apache/incubator-zeppelin/pull/437 that adds dynamic
form feature into pyspark.
When Implementing an Interpreter, getFormType() abstract method need to be
implemented.
https://github.com/apache/incubator-zeppelin/blob
Hi Guillaume,
Thanks for asking.
0.5.5-incubating is in vote at general mailing list
http://mail-archives.apache.org/mod_mbox/incubator-general/201511.mbox/%3CCALf24sZin774uuZ%2BftOLV4pBf8egWyJRAMK3fscyh_kcQXZaig%40mail.gmail.com%3E
Once vote is passed at general@incubator and packages are sync
Hi Moon
Do we have an official annonce now on user mailing list following the vote?
Cheers
Guillaume
On Nov 14, 2015 12:36 PM, "moon soo Lee" wrote:
> The vote passes with 7 binding +1 votes, 9 non-binding +1 votes, and no +0
> or -1 votes. Thanks for everyone who verified rc and voted.
>
>
> +
Github user epugh commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/418#issuecomment-157136166
@rawkintrevo I found it very valuable... I'd never set up Spark or Flink,
and your tutorial assumed a much lower degree of knowledge.
---
If your project
GitHub user blrunner opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/439
ZEPPELIN-427: Upgrade to Apache TAJO 0.11.0
I bumped up Tajo to 0.11.0. And I enabled ```cancel()``` because Tajo
supports it since 0.11.0 release. For the reference, this patch ran
su
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-157040049
And if you are not comfortable working with Zeppelin community, not because
of you're wrong or Zeppelin community is wrong, but maybe just because of the
Hi Guys,
I am Kunal. I have been using zeppelin for some time now. I have made a few
changes in the code as well for my personal modifications and I am stuck at
one particular requirement. Here goes my doubt :
If we use the %sql of %hive interpreter and write something with the
pattern '${}' , a
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-157017167
Sometimes people can argue then I see the passion.
But when people don't respect each other, it easily become blaming and
fighting.
Let's try to n
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/433
---
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 rconline commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/438#issuecomment-157002527
Looks good to me.
---
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 Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/389#issuecomment-156999761
Merging 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. I
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/438#issuecomment-156998827
Looks good to me.
Do you mind creating a corresponding issue?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/435#issuecomment-156998170
Looks good to me
---
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 Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/437#issuecomment-156997464
Working really well.
Looks good to me.
---
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/436#issuecomment-156995056
I have a notebook that have result larger than paragraph width. Tested with
this PR and i can see it is fixed.
Looks good to me.
---
If your pro
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/432#issuecomment-156979502
Nice improvement!
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
Dongkyu Hwangbo created ZEPPELIN-429:
Summary: Replace Explicit type with diamond type
Key: ZEPPELIN-429
URL: https://issues.apache.org/jira/browse/ZEPPELIN-429
Project: Zeppelin
Issue Ty
Github user corneadoug commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/438#issuecomment-156950726
Ready For Reviews, Merge and more :D
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If yo
GitHub user corneadoug opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/438
Remove deprecated grunt-autoprefixer for grunt-postcss
Making a switch off grunt plugin since grunt-autoprefixer is deprecated,
and its version of autoprefixer is old.
You can merge
48 matches
Mail list logo
