[GitHub] zeppelin pull request #1427: [ZEPPELIN-1435] Move zeppelin-server-*.jar unde...
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/1427 --- 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 #1514: ZEPPELIN-1516. NPE LivySparkSQLInterpreter thrown with...
Github user prabhjyotsingh commented on the issue: https://github.com/apache/zeppelin/pull/1514 Sure, got it. 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 #1472: Add message of localhost:port on script
Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/1472 @djKooks Yeah right. Thanks for your consideration. And please do not hesitate if you want to contribute to Zeppelin next time. All ppl in the community will help you! --- 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 #1570: [MINOR] High definition build status badge
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/1570 --- 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 #1514: ZEPPELIN-1516. NPE LivySparkSQLInterpreter thrown with...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/1514 If you start livy.sql first, you will hit this issue, because userSessionMap is null. --- 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 #1564: [ZEPPELIN-1585] Testcase for PySparkInterpreter...
GitHub user astroshim reopened a pull request: https://github.com/apache/zeppelin/pull/1564 [ZEPPELIN-1585] Testcase for PySparkInterpreter. ### What is this PR for? This PR adds PySparkInterpreter testcase. ### What type of PR is it? Improvement ### What is the Jira issue? ### 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/astroshim/zeppelin feat/pySparkInterpreterTest Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1564.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 #1564 commit 499aa6bf3439b9e2524de59067f6d88eb6aec9bf Author: astroshimDate: 2016-10-19T23:31:04Z add PySparkInterpreter testcase commit 3fe0c7e4baf447756e8aeef218401e70a4d65041 Author: astroshim Date: 2016-10-21T10:55:15Z Merge branch 'master' into feat/pySparkInterpreterTest commit 51aa813f0e4a9c2000f72e1ec10279f9f9328915 Author: astroshim Date: 2016-10-21T14:43:45Z add PySparkInterpreter testcase. commit 265a82b93a66ec568bc3550c89b89fd562a403cb Author: astroshim Date: 2016-10-21T15:50:04Z change scope commit 1cf3fae3b912052722a2210efdc9dab009d85be6 Author: astroshim Date: 2016-10-26T04:13:50Z Merge branch 'master' into feat/pySparkInterpreterTest commit 3c7abf030de637fa614c7c811b704c0c17db107f Author: astroshim Date: 2016-10-30T06:56:35Z Merge branch 'master' into feat/pySparkInterpreterTest commit 5b39384bd5c6b154febedc2e61644ae7b9d3ccc7 Author: astroshim Date: 2016-10-31T11:30:46Z ignore testcase of spark 1.1 version commit 9650077f79237696c746988ae112a793f3dcc011 Author: astroshim Date: 2016-11-01T01:46:18Z apply spark.submit.pyFiles --- 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 #1514: ZEPPELIN-1516. NPE LivySparkSQLInterpreter thrown with...
Github user gss2002 commented on the issue: https://github.com/apache/zeppelin/pull/1514 @prabhjyotsingh I have only seen this issue with livy.sql as it is the only one that shares the HashMap between livy.spark and livy.sql. livy.sparkr and livy.pyspark do not share session info. In the future yes? --- 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 #1472: Add message of localhost:port on script
Github user djKooks commented on the issue: https://github.com/apache/zeppelin/pull/1472 @AhyoungRyu Actually, I was also thinking about whether this commit needs now. I'll drop this issue and maybe look it again after when it seems useful. Thanks for help. --- 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 #1567: [ZEPPELIN-1586] Add security check in NotebookR...
GitHub user anthonycorbacho reopened a pull request: https://github.com/apache/zeppelin/pull/1567 [ZEPPELIN-1586] Add security check in NotebookRestApi ### What is this PR for? Bring some security check in `NotebookRestApi`. ### What type of PR is it? [Bug Fix | Improvement | Refactoring] ### Todos - [x] - Create a proper way to throw webapp error - [x] - Add in `NotebookAuthorization` some method to check if user is owner, reader or writer - [ ] - Add Authorization check in `NotebookRestapi` ### What is the Jira issue? - [ZEPPELIN-1586](https://issues.apache.org/jira/browse/ZEPPELIN-1586) ### How should this be tested? First, force Zeppelin to use auth. - In `conf/zeppelin-site.xml` change `zeppelin.anonymous.allowed` to **false** ``` zeppelin.anonymous.allowed false Anonymous user allowed by default ``` - In `conf/shiro.ini` set Shiro to use `Auth` at the end of the file ``` #/** = anon /** = authc ``` - Start Zeppelin, login and set some permission to a note - try to get a note from Zeppelin Rest Api `http://localhost:8080/api/notebook/{noteId}` (you can use your browser or curl (if you use curl please add shiro token to curl cookie)) ### Screenshots (if appropriate) ![note_permission_rest_api](https://cloud.githubusercontent.com/assets/3139557/19827600/ffd68a06-9dea-11e6-8dd5-43f3bd401011.gif) ### Questions: - Does the licenses files need update? No - Is there breaking changes for older versions? No - Does this needs documentation? Maybe You can merge this pull request into a Git repository by running: $ git pull https://github.com/anthonycorbacho/incubator-zeppelin fix/ZEPPELIN-1586 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1567.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 #1567 commit a69a4e10c46452dcaaf8174c37e51705d6bc3214 Author: Anthony CorbachoDate: 2016-10-28T05:49:10Z Add new method on ZeppelinConfiguration to get is zeppelin is running on anonimous mode or not commit 859fba52799bc1690b0726dc6dc672f9c4b016a7 Author: Anthony Corbacho Date: 2016-10-28T07:22:13Z Add new method to help to determinate if user is part of writer and/or owner for the given note commit 67c63148233c0bf31715c9d97b37f4702fb3d2e6 Author: Anthony Corbacho Date: 2016-10-28T09:56:04Z Add new method to check if user and roles are member of the note (at least owner, reader, writer) commit 43ec38932300db156a602507ae82a34a0b416257 Author: Anthony Corbacho Date: 2016-10-28T09:57:06Z Replace check of aninonimous by method commit 860f4b4ff789ac7087932920f71a73b30cbc9ba8 Author: Anthony Corbacho Date: 2016-10-28T11:19:32Z Add webapp exception handler :) commit 01bec7ae0ece70fe5eed6f068bc40b4cc61ffd8d Author: Anthony Corbacho Date: 2016-10-28T11:19:54Z Handle security check commit c0b98ffe2f1a3c4ee005ffe8b376bdc507eab2f0 Author: Anthony Corbacho Date: 2016-10-29T05:58:04Z Rename permission check note :: be more meaningful commit a1cc1b81bd8f69f068803e6e87d110805905a039 Author: Anthony Corbacho Date: 2016-11-01T03:33:20Z Change cxf version from 2.7.7 to 2.7.8 to avoid method not found where throw WebAppException --- 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 #1564: [ZEPPELIN-1585] Testcase for PySparkInterpreter...
Github user astroshim closed the pull request at: https://github.com/apache/zeppelin/pull/1564 --- 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 #1573: [DOC] Add `/ws` for nginx websocket configurati...
GitHub user m30m opened a pull request: https://github.com/apache/zeppelin/pull/1573 [DOC] Add `/ws` for nginx websocket configuration ### What is this PR for? It's a bit misleading that both regular webserver location and websocket location use the exact same address. It's better to specify that websocket requests should be proxy-passed to `/ws` subdirectory. ### What type of PR is it? Documentation ### 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/m30m/zeppelin patch-2 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1573.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 #1573 commit aa60fd51eff4945ce1e68bd22595eba8ae3d8d8b Author: Mohammad Amin Khashkhashi MoghaddamDate: 2016-10-31T19:07:52Z Add `/ws` for nginx websocket configuration It's a bit misleading that both regular webserver location and websocket location use the exact same address. It's better to specify that websocket requests should be proxy-passed to `/ws` subdirectory. --- 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 #1339: [ZEPPELIN-1332] Remove spark-dependencies & sug...
Github user AhyoungRyu closed the pull request at: https://github.com/apache/zeppelin/pull/1339 --- 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 #1571: [DOC] Update shiro after merging #1568
Github user anthonycorbacho closed the pull request at: https://github.com/apache/zeppelin/pull/1571 --- 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 #1571: [DOC] Update shiro after merging #1568
GitHub user anthonycorbacho reopened a pull request: https://github.com/apache/zeppelin/pull/1571 [DOC] Update shiro after merging #1568 ### What is this PR for? A simple update of the documentation to let user know how that they need to copy `shiro.ini.template` to `shiro.ini` ### What type of PR is it? [Documentation] ### Screenshots (if appropriate) ![screen shot 2016-10-31 at 7 08 09 pm](https://cloud.githubusercontent.com/assets/3139557/19850732/6466763a-9f9d-11e6-9949-d58740d6c229.png) ### 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/anthonycorbacho/incubator-zeppelin doc/ShiroTemplate Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1571.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 #1571 commit 3f11260cf6883154bec3ce036f669bc009dab9ca Author: Anthony CorbachoDate: 2016-10-31T10:05:28Z Update shiro part about coping shiro.ini.template to shiro.ini in conf commit f933a6a0f6704e87084b7e12a784e89b7d38eb37 Author: Anthony Corbacho Date: 2016-10-31T10:09:06Z Fix typo commit bcba1dbdb4add485c34bd7cef29afa4673c9b70b Author: Anthony Corbacho Date: 2016-10-31T10:48:39Z Fix typo number 2 Yo commit 2f73f56624da52304076c88ce8c0d282166fe118 Author: Anthony Corbacho Date: 2016-10-31T13:43:29Z Fix typo :: copy -> cp ^^ --- 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 #1565: [ZEPPELIN-1564] Enable note deletion and paragraph out...
Github user minahlee commented on the issue: https://github.com/apache/zeppelin/pull/1565 Hi @tae-jun, thank you for your interest. I had to rebase this branch to resolve conflict so you will need too since it is based on mine. I am planning to finish this PR once #1567 merged so that I can handle permission issue. It will speed up merging process if you can review it (I am also going to review it as soon as all the tasks are done). About the jira, there is nothing stops you from creating one so feel free to create a ticket on Jira. And make sure that you assign your self on that task, and put `PROGRESS` label so everyone can see that you are working on it. And for the PR, I suggest you to do the cherry pick after #1567, #1565 merged, otherwise it will cause some confusion for the ones who don't know the context. --- 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 #1557: ZEPPELIN-1577. LivyInterpreter should not use F...
GitHub user zjffdu reopened a pull request: https://github.com/apache/zeppelin/pull/1557 ZEPPELIN-1577. LivyInterpreter should not use FIFOScheduler ### What is this PR for? This PR create a new scheduler FIFOPerUserScheduler. So that each user's request is isolated. and it is FIFOSchduler per user. ### What type of PR is it? [Bug Fix | Improvement] ### Todos - [ ] - Task ### What is the Jira issue? - https://issues.apache.org/jira/browse/ZEPPELIN-1577 ### How should this be tested? Tested manually ### 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/zjffdu/zeppelin ZEPPELIN-1577 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1557.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 #1557 commit d14e8bd821509389666cd22ff7888a30c634e48a Author: Jeff ZhangDate: 2016-10-16T07:06:17Z ZEPPELIN-1577. LivyInterpreter should not use FIFOScheduler commit a9e273ff0f5b7a285749a616046e7d5fb8603523 Author: Jeff Zhang Date: 2016-10-27T08:40:08Z add test commit 86d937e2da2dbbabcaca675b64e1984e5dba98d3 Author: Jeff Zhang Date: 2016-10-31T09:01:12Z fix unit test --- 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 #1557: ZEPPELIN-1577. LivyInterpreter should not use F...
Github user zjffdu closed the pull request at: https://github.com/apache/zeppelin/pull/1557 --- 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 #1565: [ZEPPELIN-1564] Enable note deletion and paragraph out...
Github user tae-jun commented on the issue: https://github.com/apache/zeppelin/pull/1565 Hi @minahlee :) This is a cool feature! I have an experience that deleted output through editing note.json because of huge output stopping Zeppelin web. By the way, I've wanted a renaming folder feature. So as soon as I saw this PR, I implemented renaming note, and I am almost done with implementing renaming folder! (I saw you are planning this after coding, sorry ð¢) This is a really good example for implementing it! So, the question is this: My branch is based on your PR's branch. How should I create JIRA issue? As well as PR. Is it easy to wait to merge this PR? --- 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 #1571: [DOC] Update shiro after merging #1568
Github user anthonycorbacho commented on the issue: https://github.com/apache/zeppelin/pull/1571 merging if no more discussion --- 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 #1471: Closes [ZEPPELIN-1505] Add Scio interpreter
Github user ravwojdyla commented on the issue: https://github.com/apache/zeppelin/pull/1471 @felixcheung correct - i missed it - updated doc/examples. --- 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 #1571: [DOC] Update shiro after merging #1568
Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/1571 @anthonycorbacho LooksGreatToMe ð --- 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 #1564: [ZEPPELIN-1585] Testcase for PySparkInterpreter.
Github user minahlee commented on the issue: https://github.com/apache/zeppelin/pull/1564 It would be nice if I can see all CI profiles pass. --- 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 #1564: [ZEPPELIN-1585] Testcase for PySparkInterpreter.
Github user astroshim commented on the issue: https://github.com/apache/zeppelin/pull/1564 @minahlee I fixed it. Thank you for proper 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 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 #1572: [ZEPPELIN-1593] Enforce sorting on dynamic form...
GitHub user trengrj opened a pull request: https://github.com/apache/zeppelin/pull/1572 [ZEPPELIN-1593] Enforce sorting on dynamic form elements ### What is this PR for? Current dynamic forms elements in zeppelin-web have no ordering. The ordering of the dynamic elements is random which can be annoying when you have many of them. The root cause is that the angular frontend uses "for key in object" pattern with no sorting. I have added sorting. ### What type of PR is it? Improvement ### What is the Jira issue? [ZEPPELIN-1593](https://issues.apache.org/jira/browse/ZEPPELIN-1593) ### How should this be tested? Dynamic forms should now have fields sorted by name. ``` %md ${a=1} ${b=1} ${c=1} ${d=1} ${bb=1} ${ba=1} ``` ### 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/trengrj/zeppelin sort-form Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1572.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 #1572 commit 7ba9a3ba23b4a744d957474f2c4e922dc885f597 Author: John TrengroveDate: 2016-10-31T11:40:43Z [ZEPPELIN-1593] Enforce sorting on dynamic form elements --- 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-1593) Sort Dynamic Forms by Name
John Trengrove created ZEPPELIN-1593: Summary: Sort Dynamic Forms by Name Key: ZEPPELIN-1593 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1593 Project: Zeppelin Issue Type: Improvement Components: GUI Affects Versions: 0.6.2 Environment: Reproduced on 0.6.2 and master branch Reporter: John Trengrove Priority: Minor Current dynamic forms elements in zeppelin-web have no ordering. The ordering of the dynamic elements is random which can be annoying when you have many of them. The root cause is that the angular frontend uses "for key in object" pattern with no sorting. I have a patch for this which sorts by name and will provide a PR. Issue also mentioned here https://community.hortonworks.com/questions/61441/zeppelin-dynamic-input-forms-order.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] zeppelin issue #1559: [ZEPPELIN-1461] Doesn't display "description" value in...
Github user minahlee commented on the issue: https://github.com/apache/zeppelin/pull/1559 @jongyoul Done :) --- 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 #1571: [DOC] Update shiro after merging #1568
GitHub user anthonycorbacho opened a pull request: https://github.com/apache/zeppelin/pull/1571 [DOC] Update shiro after merging #1568 ### What is this PR for? A simple update of the documentation to let user know how that they need to copy `shiro.ini.template` to `shiro.ini` ### What type of PR is it? [Documentation] ### Screenshots (if appropriate) ![screen shot 2016-10-31 at 7 08 09 pm](https://cloud.githubusercontent.com/assets/3139557/19850732/6466763a-9f9d-11e6-9949-d58740d6c229.png) ### 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/anthonycorbacho/incubator-zeppelin doc/ShiroTemplate Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1571.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 #1571 commit 3f11260cf6883154bec3ce036f669bc009dab9ca Author: Anthony CorbachoDate: 2016-10-31T10:05:28Z Update shiro part about coping shiro.ini.template to shiro.ini in conf --- 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 #1472: Add message of localhost:port on script
Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/1472 @djKooks And in my personal opinion, I wonder we need to print wireless network address in shell window since it changes depending on the user's network environment. What do you think? --- 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 #1447: [ZEPPELIN-1293] Re-create Livy session if it's lost
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/1447 Sorry for late response. @spektom Could you add some additional message of session recreation to be displayed in frontend. Because if session is recreated, we may need to rerun all the paragraphs, without knowing session recreationusers may be confused for errors like some variables are not defined. --- 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-1592) Threads not termiated when repeating the notebook execution
Hyukjin Kwon created ZEPPELIN-1592: -- Summary: Threads not termiated when repeating the notebook execution Key: ZEPPELIN-1592 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1592 Project: Zeppelin Issue Type: Bug Affects Versions: 0.6.0 Environment: CentOS release 6.8 (Final) Reporter: Hyukjin Kwon It seems threads are not cleaned and terminated after running multiple times the notebooks. For example, I just created a note book and then just ran the codes below: {code} case class Person(name: String, age: Long) val df = Seq(Person("Andy", 32)).toDF() df.show() {code} and I found the Zepplin process as below {code} iris 20745 1 3 17:45 pts/500:00:40 .../java -Dfile.encoding=UTF-8 -Xms1024m -Xmx1024m -XX:MaxPermSize=512m -Dlog4j.configuration=file:///.../zeppelin/conf/log4j.properties -Dzeppelin.log.file=.../zeppelin/logs/zeppelin-iris-IRIS-A01.log -cp ::.../zeppelin/lib/*:.../zeppelin/*::.../zeppelin/conf org.apache.zeppelin.server.ZeppelinServer {code} and then check the thread count via the command as below: {code} ps huH p 20745 | wc -l {code} I just realised that it actually never decreases. When I run a notebook, it seems it makes two threads but only one of them seems terminated. {code} $ ps huH p 20745 | wc -l 56 $ ps huH p 20745 | wc -l 59 $ ps huH p 20745 | wc -l 60 $ ps huH p 20745 | wc -l 60 $ ps huH p 20745 | wc -l 61 $ ps huH p 20745 | wc -l 61 $ ps huH p 20745 | wc -l 63 $ ps huH p 20745 | wc -l 62 $ ps huH p 20745 | wc -l 62 {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] zeppelin issue #1564: [ZEPPELIN-1585] Testcase for PySparkInterpreter.
Github user minahlee commented on the issue: https://github.com/apache/zeppelin/pull/1564 Zeppelin doesn't support pyspark with Spark 1.1.x. You might need to add `if` clasue to skip pyspark test for Spark 1.1.x. --- 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 #1548: [ZEPPELIN-917] Apply new mechanism to LensInter...
GitHub user meenakshisekar reopened a pull request: https://github.com/apache/zeppelin/pull/1548 [ZEPPELIN-917] Apply new mechanism to LensInterpreter ### What is this PR for? This handles replacing the registration of interpreter with static block by the interpreter-setting.json file ### What type of PR is it? [| Improvement | ### Todos Sub-Task ### What is the Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-917 ### How should this be tested? here shouldn't be any warning like below on starting the server INFO [2016-09-29 00:25:46,247]({main} LensInterpreter.java[]:155) - Bootstrapping Cassandra Interpreter WARN [2016-09-29 00:25:46,250]({main} Interpreter.java[register]:347) - Static initialization is deprecated for interpreter lens, You should change it to use interpreter-setting.json in your jar or interpreter/{interpreter}/interpreter-setting.json INFO [2016-09-29 00:25:46,250]({main} InterpreterFactory.java[init]:204) - Inclass=org.apache.zeppelin.lens.LensInterpreter And ensure that the lens related paragraphs run without any error ### 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/meenakshisekar/zeppelin ZEPPELIN-917 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1548.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 #1548 commit db2827f867199cdd5e3fe2bc05f614dd88e013f5 Author: meenakshisekarDate: 2016-10-21T09:59:38Z Commented the properties in interpreter file and added setting file. commit f94c8a3d44d441174fff2e89708e9ec62c1f5d22 Author: meenakshisekar Date: 2016-10-21T11:41:58Z Commented the properties in interpreter file and added setting file. commit ad3b83ca856c54727f1ffef324f187f69a276c83 Author: meenakshisekar Date: 2016-10-24T11:57:46Z Added indentation commit 2cba9e74df90073bd03c2867a70c345e5346dc7e Author: meenakshisekar Date: 2016-10-27T07:12:54Z Added the indentation similar to other interpreter setting file. commit cc8bdc274f581e7725307e2a4706b4d8ce4e243c Author: meenakshisekar Date: 2016-10-27T07:12:54Z Added the indentation similar to other interpreter setting file. commit 269e8cb3c547d5f1ea932c571206c13931a462ca Author: meenakshisekar Date: 2016-10-27T08:02:10Z Removed the tabs and added space. --- 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 #1548: [ZEPPELIN-917] Apply new mechanism to LensInterpreter
Github user meenakshisekar commented on the issue: https://github.com/apache/zeppelin/pull/1548 Reopening for travis build. --- 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 #1548: [ZEPPELIN-917] Apply new mechanism to LensInter...
Github user meenakshisekar closed the pull request at: https://github.com/apache/zeppelin/pull/1548 --- 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 #1570: [MINOR] High definition build status badge
Github user tae-jun commented on the issue: https://github.com/apache/zeppelin/pull/1570 Thanks @AhyoungRyu ! --- 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 #1568: [ZEPPELIN-1590] Move shiro.ini to shiro.ini.template
Github user minahlee commented on the issue: https://github.com/apache/zeppelin/pull/1568 @anthonycorbacho It is already merged, but I think there are some places to be updated in docs. Do you mind to take care of them? --- 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 #1472: Add message of localhost:port on script
Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/1472 @djKooks Sorry for my late response. Tested again and it works as expected only when I'm using wireless interpreter. If I connected wired internet, it doesn't print host info as below ``` $ ./bin/zeppelin-daemon.sh restart Zeppelin stop [ OK ] Browse :8080 in your browser. If you are testing on your local computer, use localhost:8080 Zeppelin start [ OK ] ``` Can you check again this? --- 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 #1520: [ZEPPELIN-1061] Select default interpreter while creat...
Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/1520 @kavinkumarks Tested and it works well as expected! Thanks again :) Merging this into master if there are 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 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 #1514: ZEPPELIN-1516. NPE LivySparkSQLInterpreter thro...
Github user zjffdu closed the pull request at: https://github.com/apache/zeppelin/pull/1514 --- 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 #1557: ZEPPELIN-1577. LivyInterpreter should not use F...
GitHub user zjffdu reopened a pull request: https://github.com/apache/zeppelin/pull/1557 ZEPPELIN-1577. LivyInterpreter should not use FIFOScheduler ### What is this PR for? This PR create a new scheduler FIFOPerUserScheduler. So that each user's request is isolated. and it is FIFOSchduler per user. ### What type of PR is it? [Bug Fix | Improvement] ### Todos - [ ] - Task ### What is the Jira issue? - https://issues.apache.org/jira/browse/ZEPPELIN-1577 ### How should this be tested? Tested manually ### 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/zjffdu/zeppelin ZEPPELIN-1577 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1557.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 #1557 commit d14e8bd821509389666cd22ff7888a30c634e48a Author: Jeff ZhangDate: 2016-10-16T07:06:17Z ZEPPELIN-1577. LivyInterpreter should not use FIFOScheduler commit a9e273ff0f5b7a285749a616046e7d5fb8603523 Author: Jeff Zhang Date: 2016-10-27T08:40:08Z add test --- 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 #1557: ZEPPELIN-1577. LivyInterpreter should not use F...
Github user zjffdu closed the pull request at: https://github.com/apache/zeppelin/pull/1557 --- 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 #1514: ZEPPELIN-1516. NPE LivySparkSQLInterpreter thro...
GitHub user zjffdu reopened a pull request: https://github.com/apache/zeppelin/pull/1514 ZEPPELIN-1516. NPE LivySparkSQLInterpreter thrown with %livy.sql interpreter ### What is this PR for? This PR fixed NPE issue in `LivySparkSQLIntepreter`, also it resolves the multiple thread issues discussed in #1503 ### What type of PR is it? [Bug Fix] ### Todos - [ ] - Task ### What is the Jira issue? - https://issues.apache.org/jira/browse/ZEPPELIN-1516 ### How should this be tested? - Enable shiro - Log in 2 users in 2 browsers - Start livy sql paragraph at almost the same time - 2 livy sessions are created correctly. ### 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/zjffdu/zeppelin ZEPPELIN-1516 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1514.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 #1514 commit 0b5825c6769ecb3382c4d2569380fde70d8a032b Author: Jeff ZhangDate: 2016-10-14T01:27:52Z ZEPPELIN-1516. NPE LivySparkSQLInterpreter thrown with %livy.sql interpreter commit fc5692df27ed4d2313b0c0d43bcc26f11efab5f3 Author: Jeff Zhang Date: 2016-10-27T05:38:03Z add test --- 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. ---