[GitHub] zeppelin issue #1954: [ZEPPELIN-525] Test failing in zeppelin-interpreter

2017-01-28 Thread felixcheung
Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/1954 look reasonable. CI is green, 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 project

[GitHub] zeppelin issue #1663: ZEPPELIN-1692: Ability to access Spark jobs UI from th...

2017-01-28 Thread felixcheung
Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/1663 I think it is related, right? ``` Caused by: org.openqa.selenium.NoSuchElementException: Unable to locate element:

[GitHub] zeppelin pull request #1955: [ZEPPELIN-2025] Cleanup R Tutorial

2017-01-28 Thread 1ambda
GitHub user 1ambda reopened a pull request: https://github.com/apache/zeppelin/pull/1955 [ZEPPELIN-2025] Cleanup R Tutorial ### What is this PR for? 1. Remove useless paragraphs in R tutorial 2. Prettify layout I attached screenshots for comparison. See the

[GitHub] zeppelin pull request #1955: [ZEPPELIN-2025] Cleanup R Tutorial

2017-01-28 Thread 1ambda
Github user 1ambda closed the pull request at: https://github.com/apache/zeppelin/pull/1955 --- 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

[GitHub] zeppelin pull request #1663: ZEPPELIN-1692: Ability to access Spark jobs UI ...

2017-01-28 Thread karuppayya
GitHub user karuppayya reopened a pull request: https://github.com/apache/zeppelin/pull/1663 ZEPPELIN-1692: Ability to access Spark jobs UI from the paragraph ### What is this PR for? A paragraph execution may result in spark job(s). Adding ability to access the spark job

[GitHub] zeppelin issue #1663: ZEPPELIN-1692: Ability to access Spark jobs UI from th...

2017-01-28 Thread karuppayya
Github user karuppayya commented on the issue: https://github.com/apache/zeppelin/pull/1663 I see the following errors in the SELENIUM test `org.openqa.selenium.NoSuchElementException: Unable to locate element: {"method":"xpath","selector":"//i[@tooltip='WebSocket

[GitHub] zeppelin pull request #1663: ZEPPELIN-1692: Ability to access Spark jobs UI ...

2017-01-28 Thread karuppayya
Github user karuppayya closed the pull request at: https://github.com/apache/zeppelin/pull/1663 --- 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

[GitHub] zeppelin issue #1663: ZEPPELIN-1692: Ability to access Spark jobs UI from th...

2017-01-28 Thread Leemoonsoo
Github user Leemoonsoo commented on the issue: https://github.com/apache/zeppelin/pull/1663 @karuppayya tried again with clean build and i don't see problem now. Maybe my test branch has been messed up. Now, two CI profiles are failing

[GitHub] zeppelin issue #1902: [ZEPPELIN-1821] Add HTTP client to elasticsearch inter...

2017-01-28 Thread Leemoonsoo
Github user Leemoonsoo commented on the issue: https://github.com/apache/zeppelin/pull/1902 CI failure looks unrelated, since it only removed commented-out code from last CI success. Thanks @bbonnin for great contribution. LGTM and merge to master if no further discussions!

[GitHub] zeppelin pull request #1936: [ZEPPELIN-2004] List all helium packages in Zep...

2017-01-28 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/1936 --- 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

[GitHub] zeppelin pull request #1949: [MINOR] Refactor to modern apis

2017-01-28 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/1949 --- 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

[GitHub] zeppelin issue #1955: [ZEPPELIN-2025] Cleanup R Tutorial

2017-01-28 Thread 1ambda
Github user 1ambda commented on the issue: https://github.com/apache/zeppelin/pull/1955 @minahlee Thanks for review! I updated notebook layout and it looks like ## Large Size

[GitHub] zeppelin pull request #1956: Groovy Interpreter

2017-01-28 Thread dlukyanov
Github user dlukyanov closed the pull request at: https://github.com/apache/zeppelin/pull/1956 --- 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

[GitHub] zeppelin issue #1956: Groovy Interpreter

2017-01-28 Thread dlukyanov
Github user dlukyanov commented on the issue: https://github.com/apache/zeppelin/pull/1956 wrong pull request --- 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

[GitHub] zeppelin issue #1663: ZEPPELIN-1692: Ability to access Spark jobs UI from th...

2017-01-28 Thread karuppayya
Github user karuppayya commented on the issue: https://github.com/apache/zeppelin/pull/1663 Than @Leemoonsoo for the explanation I am not able to repro it. The following two lines takes care of it 1.

[GitHub] zeppelin pull request #1956: Groovy Interpreter

2017-01-28 Thread dlukyanov
GitHub user dlukyanov opened a pull request: https://github.com/apache/zeppelin/pull/1956 Groovy Interpreter ### What is this PR for? Create a Groovy Interpreter ### What type of PR is it? Feature ### Todos * [Code] - Task * [Samples] - Task *

[GitHub] zeppelin pull request #1948: [ZEPPELIN-2016] add test case for cron job sche...

2017-01-28 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/1948 --- 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