date:20170604

GitHub user jongyoul reopened a pull request:

https://github.com/apache/zeppelin/pull/2393

[ZEPPELIN-2590] Convert jupyter's notebook to Zeppelin's note

### What is this PR for?
Converting jupyter's notebook to Zeppelin's note

### What type of PR is it?
[Feature]

### Todos
* [x] - Add command line interface

### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-2590

### How should this be tested?

### Screenshots (if appropriate)

### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jongyoul/zeppelin ZEPPELIN-2590

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zeppelin/pull/2393.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2393


commit 655cc4d7eb0a4b6790da90fffdf861d66e35ec88
Author: Jongyoul Lee 
Date:   2017-05-29T08:47:58Z

Added jupyter file format

commit a0f0c995aeb717b4291ca4d0b38fa4d5d120dbb5
Author: Jongyoul Lee 
Date:   2017-06-01T15:48:43Z

Added asf header

commit 87d200476300206b7ccc59d4ee0f6569c700034f
Author: Jongyoul Lee 
Date:   2017-06-02T02:03:36Z

Fixed typo

commit 4945f32a0ee6c9c0152b0ead372e1f22eab5820e
Author: Jongyoul Lee 
Date:   2017-06-02T02:37:56Z

Fixed style

commit 621fe1f514e01bda151d1938a4186e07502d3c91
Author: Jongyoul Lee 
Date:   2017-06-04T06:27:22Z

Added note format manually

commit 4e4cfda00a60f08f3e232447228e0a7aa0294331
Author: Jongyoul Lee 
Date:   2017-06-04T16:38:48Z

Added command line interface




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2372: [ZEPPELIN-2581] Shell ansi codes

2017-06-04 Thread DrIgor

Github user DrIgor commented on the issue:

https://github.com/apache/zeppelin/pull/2372
  
Any other questions?


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2356: [ZEPPELIN-2460] Highlight active line in editor

2017-06-04 Thread Leemoonsoo

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2356
  
Yeah, that was my guess. I think keeping layout unchanged is more important 
than prevent overlapping paragraph control and text editor. 


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2356: [ZEPPELIN-2460] Highlight active line in editor

2017-06-04 Thread 1ambda

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2356
  
@Leemoonsoo Hi, Thanks for the feedback. 

- it is actually intended. otherwise highlight color will override the 
paragraph setting menus. 
- let me find an another way (e.g applying `z-index`)


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2381: [gh-pages] [ZEPPELIN-2597] Updating offcial main websi...

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/2381
  
Um.. So, for quickly review, I'll separate this PR to 2 PR. 
1. updating navbar and main sections. 
2. adding technologies and deployments


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2381: [gh-pages] [ZEPPELIN-2597] Updating offcial main websi...

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/2381
  

