[GitHub] incubator-zeppelin pull request: ZEPPELIN-547: Cannot select outpu...

2015-12-30 Thread prabhjyotsingh
GitHub user prabhjyotsingh opened a pull request: https://github.com/apache/incubator-zeppelin/pull/585 ZEPPELIN-547: Cannot select output of the paragraph ### What is this PR for? Cannot select error/output of the paragraph. Whenever there is a click on output the focus is s

[jira] [Created] (ZEPPELIN-547) Cannot select output of the paragraph

2015-12-30 Thread Prabhjyot Singh (JIRA)
Prabhjyot Singh created ZEPPELIN-547: Summary: Cannot select output of the paragraph Key: ZEPPELIN-547 URL: https://issues.apache.org/jira/browse/ZEPPELIN-547 Project: Zeppelin Issue Type

[GitHub] incubator-zeppelin pull request: Add a (local mode) Scalding Inter...

2015-12-30 Thread sriramkrishnan
Github user sriramkrishnan commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/561#issuecomment-168134305 @Leemoonsoo as you suggested, I have reverted commits for the LICENSE / files added under licenses dir, added -Pscalding flag, and updated the docs.

[GitHub] incubator-zeppelin pull request: Added Shiro security

2015-12-30 Thread elbamos
Github user elbamos commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/53#issuecomment-168122737 @hayssams Can you provide a very step-by-step intro readme? Default username/pass, what the authentication backend is, how users/groups are added, how to mak

Re: 2015: year in review

2015-12-30 Thread madhuka udantha
Wish all best for Zeppelin and happy new year for Zeppelin community!! On Thu, Dec 31, 2015 at 9:18 AM, Renjith Kamath wrote: > Alexander, Thanks for the 2015 review. Happy New Year > > Thanks & Regards, > RK > > On Thu, Dec 31, 2015 at 8:30 AM, Kevin (Sangwoo) Kim > wrote: > >> Great! Hope our

Re: 2015: year in review

2015-12-30 Thread Renjith Kamath
Alexander, Thanks for the 2015 review. Happy New Year Thanks & Regards, RK On Thu, Dec 31, 2015 at 8:30 AM, Kevin (Sangwoo) Kim wrote: > Great! Hope our community grows even more in New Year! > > > 2015년 12월 31일 (목) 오전 11:42, Jungtaek Lim 님이 작성: > >> Alexander, >> thanks for the great article!

[GitHub] incubator-zeppelin pull request: ZEPPELIN-545. Include Ignite 1.5....

2015-12-30 Thread jongyoul
Github user jongyoul commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/584#issuecomment-168113664 @c0s Okay. Thanks for quick 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 pro

[GitHub] incubator-zeppelin pull request: ZEPPELIN-545. Include Ignite 1.5....

2015-12-30 Thread c0s
Github user c0s commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/584#issuecomment-168113568 That's what I've said - the bits will be available in a day or two once the vote is over. Don't pull this one in yet. I have validated it to work just in my loca

Re: 2015: year in review

2015-12-30 Thread Kevin (Sangwoo) Kim
Great! Hope our community grows even more in New Year! 2015년 12월 31일 (목) 오전 11:42, Jungtaek Lim 님이 작성: > Alexander, > thanks for the great article! > > Happy new year all! > > Jungtaek Lim (HeartSaVioR) > > On Thu, Dec 31, 2015 at 8:00 AM, Alexander Bezzubov > wrote: > >> Dear fellow Zeppelin d

Re: 2015: year in review

2015-12-30 Thread moon soo Lee
Awesome! Happy New Year! On 2015년 12월 30일 (수) at 오후 6:42 Jungtaek Lim wrote: > Alexander, > thanks for the great article! > > Happy new year all! > > Jungtaek Lim (HeartSaVioR) > > On Thu, Dec 31, 2015 at 8:00 AM, Alexander Bezzubov > wrote: > >> Dear fellow Zeppelin developers and useres, >> >

