astralidea created ZEPPELIN-652:
---
Summary: Zeppelin use spark-sql read hive have too many CLOSE_WAIT
Key: ZEPPELIN-652
URL: https://issues.apache.org/jira/browse/ZEPPELIN-652
Project: Zeppelin
Github user r-kamath commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/682#issuecomment-179099186
:+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 project does not have this
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/654#issuecomment-179255441
@prabhjyotsingh thanks for taking care of reivew in timely manner!
It looks great, how do you think can it be further improved by `import
static
Github user vgmartinez commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/682#issuecomment-179286219
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
Github user vgmartinez commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/685#issuecomment-179252591
I tested...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
Dear Zeppelin developers,
now, after number of releases and committers grew more I'd like to suggest
the re-new the discussion of graduating Zeppelin to top level project.
If there are on objections - next step would be to start a VOTE thread here.
What do you guys think?
--
Alex
No Eran is right. The last vote for graduation passed-it was not withdrawn in
favor of releasing 0.5.6. It passed and there was some feedback from the
mentors concerning graduation, R, and some other issues. And that's the last
public discussion about graduation until today.
Alex if you
Hi guys,
I don't think any feature (R or whatever) should be prerequisites of
graduation. Especially when a project never setup those features as a
graduation goal.
Including specific features could be valid concern for release discussion,
but i don't think it's related to a graduation.
Craig McConomy created ZEPPELIN-653:
---
Summary: Unable to load notebooks when connected via IPv6
Key: ZEPPELIN-653
URL: https://issues.apache.org/jira/browse/ZEPPELIN-653
Project: Zeppelin
Amos,
I'm not sure why you taking me to want turn personal debate to you.
I'm sure i don't want to have personal debate to you.
I just wanted you share you reason why you think specific features are
prerequisites. Can you share the reason why?
Thanks,
moon
On 2016년 2월 4일 (목) at 오후 12:01 Amos
I think the community should be able to decide for itself what it wants to talk
about and I don't think it's appropriate for anyone to say that part of the
discussion is off-limits.
> On Feb 3, 2016, at 7:22 PM, moon soo Lee wrote:
>
> Hi guys,
>
> I don't think any feature
I shared why i specific features are not prerequisites of graduation and
why it's off-topic. Also alternative discussion thread that can be handled.
Amos, if you think specific features are prerequisites of graduation,
please share the reason why.
Thanks,
moon
On Thu, Feb 4, 2016 at 11:01 AM
Moon I don't think that's the question. The question is why are these things
still being delayed, and what happened to the last attempt to graduate. You
seem very focused on me.
> On Feb 3, 2016, at 10:32 PM, moon soo Lee wrote:
>
> Amos,
>
> I'm not sure why you taking me
Github user corneadoug commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/679#issuecomment-179580019
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.
Moon please don't try to turn this into a personal debate with me. Clearly,
members of the community disagree with the way you see things.
> On Feb 3, 2016, at 9:45 PM, moon soo Lee wrote:
>
> I shared why i specific features are not prerequisites of graduation and
> why it's
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/686
---
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 Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/685#issuecomment-179322637
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
Thanks Alexander for resuming the discussion.
Let's start a vote.
Best,
moon
On Wed, Feb 3, 2016 at 11:11 PM Alexander Bezzubov wrote:
> Dear Zeppelin developers,
>
> now, after number of releases and committers grew more I'd like to suggest
> the re-new the discussion of
Github user corneadoug commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/685#issuecomment-179664736
@prabhjyotsingh Doesn't look that hacky to me and preserve a nice
formatting.
> Also its integerFormatter is referenced in
Github user prabhjyotsingh commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/685#issuecomment-179666377
My bad, searched into a wrong directory; it was under reports. Please
ignore.
---
If your project is set up for it, you can reply to this email and
GitHub user ravicodder opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/689
Add new selenium test case to test clear output button
##What is this PR for?
Add a new test case for testing the clear output button.
Clear output button clears the
GitHub user ravicodder opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/690
Add selenium test case to test hide and show line number button of paragraph
What is this PR for?
Add a new test case for testing the show line number and hide line number
GitHub user ravicodder opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/691
Add test case for remove paragraph button
What is this PR for?
Add a new test case for testing the Remove Button.
Remove button is used for removing Paragraph in
GitHub user ravicodder opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/692
Add selenium test case for show and hide title of paragraph
What is this PR for?
Add a new test case for testing the show title and hide title button.
What type of
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/604#issuecomment-179616826
Regarding version, I tried and it seems need to be defined in this way
Amos, I'm not focused on you at all unless you're very beautiful women.
So, please don't worry about that.
As i already described, since last graduation discussion, community
improved/clarify contribution guide and review process and Committers are
helping long living PR to be merged. And now
GitHub user ravicodder opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/688
Add new selenium test case for create new paragraph button
The Selenium test case which will test the create new button .
Create new button is for creating new paragraph in a
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/675#issuecomment-179614103
merging if no more comment
---
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
This does make sense Moon. Completely agree with you that features are not
important for becoming a top level project
However, in my opinion, from the practical usage standpoint, without these
two features Zeppelin does not look to me a full fledged top level project.
Curious whether there are
Thanks Sourav for interest in this discussion and very valuable opinion.
I completely agree how much R and Authentication (which i believe already
in Zeppelin) will be useful for users. And believe me, I want these
features in Zeppelin more than anyone.
But at the same time we have diversity of
Github user prabhjyotsingh commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/685#issuecomment-179662685
I have slightly different view, what I think original idea behind using
`var integerFormatter = d3.format(',.1d');`
was to display number
Hey all-
A data point and observation from an ASF Member and Incubator PMC Member...
Moon is correct that readiness for graduation is a function of
community development and adherence to the Apache Way, rather any
specific feature or tech milestones. Since entering Incubator,
Zeppelin's
What is 'first non-beta release' are you referring?
On Thu, Feb 4, 2016 at 4:39 PM Amos B. Elberg wrote:
> I don't see a point to splitting it. The reason we didn't merge in
> December is that bugs in CI prevented the tests *in* 208 from functioning.
> It wasn't causing
I don't see a point to splitting it. The reason we didn't merge in December is
that bugs in CI prevented the tests *in* 208 from functioning. It wasn't
causing anything else to fail. Now CI is broken for the project anyway. If it
was going to be split, I would do that myself.
The reliability
Github user corneadoug commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/679#issuecomment-179371302
Except for that last comment, 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
Github user prabhjyotsingh commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/654#issuecomment-179370570
@bzz thank you for the quick review, did the relevant change.
---
If your project is set up for it, you can reply to this email and have your
reply
Hi Eran,
thanks for sharing your oppinion!
Could you please check my previous reply about release schedulle and let us
know if that makes sense to you?
By the way, please our mentors correct me if I'm wrong here, but after
reading [1] I was under impression that project does not have
Github user corneadoug commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/685#issuecomment-179421920
This doesn't work well without a floating point
https://cloud.githubusercontent.com/assets/710411/12794491/2f936124-ca6a-11e5-99b8-61100eb12ad0.png;>
Github user minahlee commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/660#issuecomment-179429353
Nice improvement!
I have one suggestion for style.
When user have long name of notebook, dropdown menu's width also changes:
GitHub user felixcheung reopened a pull request:
https://github.com/apache/incubator-zeppelin/pull/686
[DOC] Update doc for HBase interpreter
### What is this PR for?
Update HBase interpreter for style and additional info
### What type of PR is it?
Documentation
Github user felixcheung closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/686
---
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
Same here. I want to know the answer too.
> On Feb 2, 2016, at 12:32 PM, Jonathan Kelly wrote:
>
> Hey, I just ran into that same exact issue yesterday and wasn't sure if I was
> doing something wrong or what. Glad to know it's not just me! Unfortunately I
> have not
If I recall correctly R support was one of the pre-requisite for graduation
from day one.
I agree that Authentication should be added as well.
+1 for graduation after we add both
Eran
On Wed, 3 Feb 2016 at 20:24 Sourav Mazumder
wrote:
> Surely I vote for the same.
Hi Amos,
thank you for the question.
Let me recap past events to give some context - last month there was a
discussion started, it stopped for the period of releasing new version
0.5.6
Now its on again in order to make sure we have a concensus before starting
a vote process.
On Wed, Feb 3,
Hi Sourav,
thank you for your kind words and support!
>From the previous discussions we came up with a concensus that Zeppelin is
moving from featre based release to time based ones with timeframe of about
3 months. Given that, its reasonable to expect next realase happen around
March and I
Surely I vote for the same. Zeppelin is already very popular in different
quarts of the Spark/Big Data user group. High time to graduate it to top
level.
However, I shall suggest to have the support for R and Authentication added
to Zeppelin before that. These are the supports most of the people
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/682
---
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 bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/654#issuecomment-179386505
Very nice useage of `Enum` here!
Probably a knit-piking but may be also `SHIFT_ENTER` diserves a place there
too?
Looks great to me.
Alex -
I hestitate to respond at all since recently when a pmc member has
called for a "vote" it seems more that the purpose is to ratify
something that a few people have already privately agreed on.
But -- the last time Zeppelin applied for graduation was a month ago.
What happened then?
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/6#issuecomment-179430300
Hi - would you still be interested in completing this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user minahlee commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/685#issuecomment-179431380
@corneadoug Thank you for review. 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
Github user corneadoug commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/685#issuecomment-179438556
Since its the only problem I found, I would say LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on
52 matches
Mail list logo