[GitHub] zeppelin issue #2506: [ZEPPELIN-2813] revisions comparator
Github user tinkoff-dwh commented on the issue: https://github.com/apache/zeppelin/pull/2506 @zjffdu 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. ---
[jira] [Created] (ZEPPELIN-2817) Support specify default interpreter in create notebook rest api
slee created ZEPPELIN-2817: -- Summary: Support specify default interpreter in create notebook rest api Key: ZEPPELIN-2817 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2817 Project: Zeppelin Issue Type: Improvement Components: rest-api Affects Versions: 0.7.2 Reporter: slee CreateNoteBook rest api supports setting note name and paragraphs at present, it should also support setting default interpreter as what we do in zeppelin web. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ZEPPELIN-2816) livy interpreter does not honour impersonation
Daniel Kozlowski created ZEPPELIN-2816: -- Summary: livy interpreter does not honour impersonation Key: ZEPPELIN-2816 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2816 Project: Zeppelin Issue Type: Bug Components: livy-interpreter Affects Versions: 0.7.0 Environment: OS: CentOS6 Ambari: 2.5.0.3 HDP: 2.6.1 Reporter: Daniel Kozlowski On one webUI run Zeppelin and log in as userA. On another webUI run Zeppelin and log in as userB. >From the zeppelin UI logged in as userA run: %livy.spark sc.sparkUser This starts a job in RM UI as userA and the output from the above query is: userA Now, go to the zeppelin UI where you are logged in as userB. This session uses the same job created by userA and the output of the query in that session is also userA. If you start running the query as userB, the job will start as userB and userA will see userB as the output from its query. Options -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] zeppelin issue #2502: [ZEPPELIN-2807] Passing Z variables to SQL Interpreter...
Github user sanjaydasgupta commented on the issue: https://github.com/apache/zeppelin/pull/2502 Thank you for the insight. Do you think we may retain variable substitution within literal strings as in the following contrived example? `%sql select * from spares where part_no = 'pump-{manufacturer-code}'` Thanks again for your 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 issue #2474: [ZEPPELIN-2753] Basic Implementation of IPython Interp...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2474 Just push another commit to use IPythonInterpreter first, if it is not available, I will fallback it to the old PythonInterpreter. --- 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 #2506: [ZEPPELIN-2813] revisions comparator
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2506 @tinkoff-dwh Do you mind to attach a gif for easy 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 #2462: ZEPPELIN-2527 Changed editor cursor to thin
Github user malayhm commented on the issue: https://github.com/apache/zeppelin/pull/2462 Updated screenshot: ![cursor-change-pr-after](https://user-images.githubusercontent.com/1881135/28693294-cb29f036-72d8-11e7-8029-511301b70209.gif) --- 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 #2507: [ZEPPELIN-2815] Improve interpreter dependencies loggi...
Github user necosta commented on the issue: https://github.com/apache/zeppelin/pull/2507 Hi @Leemoonsoo and others, should be a trivial one. Low priority. Many thanks --- 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 #2507: [ZEPPELIN-2815] Improve interpreter dependencie...
GitHub user necosta opened a pull request: https://github.com/apache/zeppelin/pull/2507 [ZEPPELIN-2815] Improve interpreter dependencies logging ### What is this PR for? As a developer, I want to be able to debug issues on dependency resolution "easier". To achieve this, making available (in debug mode), existing listeners. Also, exposing exceptions on dependency resolver. ### What type of PR is it? Improvement ### What is the Jira issue? * https://issues.apache.org/jira/browse/ZEPPELIN-2815 ### How should this be tested? Enable DEBUG logging mode. Import dependencies. Check detailed info. from dependency loading being logged. ### Questions: * Does the licenses files need update? N * Is there breaking changes for older versions? N * Does this needs documentation? N You can merge this pull request into a Git repository by running: $ git pull https://github.com/nokia/zeppelin zeppelin2815 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/2507.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 #2507 commit 06b8c23b0deafb9054574a9bad473bb7700bd480 Author: Nelson CostaDate: 2017-07-27T20:55:22Z [ZEPPELIN-2815] Improve interpreter dependencies logging --- 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-2815) Improve interpreter dependencies logging
Nelson Costa created ZEPPELIN-2815: -- Summary: Improve interpreter dependencies logging Key: ZEPPELIN-2815 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2815 Project: Zeppelin Issue Type: Improvement Affects Versions: 0.8.0 Reporter: Nelson Costa Assignee: Nelson Costa Priority: Minor Fix For: 0.8.0 As a developer, I want to be able to debug issues on dependency resolution "easier" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] zeppelin pull request #2505: [ZEPPELIN-2806] New paragraph does not displaye...
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/2505 --- 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-2814) Zeppelin doesn't show if interpreter is running or crashed
Ambud Sharma created ZEPPELIN-2814: -- Summary: Zeppelin doesn't show if interpreter is running or crashed Key: ZEPPELIN-2814 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2814 Project: Zeppelin Issue Type: Improvement Affects Versions: 0.6.0 Reporter: Ambud Sharma Zeppelin doesn't show if interpreter is running or crashed. If the interpreter dies due to bad settings this should be visible in the UI. E.g. livy interpreter crashes due to invalid configuration however one doesn't know about this until we try to run a query and even then it shows connection refused without showing connection refused to what port / server. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] zeppelin issue #2502: [ZEPPELIN-2807] Passing Z variables to SQL Interpreter...
Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/2502 I like what you propose, but think it might be very confusing for user if behavior changes depending on whether the variable is in the z context. for instance, it could be a shared notebook and someone might have set `what` and that would changes the outcome of the sql query example you have --- 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 #2506: Zeppelin 2813
GitHub user tinkoff-dwh opened a pull request: https://github.com/apache/zeppelin/pull/2506 Zeppelin 2813 ### What is this PR for? Sometimes need to see the difference between versions and to switch to another version and look for changes are not convenient (the page reloaded). This feature allows you to compare any two versions of the notebook. ### What type of PR is it? Feature ### What is the Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-2813 ### How should this be tested? 1 make some commits. Сchange the contents of paragraphs (delete, add, edit) 2 open Revisions comparator 3 compare revisions and check diff ### Screenshots (if appropriate) ![1](https://user-images.githubusercontent.com/25951039/28675980-e11f7134-7302-11e7-961c-f16a17daab62.png) ![2](https://user-images.githubusercontent.com/25951039/28675981-e1208772-7302-11e7-93bf-479bc628d103.png) ![3](https://user-images.githubusercontent.com/25951039/28675985-e1298002-7302-11e7-8d86-3f5dd0208ddd.png) ![4](https://user-images.githubusercontent.com/25951039/28675984-e1254fdc-7302-11e7-8e37-9e9266031e3e.png) ![5](https://user-images.githubusercontent.com/25951039/28675982-e123572c-7302-11e7-950e-a1fe2120c510.png) ![6](https://user-images.githubusercontent.com/25951039/28675983-e1250aae-7302-11e7-9c48-f2a2644b70fa.png) ![7](https://user-images.githubusercontent.com/25951039/28675986-e13c69f6-7302-11e7-8f27-b77a895c413c.png) if title exist ![8](https://user-images.githubusercontent.com/25951039/28675987-e13d8fc0-7302-11e7-92b8-704af189fdba.png) ### Questions: * Does the licenses files need update? yes (updated) * 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/tinkoff-dwh/zeppelin ZEPPELIN-2813 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/2506.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 #2506 commit a192b95dbb1f8b1cb07123194c77a12c28978eec Author: Tinkoff DWHDate: 2017-07-27T12:31:07Z [ZEPPELIN-2813] revisions comparator for note commit b9498142b40d80ba07581818011996a66056a9f3 Author: Tinkoff DWH Date: 2017-07-27T14:35:26Z [ZEPPELIN-2813] license --- 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-2813) Revisions comparator for note
Tinkoff DWH created ZEPPELIN-2813: - Summary: Revisions comparator for note Key: ZEPPELIN-2813 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2813 Project: Zeppelin Issue Type: New Feature Reporter: Tinkoff DWH Assignee: Tinkoff DWH Sometimes need to see the difference between versions and switch and watch (page reloaded) not convenient -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] zeppelin issue #2490: [Zeppelin-2718] Find and replace code in note
Github user tinkoff-dwh commented on the issue: https://github.com/apache/zeppelin/pull/2490 @1ambda 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 #2462: ZEPPELIN-2527 Changed editor cursor to thin
Github user malayhm commented on the issue: https://github.com/apache/zeppelin/pull/2462 @1ambda I have changed the fix and also verified it. It should show the thin cursor with latest changes. --- 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. ---