![image](https://cloud.githubusercontent.com/assets/8110458/26771309/5e6b8b8e-49f8-11e7-941c-8efd7ef7c1e9.png)

this part is different between #2371. Let me update to match it.


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [DISCUSS] Release 0.7.2

+1

On Mon, Jun 5, 2017 at 10:57 AM, Khalid Huseynov  wrote:

> +1
>
> On Mon, Jun 5, 2017 at 9:49 AM, Hyung Sung Shim  wrote:
>
> > +1
> >
> > 2017-06-05 8:42 GMT+09:00 Jeff Zhang :
> >
> > > +1
> > >
> > > Ahyoung Ryu 于2017年6月5日周一 上午4:00写道：
> > >
> > > > +1 for the release
> > > >
> > > > On Sat, Jun 3, 2017 at 11:32 PM, 18637156...@163.com <
> > > 18637156...@163.com>
> > > > wrote:
> > > >
> > > > > +1 for release 0.7.2
> > > > >
> > > > >
> > > > >
> > > > > 18637156...@163.com
> > > > >
> > > > > From: moon soo Lee
> > > > > Date: 2017-06-04 01:47
> > > > > To: dev
> > > > > Subject: [DISCUSS] Release 0.7.2
> > > > > Hi,
> > > > >
> > > > > Since 0.7.1 release, we have resolved 38 issues and that includes
> > most
> > > of
> > > > > critical issues in 0.7.2 umbrella issue [1].
> > > > >
> > > > > Since 0.7.1 has major problems like ZEPPELIN-2336 [2], i'd like to
> > > > proceed
> > > > > release process for 0.7.2 at this point and provide stable release.
> > > > >
> > > > > Remaining issue can be resolved in 0.8.0 release (or 0.7.3 if
> another
> > > > > maintenance release is necessary).
> > > > >
> > > > > Shell we proceed to 0.7.2?
> > > > >
> > > > > Thanks,
> > > > > moon
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/ZEPPELIN-2276
> > > > > [2] https://issues.apache.org/jira/browse/ZEPPELIN-2336
> > > > >
> > > >
> > >
> >
>



-- 
이종열, Jongyoul Lee, 李宗烈
http://madeng.net

Re: Release 0.7.2

I saw another mailing thread now. Ignore it.

On Mon, Jun 5, 2017 at 1:45 PM, Jongyoul Lee  wrote:

> Hi all,
>
> We have umbrella issue for 0.7.2. See https://issues.apache.org/
> jira/browse/ZEPPELIN-2276
>
> I think it's almost done and there're some trivial issues which don't look
> like blockers. How about starting release process for 0.7.2? And I suggest
> moving remaining issues into 0.8.0.
>
> Regards,
> JL
>
> --
> 이종열, Jongyoul Lee, 李宗烈
> http://madeng.net
>



-- 
이종열, Jongyoul Lee, 李宗烈
http://madeng.net

Re: [DISCUSS] Reducing default interpreters while building and releasing Zeppelin

Felix,
Yes, I said a bit confused. I want to release Zeppelin with some - not-all
- interpreters, but deploy all interpreters into maven to install them if
users want to use them.

Moon,
I think it's the best to fit the list as same as homepage by default as it
makes users confused less. But if we want to add more interpreters, I think
mailing questions and related issues are one of the proper criteria.

Jeff,
Agreed. We already had a menu but it just shows how to use
install-interpreter.sh.

On Mon, Jun 5, 2017 at 9:36 AM, Jeff Zhang  wrote:

>
> If possible, we need to integrate the install script in zeppelin UI. As I
> would expect many users would ask why some interpreter is missing and how
> to install them.
>
>
>
> moon soo Lee 于2017年6月5日周一 上午2:06写道：
>
>> Following is last discussion related to release package size.
>>
>> https://lists.apache.org/thread.html/69f606409790d7ba11422e8c6df941
>> a75c5dfae0aca63eccf2f840bf@%3Cusers.zeppelin.apache.org%3E
>>
>> at this time, we have discussed about having bin-all (every
>> interpreters), bin-min (selected interpreters), bin-netinst (no
>> interpreters) package but didn't conclude the criteria and how we make a
>> decision.
>>
>> Jongyoul, do you have any idea about criteria?
>>
>> Thanks,
>> moon
>>
>> On Sun, Jun 4, 2017 at 10:47 AM Felix Cheung 
>> wrote:
>>
>>> Sure - I think it will be important to discuss what criteria to use to
>>> decide what is included vs what will be released separately.
>>>
>>> _
>>> From: Jongyoul Lee 
>>>
>> Sent: Sunday, June 4, 2017 9:47 AM
>>> Subject: Re: [DISCUSS] Reducing default interpreters while building and
>>> releasing Zeppelin
>>> To: dev 
>>>
>> Cc: 
>>>
>>
>>>
>>>
>>> It means we release with some interpreters and deploy all interpreters
>>> into
>>> maven separately. We already had a install-interpreter script inside it.
>>> If
>>> someone wants to install specific interpreter not included in default
>>> release package, they can use that script to install specific one.
>>>
>>> On Sun, Jun 4, 2017 at 9:11 AM, Felix Cheung 
>>> wrote:
>>>
>>> > Are we proposing some interpreters to be built and released separately?
>>> >
>>> > Is this going to be separate packaging? Or separate release pipeline?
>>> >
>>> >
>>> > _
>>> > From: Jongyoul Lee >> >>
>>> > Sent: Friday, June 2, 2017 11:04 PM
>>> > Subject: [DISCUSS] Reducing default interpreters while building and
>>> > releasing Zeppelin
>>>
>> > To: dev >> >>, <
>>>
>>
>>> > us...@zeppelin.apache.org>> >>
>>> >
>>> >
>>> > Hi dev and users,
>>> >
>>>
>> > Recently, zeppelin.apache.org is being
>>>
>>
>>> > changed for increasing user experiences and convenience. I like this
>>> kind
>>> > of changes. I, however, saw some arguments that which interpreters we
>>> will
>>> > locate in the first page. I'd like to expand its argument to the
>>> package we
>>> > release.
>>> >
>>> > Current zeppelin packages exceed 700MB with default option because
>>> > Zeppelin tried to include all interpreters by default. It was good at
>>> the
>>> > early age but, nowadays, Zeppelin community suffer from the size
>>> because
>>> > ASF infra allows the package size under 500MB. So I'd like to reduce
>>> the
>>> > package size by reducing default packages.
>>> >
>>> > In case of rebuilding homepage, community proposed some criteria
>>> including
>>> > mailing list and # of question in stackoverflow. I think we can adapt
>>> same
>>> > criteria into release version of Zeppelin.
>>> >
>>> > To handle this kind of issue, I think consensus of community is the
>>> most
>>> > important factor. If someone wants to have an idea to deal with it,
>>> please
>>> > feel free to talk about it.
>>> >
>>> > Thanks,
>>> > Jongyoul Lee
>>> >
>>> > --
>>> > 이종열, Jongyoul Lee, 李宗烈
>>> > http://madeng.net
>>> >
>>> >
>>> >
>>>
>>>
>>> --
>>> 이종열, Jongyoul Lee, 李宗烈
>>> http://madeng.net
>>>
>>>
>>>


-- 
이종열, Jongyoul Lee, 李宗烈
http://madeng.net

[GitHub] zeppelin issue #2371: [ZEPPELIN-2596] Improving documentation page

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/2371
  
Sorry for my late response
I quickly checked some navbar bug  about 
https://github.com/apache/zeppelin/pull/2381#issuecomment-305451690 and 
https://github.com/apache/zeppelin/pull/2381#issuecomment-305705051 in #2381. 
and this branch has same those bugs.
@1ambda, could you check those bugs?


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #1970: ZEPPELIN-2045. Pass interpreter properties with "spark...

2017-06-04 Thread zjffdu

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/1970
  
@orenpai IIUC, spark won't propagate non spark.* properties to executor. 
How does ElasticsEarch use these configuration. Does it only use it in driver 
side ?


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Release 0.7.2

Hi all,

We have umbrella issue for 0.7.2. See
https://issues.apache.org/jira/browse/ZEPPELIN-2276

I think it's almost done and there're some trivial issues which don't look
like blockers. How about starting release process for 0.7.2? And I suggest
moving remaining issues into 0.8.0.

Regards,
JL

-- 
이종열, Jongyoul Lee, 李宗烈
http://madeng.net

[GitHub] zeppelin issue #1970: ZEPPELIN-2045. Pass interpreter properties with "spark...

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/1970
  
@zjffdu Can you handle this issue?


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #2393: [ZEPPELIN-2590] Convert jupyter's notebook to Z...

Github user jongyoul closed the pull request at:

https://github.com/apache/zeppelin/pull/2393


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #2393: [ZEPPELIN-2590] Convert jupyter's notebook to Z...

GitHub user jongyoul reopened a pull request:

https://github.com/apache/zeppelin/pull/2393

[ZEPPELIN-2590] Convert jupyter's notebook to Zeppelin's note

### What is this PR for?
Converting jupyter's notebook to Zeppelin's note

### What type of PR is it?
[Feature]

### Todos
* [x] - Add command line interface

### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-2590

### How should this be tested?

### Screenshots (if appropriate)

### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jongyoul/zeppelin ZEPPELIN-2590

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zeppelin/pull/2393.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2393


commit 655cc4d7eb0a4b6790da90fffdf861d66e35ec88
Author: Jongyoul Lee 
Date:   2017-05-29T08:47:58Z

Added jupyter file format

commit a0f0c995aeb717b4291ca4d0b38fa4d5d120dbb5
Author: Jongyoul Lee 
Date:   2017-06-01T15:48:43Z

Added asf header

commit 87d200476300206b7ccc59d4ee0f6569c700034f
Author: Jongyoul Lee 
Date:   2017-06-02T02:03:36Z

Fixed typo

commit 4945f32a0ee6c9c0152b0ead372e1f22eab5820e
Author: Jongyoul Lee 
Date:   2017-06-02T02:37:56Z

Fixed style

commit 621fe1f514e01bda151d1938a4186e07502d3c91
Author: Jongyoul Lee 
Date:   2017-06-04T06:27:22Z

Added note format manually

commit 4e4cfda00a60f08f3e232447228e0a7aa0294331
Author: Jongyoul Lee 
Date:   2017-06-04T16:38:48Z

Added command line interface




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [DISCUSS] Release 0.7.2

2017-06-04 Thread Khalid Huseynov

+1

On Mon, Jun 5, 2017 at 9:49 AM, Hyung Sung Shim  wrote:

> +1
>
> 2017-06-05 8:42 GMT+09:00 Jeff Zhang :
>
> > +1
> >
> > Ahyoung Ryu 于2017年6月5日周一 上午4:00写道：
> >
> > > +1 for the release
> > >
> > > On Sat, Jun 3, 2017 at 11:32 PM, 18637156...@163.com <
> > 18637156...@163.com>
> > > wrote:
> > >
> > > > +1 for release 0.7.2
> > > >
> > > >
> > > >
> > > > 18637156...@163.com
> > > >
> > > > From: moon soo Lee
> > > > Date: 2017-06-04 01:47
> > > > To: dev
> > > > Subject: [DISCUSS] Release 0.7.2
> > > > Hi,
> > > >
> > > > Since 0.7.1 release, we have resolved 38 issues and that includes
> most
> > of
> > > > critical issues in 0.7.2 umbrella issue [1].
> > > >
> > > > Since 0.7.1 has major problems like ZEPPELIN-2336 [2], i'd like to
> > > proceed
> > > > release process for 0.7.2 at this point and provide stable release.
> > > >
> > > > Remaining issue can be resolved in 0.8.0 release (or 0.7.3 if another
> > > > maintenance release is necessary).
> > > >
> > > > Shell we proceed to 0.7.2?
> > > >
> > > > Thanks,
> > > > moon
> > > >
> > > > [1] https://issues.apache.org/jira/browse/ZEPPELIN-2276
> > > > [2] https://issues.apache.org/jira/browse/ZEPPELIN-2336
> > > >
> > >
> >
>

Re: [DISCUSS] Release 0.7.2

2017-06-04 Thread Hyung Sung Shim

+1

2017-06-05 8:42 GMT+09:00 Jeff Zhang :

> +1
>
> Ahyoung Ryu 于2017年6月5日周一 上午4:00写道：
>
> > +1 for the release
> >
> > On Sat, Jun 3, 2017 at 11:32 PM, 18637156...@163.com <
> 18637156...@163.com>
> > wrote:
> >
> > > +1 for release 0.7.2
> > >
> > >
> > >
> > > 18637156...@163.com
> > >
> > > From: moon soo Lee
> > > Date: 2017-06-04 01:47
> > > To: dev
> > > Subject: [DISCUSS] Release 0.7.2
> > > Hi,
> > >
> > > Since 0.7.1 release, we have resolved 38 issues and that includes most
> of
> > > critical issues in 0.7.2 umbrella issue [1].
> > >
> > > Since 0.7.1 has major problems like ZEPPELIN-2336 [2], i'd like to
> > proceed
> > > release process for 0.7.2 at this point and provide stable release.
> > >
> > > Remaining issue can be resolved in 0.8.0 release (or 0.7.3 if another
> > > maintenance release is necessary).
> > >
> > > Shell we proceed to 0.7.2?
> > >
> > > Thanks,
> > > moon
> > >
> > > [1] https://issues.apache.org/jira/browse/ZEPPELIN-2276
> > > [2] https://issues.apache.org/jira/browse/ZEPPELIN-2336
> > >
> >
>

Re: [DISCUSS] Reducing default interpreters while building and releasing Zeppelin

2017-06-04 Thread Jeff Zhang

If possible, we need to integrate the install script in zeppelin UI. As I
would expect many users would ask why some interpreter is missing and how
to install them.



moon soo Lee 于2017年6月5日周一 上午2:06写道：

> Following is last discussion related to release package size.
>
>
> https://lists.apache.org/thread.html/69f606409790d7ba11422e8c6df941a75c5dfae0aca63eccf2f840bf@%3Cusers.zeppelin.apache.org%3E
>
> at this time, we have discussed about having bin-all (every interpreters),
> bin-min (selected interpreters), bin-netinst (no interpreters) package but
> didn't conclude the criteria and how we make a decision.
>
> Jongyoul, do you have any idea about criteria?
>
> Thanks,
> moon
>
> On Sun, Jun 4, 2017 at 10:47 AM Felix Cheung 
> wrote:
>
>> Sure - I think it will be important to discuss what criteria to use to
>> decide what is included vs what will be released separately.
>>
>> _
>> From: Jongyoul Lee 
>>
> Sent: Sunday, June 4, 2017 9:47 AM
>> Subject: Re: [DISCUSS] Reducing default interpreters while building and
>> releasing Zeppelin
>> To: dev 
>>
> Cc: 
>>
>
>>
>>
>> It means we release with some interpreters and deploy all interpreters
>> into
>> maven separately. We already had a install-interpreter script inside it.
>> If
>> someone wants to install specific interpreter not included in default
>> release package, they can use that script to install specific one.
>>
>> On Sun, Jun 4, 2017 at 9:11 AM, Felix Cheung 
>> wrote:
>>
>> > Are we proposing some interpreters to be built and released separately?
>> >
>> > Is this going to be separate packaging? Or separate release pipeline?
>> >
>> >
>> > _
>> > From: Jongyoul Lee > >>
>> > Sent: Friday, June 2, 2017 11:04 PM
>> > Subject: [DISCUSS] Reducing default interpreters while building and
>> > releasing Zeppelin
>>
> > To: dev > >>, <
>>
>
>> > us...@zeppelin.apache.org> >>
>> >
>> >
>> > Hi dev and users,
>> >
>>
> > Recently, zeppelin.apache.org is being
>>
>
>> > changed for increasing user experiences and convenience. I like this
>> kind
>> > of changes. I, however, saw some arguments that which interpreters we
>> will
>> > locate in the first page. I'd like to expand its argument to the
>> package we
>> > release.
>> >
>> > Current zeppelin packages exceed 700MB with default option because
>> > Zeppelin tried to include all interpreters by default. It was good at
>> the
>> > early age but, nowadays, Zeppelin community suffer from the size because
>> > ASF infra allows the package size under 500MB. So I'd like to reduce the
>> > package size by reducing default packages.
>> >
>> > In case of rebuilding homepage, community proposed some criteria
>> including
>> > mailing list and # of question in stackoverflow. I think we can adapt
>> same
>> > criteria into release version of Zeppelin.
>> >
>> > To handle this kind of issue, I think consensus of community is the most
>> > important factor. If someone wants to have an idea to deal with it,
>> please
>> > feel free to talk about it.
>> >
>> > Thanks,
>> > Jongyoul Lee
>> >
>> > --
>> > 이종열, Jongyoul Lee, 李宗烈
>> > http://madeng.net
>> >
>> >
>> >
>>
>>
>> --
>> 이종열, Jongyoul Lee, 李宗烈
>> http://madeng.net
>>
>>
>>

[GitHub] zeppelin pull request #2388: [ZEPPELIN-2492] Use single Dockerfile for each ...

2017-06-04 Thread 1ambda

Github user 1ambda closed the pull request at:

https://github.com/apache/zeppelin/pull/2388


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2388: [ZEPPELIN-2492] Use single Dockerfile for each tag (br...

2017-06-04 Thread 1ambda

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2388
  
Thanks @jongyoul.


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [DISCUSS] Release 0.7.2

2017-06-04 Thread Jeff Zhang

+1

Ahyoung Ryu 于2017年6月5日周一 上午4:00写道：

> +1 for the release
>
> On Sat, Jun 3, 2017 at 11:32 PM, 18637156...@163.com <18637156...@163.com>
> wrote:
>
> > +1 for release 0.7.2
> >
> >
> >
> > 18637156...@163.com
> >
> > From: moon soo Lee
> > Date: 2017-06-04 01:47
> > To: dev
> > Subject: [DISCUSS] Release 0.7.2
> > Hi,
> >
> > Since 0.7.1 release, we have resolved 38 issues and that includes most of
> > critical issues in 0.7.2 umbrella issue [1].
> >
> > Since 0.7.1 has major problems like ZEPPELIN-2336 [2], i'd like to
> proceed
> > release process for 0.7.2 at this point and provide stable release.
> >
> > Remaining issue can be resolved in 0.8.0 release (or 0.7.3 if another
> > maintenance release is necessary).
> >
> > Shell we proceed to 0.7.2?
> >
> > Thanks,
> > moon
> >
> > [1] https://issues.apache.org/jira/browse/ZEPPELIN-2276
> > [2] https://issues.apache.org/jira/browse/ZEPPELIN-2336
> >
>

[GitHub] zeppelin issue #1970: ZEPPELIN-2045. Pass interpreter properties with "spark...

2017-06-04 Thread orenpai

Github user orenpai commented on the issue:

https://github.com/apache/zeppelin/pull/1970
  
@zjffdu @Leemoonsoo I believe this is a mistake, and poses a real problem 
for me and other Zeppelin users.
While it's true that the properties file is being skimmed to remove any 
non- spark.* properties, SparkConf.set allows it directly via code:

https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/SparkConf.scala#L84
There are many libraries like es-hadoop for ElasticSearch integration that 
depend on the SparkConf having non spark.* properties, such as "es.nodes".
Since Zeppelin does not allow a user to recreate the sc, this important 
mechanism of directly adding non spark properties via code is being blocked. I 
can't find any workaround either.


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2381: [WIP] [gh-pages] [ZEPPELIN-2597] Updating offcial main...

2017-06-04 Thread AhyoungRyu

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2381

Thank you for great work! Especially big +1 for adding this section

https://cloud.githubusercontent.com/assets/10060731/26764287/e5b90aa2-4918-11e7-908c-1fdfd4870037.png;>

I've always thought we need this kind of guide in first page of website.

I quickly look through the change and here are some thought in my head.

### 1. Navbar
- before
https://cloud.githubusercontent.com/assets/10060731/26764234/1be270e2-4918-11e7-976c-ed07289479b2.png;>

- after
https://cloud.githubusercontent.com/assets/10060731/26764235/1ec0bd82-4918-11e7-981c-4ba4f3c119b8.png;>

Adding "Quick Start" menu and switching menu order are really good idea I
think. But not sure about making the font size bigger and adding too much
shadow. So in my opinion, just below work will be enough.

- Adding "Quick Start" menu
- Switching menu order

### 2. Main
I also agree this part doesn't have really good looking.
https://cloud.githubusercontent.com/assets/10060731/26764349/4a00b96e-491a-11e7-9f06-6841bff11b50.png;>

But not sure the new change is definitely better than current one.
https://cloud.githubusercontent.com/assets/10060731/26764350/55ed2a46-491a-11e7-8f14-12cd3ff2385b.png;>

I think it'll be better to update other parts expect "Technologies" &
"Deployments" that you newly added in another PR step by step. That would be
easier to get review/ consensus from other ppl and also easier to make it
merged. I mean we can separate the work like below.

```
1. update navbar
2. update main section
3. adding "Technologies" & "Deployment" section
4. minor styling

```
What do you think?
Thanks again for staring this work.

---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2356: [ZEPPELIN-2460] Highlight active line in editor

2017-06-04 Thread Leemoonsoo

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2356
  
This PR makes unnecessary margin above the Editor inside of Paragraph.

before

![image](https://cloud.githubusercontent.com/assets/1540981/26764299/4640bb22-4919-11e7-8997-985178382583.png)

after

![image](https://cloud.githubusercontent.com/assets/1540981/26764294/21c1b1f2-4919-11e7-9274-1f22826a3699.png)

@1ambda Could you restore this margin to original?


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2393: [ZEPPELIN-2590] Convert jupyter's notebook to Zeppelin...

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2393
  
Made [ZEPPELIN-2616](https://issues.apache.org/jira/browse/ZEPPELIN-2616)


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (ZEPPELIN-2616) Add docs to describe how to use this feature

2017-06-04 Thread Jongyoul Lee (JIRA)

Jongyoul Lee created ZEPPELIN-2616:
--

 Summary: Add docs to describe how to use this feature
 Key: ZEPPELIN-2616
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2616
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: Jongyoul Lee
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zeppelin issue #2393: [ZEPPELIN-2590] Convert jupyter's notebook to Zeppelin...

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2393
  
Yes, sure. I'll made another PR for adding docs


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [DISCUSS] Release 0.7.2

2017-06-04 Thread DuyHai Doan

+1 too

On Sun, Jun 4, 2017 at 2:16 AM, Park Hoon <1am...@gmail.com> wrote:

> +1 for release 0.7.2 since  0.7.1 has few critical bugs.
>
>
> Thanks.
>
> On Sun, Jun 4, 2017 at 9:13 AM, Felix Cheung 
> wrote:
>
> > +1
> > 
> > From: moon soo Lee 
> > Sent: Saturday, June 3, 2017 10:47:39 AM
> > To: dev
> > Subject: [DISCUSS] Release 0.7.2
> >
> > Hi,
> >
> > Since 0.7.1 release, we have resolved 38 issues and that includes most of
> > critical issues in 0.7.2 umbrella issue [1].
> >
> > Since 0.7.1 has major problems like ZEPPELIN-2336 [2], i'd like to
> proceed
> > release process for 0.7.2 at this point and provide stable release.
> >
> > Remaining issue can be resolved in 0.8.0 release (or 0.7.3 if another
> > maintenance release is necessary).
> >
> > Shell we proceed to 0.7.2?
> >
> > Thanks,
> > moon
> >
> > [1] https://issues.apache.org/jira/browse/ZEPPELIN-2276
> > [2] https://issues.apache.org/jira/browse/ZEPPELIN-2336
> >
>

Re: [DISCUSS] Reducing default interpreters while building and releasing Zeppelin

2017-06-04 Thread Felix Cheung

Sure - I think it will be important to discuss what criteria to use to decide 
what is included vs what will be released separately.

_
From: Jongyoul Lee >
Sent: Sunday, June 4, 2017 9:47 AM
Subject: Re: [DISCUSS] Reducing default interpreters while building and 
releasing Zeppelin
To: dev >
Cc: >


It means we release with some interpreters and deploy all interpreters into
maven separately. We already had a install-interpreter script inside it. If
someone wants to install specific interpreter not included in default
release package, they can use that script to install specific one.

On Sun, Jun 4, 2017 at 9:11 AM, Felix Cheung 
>
wrote:

> Are we proposing some interpreters to be built and released separately?
>
> Is this going to be separate packaging? Or separate release pipeline?
>
>
> _
> From: Jongyoul Lee 
> >
> Sent: Friday, June 2, 2017 11:04 PM
> Subject: [DISCUSS] Reducing default interpreters while building and
> releasing Zeppelin
> To: dev 
> >,
>  <
> us...@zeppelin.apache.org>
>
>
> Hi dev and users,
>
> Recently, 
> zeppelin.apache.org 
> is being
> changed for increasing user experiences and convenience. I like this kind
> of changes. I, however, saw some arguments that which interpreters we will
> locate in the first page. I'd like to expand its argument to the package we
> release.
>
> Current zeppelin packages exceed 700MB with default option because
> Zeppelin tried to include all interpreters by default. It was good at the
> early age but, nowadays, Zeppelin community suffer from the size because
> ASF infra allows the package size under 500MB. So I'd like to reduce the
> package size by reducing default packages.
>
> In case of rebuilding homepage, community proposed some criteria including
> mailing list and # of question in stackoverflow. I think we can adapt same
> criteria into release version of Zeppelin.
>
> To handle this kind of issue, I think consensus of community is the most
> important factor. If someone wants to have an idea to deal with it, please
> feel free to talk about it.
>
> Thanks,
> Jongyoul Lee
>
> --
> 이종열, Jongyoul Lee, 李宗烈
> http://madeng.net
>
>
>


--
이종열, Jongyoul Lee, 李宗烈
http://madeng.net

[GitHub] zeppelin issue #2388: [ZEPPELIN-2492] Use single Dockerfile for each tag (br...

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2388
  
Can you close it by yourself?


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2282: [ZEPPELIN-2447] Fix python interpreter as to use max r...

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2282
  
ping.


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2369: [ZEPPELIN-2591] Show user info in spark job descriptio...

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2369
  
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 feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2388: [ZEPPELIN-2492] Use single Dockerfile for each tag (br...

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2388
  
I'll merge it 


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2393: [ZEPPELIN-2590] Convert jupyter's notebook to Zeppelin...

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2393
  
Ready to review. Please make sure it works with latest jupyter format with 
major version of 4


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [DISCUSS] Reducing default interpreters while building and releasing Zeppelin

It means we release with some interpreters and deploy all interpreters into
maven separately. We already had a install-interpreter script inside it. If
someone wants to install specific interpreter not included in default
release package, they can use that script to install specific one.

On Sun, Jun 4, 2017 at 9:11 AM, Felix Cheung 
wrote:

> Are we proposing some interpreters to be built and released separately?
>
> Is this going to be separate packaging? Or separate release pipeline?
>
>
> _
> From: Jongyoul Lee >
> Sent: Friday, June 2, 2017 11:04 PM
> Subject: [DISCUSS] Reducing default interpreters while building and
> releasing Zeppelin
> To: dev >, <
> us...@zeppelin.apache.org>
>
>
> Hi dev and users,
>
> Recently, zeppelin.apache.org is being
> changed for increasing user experiences and convenience. I like this kind
> of changes. I, however, saw some arguments that which interpreters we will
> locate in the first page. I'd like to expand its argument to the package we
> release.
>
> Current zeppelin packages exceed 700MB with default option because
> Zeppelin tried to include all interpreters by default. It was good at the
> early age but, nowadays, Zeppelin community suffer from the size because
> ASF infra allows the package size under 500MB. So I'd like to reduce the
> package size by reducing default packages.
>
> In case of rebuilding homepage, community proposed some criteria including
> mailing list and # of question in stackoverflow. I think we can adapt same
> criteria into release version of Zeppelin.
>
> To handle this kind of issue, I think consensus of community is the most
> important factor. If someone wants to have an idea to deal with it, please
> feel free to talk about it.
>
> Thanks,
> Jongyoul Lee
>
> --
> 이종열, Jongyoul Lee, 李宗烈
> http://madeng.net
>
>
>


-- 
이종열, Jongyoul Lee, 李宗烈
http://madeng.net

[GitHub] zeppelin pull request #2343: [ZEPPELIN-2538] JDBC completer improvements for...

2017-06-04 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/zeppelin/pull/2343


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2343: [ZEPPELIN-2538] JDBC completer improvements for work w...

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2343
  
LGTM. Will merge it now.


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2268: [ZEPPELIN-2403] interpreter property widgets

2017-06-04 Thread tinkoff-dwh

Github user tinkoff-dwh commented on the issue:

https://github.com/apache/zeppelin/pull/2268
  
Ready to 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 not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2309: [ZEPPELIN-2482] added font size for paragraph

2017-06-04 Thread tinkoff-dwh

Github user tinkoff-dwh commented on the issue:

https://github.com/apache/zeppelin/pull/2309
  
Ready to 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 not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2381: [WIP] [gh-pages] [ZEPPELIN-2597] Updating offcial main...