[GitHub] incubator-zeppelin pull request: ZEPPELIN-545. Include Ignite 1.5....

2015-12-30 Thread jongyoul
Github user jongyoul commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/584#issuecomment-168113417 @c0s There is not 1.5.0.final in a maven repository and I've found 1.5.0-b1 only. Would it be resolved? --- If your project is set up for it, you can reply

Re: 2015: year in review

2015-12-30 Thread Jungtaek Lim
Alexander, thanks for the great article! Happy new year all! Jungtaek Lim (HeartSaVioR) On Thu, Dec 31, 2015 at 8:00 AM, Alexander Bezzubov wrote: > Dear fellow Zeppelin developers and useres, > > the year 2015 is about to end so I wanted to say thank you to everybody > here - its been a great

[GitHub] incubator-zeppelin pull request: ZEPPELIN-545. Include Ignite 1.5....

2015-12-30 Thread c0s
GitHub user c0s opened a pull request: https://github.com/apache/incubator-zeppelin/pull/584 ZEPPELIN-545. Include Ignite 1.5.0.final into next release of Zeppelin Ready for the review. The latest Ignite release will be published in the next day or so You can merge this pull reque

Re: 2015: year in review

2015-12-30 Thread Henry Saputra
Happy New Year to Zeppelin community =) - Henry On Wed, Dec 30, 2015 at 3:00 PM, Alexander Bezzubov wrote: > Dear fellow Zeppelin developers and useres, > > the year 2015 is about to end so I wanted to say thank you to everybody > here - its been a great year for the project indeed! > > Wish you

Re: Version handling in the JIRA

2015-12-30 Thread Konstantin Boudnik
On Wed, Dec 30, 2015 at 07:38AM, moon soo Lee wrote: > Make sense. If it is okay, let me move resolved issue from 0.5.1 to 0.5.5 > while they're included in 0.5.5-incubating and move open issue from 0.5.1 > from 0.6.0. Then nuke 0.5.1. Yup, good idea. > Thanks, > moon > > On Tue, Dec 29, 2015 at

Re: 2015: year in review

2015-12-30 Thread Hyung Sung Shim
Dear Alexander. Thank you for your Very good review and happy new year!! 2015년 12월 31일 목요일, Alexander Bezzubov님이 작성한 메시지: > Dear fellow Zeppelin developers and useres, > > the year 2015 is about to end so I wanted to say thank you to everybody > here - its been a great year for the project indee

[GitHub] incubator-zeppelin pull request: Add a (local mode) Scalding Inter...

2015-12-30 Thread Leemoonsoo
Github user Leemoonsoo commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/561#issuecomment-168101636 Apart from license for jgrapht, using 3rd party repo (conjars) need to be avoided. How about revert commits for the LICENSE / files added under licenses d

[GitHub] incubator-zeppelin pull request: Add a (local mode) Scalding Inter...

2015-12-30 Thread sriramkrishnan
Github user sriramkrishnan commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/561#issuecomment-168097018 Thanks @Leemoonsoo. So how should we proceed? Should I add it as LGPL? Also, are you OK with using the conjars repo now? Or do you recommend th

2015: year in review

2015-12-30 Thread Alexander Bezzubov
Dear fellow Zeppelin developers and useres, the year 2015 is about to end so I wanted to say thank you to everybody here - its been a great year for the project indeed! Wish you a happy new year and want to share a small review of Zeppelin in 2015 I did https://medium.com/@bzz_/apache-zeppelin-in

[GitHub] incubator-zeppelin pull request: Add a (local mode) Scalding Inter...

2015-12-30 Thread Leemoonsoo
Github user Leemoonsoo commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/561#issuecomment-168023202 fyi, i have got replied about license >> moon soo Lee >> Subject: Questions about license of jgrapht-jdk1.6:0.8.1 binary, like > > DEC

[GitHub] incubator-zeppelin pull request: JDBC generic interpreter

2015-12-30 Thread vrajat
Github user vrajat commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/361#issuecomment-168020790 I read your mail. I understand why you are following this process. I am voting for a requirement that seems to be missing in others but is satisfied in

[GitHub] incubator-zeppelin pull request: update error message and output s...

2015-12-30 Thread Leemoonsoo
Github user Leemoonsoo commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/583#issuecomment-168020692 Thanks @r-kamath for the contribution. The reason in the beginning code editor has vertical bar was, to distinguish it from the output. If out

[GitHub] incubator-zeppelin pull request: update error message and output s...

2015-12-30 Thread jongyoul
Github user jongyoul commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/583#issuecomment-168013639 Looks nice, too. --- 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 ha

[GitHub] incubator-zeppelin pull request: ZEPPELIN-544 ] After the restart ...

2015-12-30 Thread HeartSaVioR
Github user HeartSaVioR commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/581#issuecomment-168013136 Minor: How about extracting whole synchronized block to new private method? Actually setPropertyAndRestart() and restart() takes same logic except

[GitHub] incubator-zeppelin pull request: update error message and output s...

2015-12-30 Thread HeartSaVioR
Github user HeartSaVioR commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/583#issuecomment-168011185 LGTM. Looks nicer. --- 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] incubator-zeppelin pull request: JDBC generic interpreter

2015-12-30 Thread jongyoul
Github user jongyoul commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/361#issuecomment-168008003 @vrajat And I also think JDBC interpreter supports all kind of JDBC drivers. --- If your project is set up for it, you can reply to this email and have your

[GitHub] incubator-zeppelin pull request: JDBC generic interpreter

2015-12-30 Thread jongyoul
Github user jongyoul commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/361#issuecomment-168004929 @vrajat Thanks for taking an interest in this issue and being willing to contribute your code. I have a plan to merge several jdbc-like interpreters until 0

[DISCUSS] PR #208 - R Interpreter for Zeppelin

2015-12-30 Thread Eric Charles
Hi, I had a look at https://github.com/apache/incubator-zeppelin/pull/208 (and related Github repo https://github.com/elbamos/Zeppelin-With-R [1]) Here are a few topics for discussion based on my experience developing https://github.com/datalayer/zeppelin-R [2]. 1. rscala jar not in Maven R

[GitHub] incubator-zeppelin pull request: Added Shiro security

2015-12-30 Thread hayssams
Github user hayssams commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/53#issuecomment-168004206 I have just added a short [security readme](https://github.com/ebiznext/incubator-zeppelin/blob/3b276057a22c5569ea6f6cf1c5851b4aa5277e2f/Security-README.md)

[GitHub] incubator-zeppelin pull request: update error message and output s...

2015-12-30 Thread r-kamath
GitHub user r-kamath opened a pull request: https://github.com/apache/incubator-zeppelin/pull/583 update error message and output style ### What is this PR for? Styling text and error output ### What type of PR is it? Improvement ### How should this be teste

Re: [DISCUSS] Release 0.5.6-incubating

2015-12-30 Thread Khalid Huseynov
+1 for 0.5.6 release with current improvements/fixes. On Wed, Dec 30, 2015 at 4:10 PM, moon soo Lee wrote: > Amos, > > Who started the word "meaningful" is not important. > Release discussion will not be judgement of how meaningful/major/big the > contributions are. > > CI problem i have descri

[GitHub] incubator-zeppelin pull request: JDBC generic interpreter

2015-12-30 Thread vrajat
Github user vrajat commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/361#issuecomment-167984726 FWIW - I vote for this implementation of JDBC Interpreter. I understand that your focus is on well-known databases - mysql, postgres etc. I am working wit

[GitHub] incubator-zeppelin pull request: ZEPPELIN-541 - [WIP] increase log...

2015-12-30 Thread jongyoul
Github user jongyoul commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/579#issuecomment-167960756 +1 @HeartSaVioR --- 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 ha