[GitHub] zeppelin issue #1946: [ZEPPELIN-921] Apply new mechanism to KnitR and RRepl
Github user DrIgor commented on the issue: https://github.com/apache/zeppelin/pull/1946 Rebased on master and ran build. I tried several times: - https://travis-ci.org/apache/zeppelin/builds/197341657 - https://travis-ci.org/apache/zeppelin/builds/197539698 - https://travis-ci.org/apache/zeppelin/builds/197547341 CI is still red, but every time it had a different failure. I think they are not caused by my 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. ---
[GitHub] zeppelin issue #1929: [ZEPPELIN-1997] Added derbylog in .gitignore
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/1929 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 pull request #1961: [ZEPPELIN-1934] maven-assembly-plugin fails mak...
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/1961 --- 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 #1945: [ZEPPELIN-2003] Remove PostgresqlInterpreter
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/1945 --- 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 #1960: [ZEPPELIN-2030] Select statement doesn't work i...
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/1960 --- 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 #1946: [ZEPPELIN-921] Apply new mechanism to KnitR and...
Github user DrIgor closed the pull request at: https://github.com/apache/zeppelin/pull/1946 --- 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 #1946: [ZEPPELIN-921] Apply new mechanism to KnitR and...
GitHub user DrIgor reopened a pull request: https://github.com/apache/zeppelin/pull/1946 [ZEPPELIN-921] Apply new mechanism to KnitR and RRepl ### What is this PR for? Applies new registration mechanism for R interpreter ### What type of PR is it? [Refactoring] ### What is the Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-921 ### How should this be tested? Build zeppelin with R profile enabled and run several R snippets ### 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/DrIgor/zeppelin ZEPPELIN-921 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1946.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 #1946 commit a76a41d7dd538eb47522d6bf53e7aecdf65f3829 Author: Igor DrozdovDate: 2017-01-25T08:36:53Z New registration mechanism for R interpreter --- 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 #1929: [ZEPPELIN-1997] Added derbylog in .gitignore
Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/1929 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 pull request #1930: [ZEPPELIN-1886] implementation z.getZeppelinJob...
GitHub user cloverhearts reopened a pull request: https://github.com/apache/zeppelin/pull/1930 [ZEPPELIN-1886] implementation z.getZeppelinJobStatus ### What is this PR for? You can get the state of a paragraph through ZeppelinContext. This allows you to implement code according to the paragraph condition. related https://github.com/apache/zeppelin/pull/1799 ### What type of PR is it? Feature ### What is the Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-1886 ### How should this be tested? 1. run paragraph. 2. Record the noteid and paragraph id of the paragraph you have run. 3. You can use the following code: for example ``` %spark z.getJobStatus("noteID", "paragraphId").name() z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isFinished() z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isAbort() z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isError() z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isPending() z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isRunning() ``` ### Screenshots (if appropriate) ![zeppelinstatus](https://cloud.githubusercontent.com/assets/10525473/22175433/770168b2-dfa9-11e6-8471-5dfa92e56eaa.png) ### Questions: * Does the licenses files need update? no * Is there breaking changes for older versions? no * Does this needs documentation? yes You can merge this pull request into a Git repository by running: $ git pull https://github.com/cloverhearts/zeppelin ZEPPELIN-GET-PARAGRAPH-STATUS Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1930.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 #1930 commit 43c9ea5051745a013fd78d5a9497e960d42c6570 Author: cloverheartsDate: 2016-12-30T22:29:38Z extends z.status on RemoteWorks commit f0e9825e0e5867b750a8b386c0b82233b3915302 Author: cloverhearts Date: 2017-01-01T05:53:09Z implement check status logic in workflow commit 44fd762e1e9646deb0fdccfec7e3cabaa2042bfb Author: cloverhearts Date: 2017-01-21T15:10:10Z add status getter commit 7eac7572dcaf81f9b14a255f531fb7df7d465d7e Author: cloverhearts Date: 2017-01-21T20:08:42Z change method name commit 01614e6be21f7d08038db55b38a6da58744df505 Author: cloverhearts Date: 2017-01-21T20:55:01Z added test case commit cdbdb4ce51453239323e228847f7b6d87cbc2bb6 Author: cloverhearts Date: 2017-01-21T21:43:09Z remove â commit b9948df748281579c1998434915b0a9e29dd274d Author: cloverhearts Date: 2017-01-23T22:03:14Z change test case for println commit 7ecde8aeca227ff43c7ac2c5bb139dfedbeee4b6 Author: cloverhearts Date: 2017-01-23T22:57:53Z remove println in testcase commit a6b1719594c481c9236eea639b419526ab7918db Author: cloverhearts Date: 2017-01-24T02:40:24Z remove " commit 0482333c3394b878dec5cdb9f60322c6d19a2de5 Author: cloverhearts Date: 2017-01-24T07:13:05Z remove system.out --- 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 #1930: [ZEPPELIN-1886] implementation z.getZeppelinJob...
Github user cloverhearts closed the pull request at: https://github.com/apache/zeppelin/pull/1930 --- 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 #1946: [ZEPPELIN-921] Apply new mechanism to KnitR and...
GitHub user DrIgor reopened a pull request: https://github.com/apache/zeppelin/pull/1946 [ZEPPELIN-921] Apply new mechanism to KnitR and RRepl ### What is this PR for? Applies new registration mechanism for R interpreter ### What type of PR is it? [Refactoring] ### What is the Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-921 ### How should this be tested? Build zeppelin with R profile enabled and run several R snippets ### 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/DrIgor/zeppelin ZEPPELIN-921 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1946.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 #1946 commit a76a41d7dd538eb47522d6bf53e7aecdf65f3829 Author: Igor DrozdovDate: 2017-01-25T08:36:53Z New registration mechanism for R interpreter --- 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 #1946: [ZEPPELIN-921] Apply new mechanism to KnitR and...
Github user DrIgor closed the pull request at: https://github.com/apache/zeppelin/pull/1946 --- 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 #1663: ZEPPELIN-1692: Ability to access Spark jobs UI from th...
Github user Leemoonsoo commented on the issue: https://github.com/apache/zeppelin/pull/1663 @karuppayya could you try following change? ``` --- a/zeppelin-server/src/test/java/org/apache/zeppelin/AbstractZeppelinIT.java +++ b/zeppelin-server/src/test/java/org/apache/zeppelin/AbstractZeppelinIT.java @@ -71,7 +71,7 @@ abstract public class AbstractZeppelinIT { protected String getParagraphStatus(final int paragraphNo) { By locator = By.xpath(getParagraphXPath(paragraphNo) -+ "//div[contains(@class, 'control')]//span[2]"); ++ "//div[contains(@class, 'control')]/span[2]"); return driver.findElement(locator).getText(); } ``` In case of you'd like to run selenium test, please check https://github.com/apache/zeppelin/pull/1967 --- 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 #1967: [ZEPPELIN-2042] Document how to run selenium te...
GitHub user Leemoonsoo opened a pull request: https://github.com/apache/zeppelin/pull/1967 [ZEPPELIN-2042] Document how to run selenium test ### What is this PR for? This PR document how to run selenium test in development environment ### What type of PR is it? Documentation ### What is the Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-2042 ### 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/Leemoonsoo/zeppelin doc_run_selenium_test Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1967.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 #1967 commit e1312f3e20c5065f26e6c4044ec3d90c15fca160 Author: Lee moon sooDate: 2017-02-02T05:20:51Z Add 'Run Selenium test' section --- 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 #1929: [ZEPPELIN-1997] Added derbylog in .gitignore
Github user cloverhearts commented on the issue: https://github.com/apache/zeppelin/pull/1929 @jongyoul Fixed :) will not track all derby.log 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. ---
[jira] [Created] (ZEPPELIN-2042) Document how to run selenium test
Lee moon soo created ZEPPELIN-2042: -- Summary: Document how to run selenium test Key: ZEPPELIN-2042 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2042 Project: Zeppelin Issue Type: Task Reporter: Lee moon soo Assignee: Lee moon soo Priority: Minor Document how to run selenium test in development environment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] zeppelin issue #1960: [ZEPPELIN-2030] Select statement doesn't work in LivyS...
Github user minahlee commented on the issue: https://github.com/apache/zeppelin/pull/1960 Thank you for quick response! Let me merge 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 #1960: [ZEPPELIN-2030] Select statement doesn't work in LivyS...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/1960 Yes, the PR is ready. CI failure is not relevant. Please help include it in 0.7 --- 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 #1960: [ZEPPELIN-2030] Select statement doesn't work i...
Github user del680202 closed the pull request at: https://github.com/apache/zeppelin/pull/1960 --- 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 #1960: [ZEPPELIN-2030] Select statement doesn't work i...
GitHub user del680202 reopened a pull request: https://github.com/apache/zeppelin/pull/1960 [ZEPPELIN-2030] Select statement doesn't work in LivySparkSQLInterpreter ### What is this PR for? I try to execute sql query by ``%livy.sql``, I got a error as below ``` ERROR [2017-01-30 11:15:57,060] ({pool-2-thread-6} LivySparkSQLInterpreter.java[interpret]:143) - Exception in LivySparkSQLInterpreter while interpret java.lang.StringIndexOutOfBoundsException: String index out of range: 28 at java.lang.String.substring(String.java:1963) at org.apache.zeppelin.livy.LivySparkSQLInterpreter.parseSQLOutput(LivySparkSQLInterpreter.java:177) at org.apache.zeppelin.livy.LivySparkSQLInterpreter.interpret(LivySparkSQLInterpreter.java:128) at org.apache.zeppelin.interpreter.LazyOpenInterpreter.interpret(LazyOpenInterpreter.java:94) at org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:489) at org.apache.zeppelin.scheduler.Job.run(Job.java:175) at org.apache.zeppelin.scheduler.FIFOScheduler$1.run(FIFOScheduler.java:139) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) ``` I seem ``parseSQLOutput`` method try to filter out ``only showing top 1 row`` but it doesn't. Therefore, I fix this issue by modifying condition ### What type of PR is it? Bug Fix ### Todos * [x] - none ### What is the Jira issue? [ZEPPELIN-2030](https://issues.apache.org/jira/browse/ZEPPELIN-2030) ### How should this be tested? try to execute ``%livy.sql SELECT * FROM bank`` on tutorial ### Screenshots (if appropriate) Before ![2017-01-30 11 42 15](https://cloud.githubusercontent.com/assets/3747345/22412521/73c09e70-e6f2-11e6-9db4-d948201b7e9e.png) After ![2017-01-30 12 08 13](https://cloud.githubusercontent.com/assets/3747345/22412525/806e3696-e6f2-11e6-909e-6c4ffade4356.png) ### Questions: * Does the licenses files need update? * Is there breaking changes for older versions? * Does this needs documentation? You can merge this pull request into a Git repository by running: $ git pull https://github.com/del680202/zeppelin bug-2030 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1960.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 #1960 commit 8f499c49ecb4bca1077674de12f44c9b67e4e66e Author: Chin TzulinDate: 2017-01-30T04:40:21Z [ZEPPELIN-2030] Select statement doesn't work in LivySparkSQLInterpreter commit d6811006efe4d36f9163a2d9d3a703d241d948c5 Author: Chin Tzulin Date: 2017-01-31T06:26:20Z Add test case into LivySQLInterpreterTest.java commit 86ebc82ea9b5b70d7d9eaefc538d38aeaeae5029 Author: Chin Tzulin Date: 2017-01-31T08:34:38Z Fix test problem --- 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 #1960: [ZEPPELIN-2030] Select statement doesn't work in LivyS...
Github user minahlee commented on the issue: https://github.com/apache/zeppelin/pull/1960 @zjffdu @del680202 Is this ready? :) --- 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 #1952: [ZEPPELIN-753] TableData abstraction
Github user 1ambda commented on the issue: https://github.com/apache/zeppelin/pull/1952 @Leemoonsoo Nice to have abstracted table structure inside zeppelin. It enable us many things even i just glanced at. I will take look deeply and comment soon. --- 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 #1935: [gh-pages][ZEPPELIN-1973] List all available Helium pa...
Github user 1ambda commented on the issue: https://github.com/apache/zeppelin/pull/1935 @AhyoungRyu Thanks for great contribution. This PR increase the number of helium package users significantly. I would like to comment about the design of `helium.json`. Basically, It's concise and well designed. - It would be great if helium package has `version` field considering local package and `latest` - If once people start to develop packages, there must be operational things like user complains. For example, "I published package to npm, but it's not collected by helium for last 2 days. What's the problem?" So, it's good for each package to have some information for debug and ops like `createdAt`, `heliumFormatVersion`. --- 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 #1965: [ZEPPELIN-2036] add documentation on separating worksp...
Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/1965 CI failure is irrelevant with this docs change. Merge into branch-0.7 and master if there are no more 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 issue #1886: [ZEPPELIN-1876] improved comptetion with schema/table/...
Github user Leemoonsoo commented on the issue: https://github.com/apache/zeppelin/pull/1886 CI failure is not related to this change. LGTM and merge to master if no further 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 pull request #1940: [ZEPPELIN-2008] Introduce Spell
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/1940 --- 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 #1663: ZEPPELIN-1692: Ability to access Spark jobs UI from th...
Github user Leemoonsoo commented on the issue: https://github.com/apache/zeppelin/pull/1663 @karuppayya sure, let me take a look selenium test in this branch. --- 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 #1965: [ZEPPELIN-2036] add documentation on separating worksp...
Github user epahomov commented on the issue: https://github.com/apache/zeppelin/pull/1965 Love it. Everything very clear --- 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 #1961: [ZEPPELIN-1934] maven-assembly-plugin fails make-assem...
Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/1961 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 #1945: [ZEPPELIN-2003] Remove PostgresqlInterpreter
Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/1945 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 #1961: [ZEPPELIN-1934] maven-assembly-plugin fails make-assem...
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/1961 Thanks. 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 #1929: [ZEPPELIN-1997] Added derbylog in .gitignore
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/1929 Is there any update? :-) --- 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 #1961: [ZEPPELIN-1934] maven-assembly-plugin fails make-assem...
Github user DmytroShkvyra commented on the issue: https://github.com/apache/zeppelin/pull/1961 @jongyoul Yes, you can do this like described there https://issues.apache.org/jira/browse/MASSEMBLY-781?focusedCommentId=14640499=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14640499 --- 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 #1911: [ZEPPELIN-1972] Preserve context classloader
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/1911 Is there any update on 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 #1945: [ZEPPELIN-2003] Remove PostgresqlInterpreter
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/1945 @AhyoungRyu Please check the change. --- 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 #1961: [ZEPPELIN-1934] maven-assembly-plugin fails make-assem...
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/1961 Cool. Can you tell me how to test it by myself? --- 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 #1946: [ZEPPELIN-921] Apply new mechanism to KnitR and RRepl
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/1946 I merged #1937. Can you rebase it onto master and make CI green? --- 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 #1937: Search for interpreter-settings in several jars...
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/1937 --- 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-2041) Introduce a new abstraction layer for managing and launching interpreters
Jongyoul Lee created ZEPPELIN-2041: -- Summary: Introduce a new abstraction layer for managing and launching interpreters Key: ZEPPELIN-2041 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2041 Project: Zeppelin Issue Type: Sub-task Components: zeppelin-server Reporter: Jongyoul Lee Assignee: Jongyoul Lee -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ZEPPELIN-2040) ClusterManager to support launching interpreter in a cluster
Jongyoul Lee created ZEPPELIN-2040: -- Summary: ClusterManager to support launching interpreter in a cluster Key: ZEPPELIN-2040 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2040 Project: Zeppelin Issue Type: New Feature Components: zeppelin-interpreter, zeppelin-server Reporter: Jongyoul Lee Assignee: Jongyoul Lee Zeppelin's interpreter launches in a same machine of Zeppelin server only. This umbrella issue covers to support launching interpreters in remote machine including Yarn, Mesos and AWS. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] zeppelin issue #1937: Search for interpreter-settings in several jars in fol...
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/1937 I'll merge this PR and will make a new PR to handle with Jeff's worries which are reasonable and should be maintained. --- 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 #1944: [HOTFIX][MINOR] Change the scope of httpclient to runt...
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/1944 If you remove that dependency, I think you cannot compile zeppelin-server 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 issue #1957: Branch 0.6 Groovy Interpreter
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/1957 If you contribute code based on master, we will review and merge it into master and branch-0.7 if necessary. --- 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 #1804: [ZEPPELIN-1578] notes list in customizing zeppe...
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/1804 --- 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 #1966: [ZEPPELIN-2039] Upgrade safe_yaml version in gh-page
Github user soralee commented on the issue: https://github.com/apache/zeppelin/pull/1966 I realized my branch is wrong. I closed this pr. Sorry for confusing :disappointed_relieved: --- 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 #1966: [ZEPPELIN-2039] Upgrade safe_yaml version in gh...
GitHub user soralee opened a pull request: https://github.com/apache/zeppelin/pull/1966 [ZEPPELIN-2039] Upgrade safe_yaml version in gh-page ### What is this PR for? This PR will fix some problem which I faced when starting the gh-page server like the following code. ``` $ bundle exec jekyll serve --watch /var/lib/gems/2.3.0/gems/commander-4.1.5/lib/commander/user_interaction.rb:328: warning: constant ::TimeoutError is deprecated /var/lib/gems/2.3.0/gems/commander-4.1.5/lib/commander/runner.rb:365:in `block in require_program': program version required (Commander::Runner::CommandError) from /var/lib/gems/2.3.0/gems/commander-4.1.5/lib/commander/runner.rb:364:in `each' from /var/lib/gems/2.3.0/gems/commander-4.1.5/lib/commander/runner.rb:364:in `require_program' from /var/lib/gems/2.3.0/gems/commander-4.1.5/lib/commander/runner.rb:52:in `run!' from /var/lib/gems/2.3.0/gems/commander-4.1.5/lib/commander/delegates.rb:7:in `run!' from /var/lib/gems/2.3.0/gems/commander-4.1.5/lib/commander/import.rb:10:in `block in ' /var/lib/gems/2.3.0/gems/safe_yaml-0.9.7/lib/safe_yaml/syck_node_monkeypatch.rb:42:in `': uninitialized constant Syck (NameError) from /var/lib/gems/2.3.0/gems/safe_yaml-0.9.7/lib/safe_yaml.rb:200:in `require' from /var/lib/gems/2.3.0/gems/safe_yaml-0.9.7/lib/safe_yaml.rb:200:in `' from /var/lib/gems/2.3.0/gems/safe_yaml-0.9.7/lib/safe_yaml.rb:132:in `' from /var/lib/gems/2.3.0/gems/jekyll-1.3.0/lib/jekyll.rb:21:in `require' from /var/lib/gems/2.3.0/gems/jekyll-1.3.0/lib/jekyll.rb:21:in `' from /var/lib/gems/2.3.0/gems/jekyll-1.3.0/bin/jekyll:7:in `require' from /var/lib/gems/2.3.0/gems/jekyll-1.3.0/bin/jekyll:7:in `' from /usr/local/bin/jekyll:23:in `load' from /usr/local/bin/jekyll:23:in `' ``` This issue is similar with [ZEPPELIN-813](https://issues.apache.org/jira/browse/ZEPPELIN-813) and it was solved by [PR #1167](https://github.com/apache/zeppelin/pull/1167). ### What type of PR is it? [Bug Fix | Improvement | Documentation(`README.md`)] ### What is the Jira issue? [ZEPPELIN-2039](https://issues.apache.org/jira/browse/ZEPPELIN-2039) ### How should this be tested? **Please read `README.md` if you didn't installed dependencies ever.** 1. If you already installed dependencies before, you need ``` $ bundle update safe_yaml ``` 2. Check what version of safe_yaml is installed and then run this command ``` $ bundle exec jekyll serve --watch ``` ### 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/soralee/zeppelin ZEPPELIN-2039_gh Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1966.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 #1966 commit 5581874e1f716fb86c29c5155af2bb4c800b816d Author: soraleeDate: 2017-02-01T10:11:17Z update dependency commit 7311a28750de79314001f971c097bb0834e9cdd4 Author: soralee Date: 2017-02-01T10:22:42Z update dependency and README document --- 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-2039) Update gh-site dependencies
Sora Lee created ZEPPELIN-2039: -- Summary: Update gh-site dependencies Key: ZEPPELIN-2039 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2039 Project: Zeppelin Issue Type: Improvement Reporter: Sora Lee Assignee: Sora Lee Priority: Minor I faced this problem when starting the gh-site server. This issue is similar with [ZEPPELIN-813|https://issues.apache.org/jira/browse/ZEPPELIN-813]. {code} $ bundle exec jekyll serve --watch /var/lib/gems/2.3.0/gems/commander-4.1.5/lib/commander/user_interaction.rb:328: warning: constant ::TimeoutError is deprecated /var/lib/gems/2.3.0/gems/commander-4.1.5/lib/commander/runner.rb:365:in `block in require_program': program version required (Commander::Runner::CommandError) from /var/lib/gems/2.3.0/gems/commander-4.1.5/lib/commander/runner.rb:364:in `each' from /var/lib/gems/2.3.0/gems/commander-4.1.5/lib/commander/runner.rb:364:in `require_program' from /var/lib/gems/2.3.0/gems/commander-4.1.5/lib/commander/runner.rb:52:in `run!' from /var/lib/gems/2.3.0/gems/commander-4.1.5/lib/commander/delegates.rb:7:in `run!' from /var/lib/gems/2.3.0/gems/commander-4.1.5/lib/commander/import.rb:10:in `block in ' /var/lib/gems/2.3.0/gems/safe_yaml-0.9.7/lib/safe_yaml/syck_node_monkeypatch.rb:42:in `': uninitialized constant Syck (NameError) from /var/lib/gems/2.3.0/gems/safe_yaml-0.9.7/lib/safe_yaml.rb:200:in `require' from /var/lib/gems/2.3.0/gems/safe_yaml-0.9.7/lib/safe_yaml.rb:200:in `' from /var/lib/gems/2.3.0/gems/safe_yaml-0.9.7/lib/safe_yaml.rb:132:in `' from /var/lib/gems/2.3.0/gems/jekyll-1.3.0/lib/jekyll.rb:21:in `require' from /var/lib/gems/2.3.0/gems/jekyll-1.3.0/lib/jekyll.rb:21:in `' from /var/lib/gems/2.3.0/gems/jekyll-1.3.0/bin/jekyll:7:in `require' from /var/lib/gems/2.3.0/gems/jekyll-1.3.0/bin/jekyll:7:in `' from /usr/local/bin/jekyll:23:in `load' from /usr/local/bin/jekyll:23:in `' {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] zeppelin issue #1940: [ZEPPELIN-2008] Introduce Spell
Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/1940 From now, `SPELL` type pkg info fetched from [Helium registry](https://s3.amazonaws.com/helium-package/helium.json) is also shown in GUI :) https://cloud.githubusercontent.com/assets/10060731/22501386/e56b8336-e8ab-11e6-94ee-e0bed54fe2a1.png;> --- 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 #1963: [ZEPPELIN-2033] Handle focus/blur of paragraph with hi...
Github user minahlee commented on the issue: https://github.com/apache/zeppelin/pull/1963 Merge into branch-0.7 and master --- 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 #1963: [ZEPPELIN-2033] Handle focus/blur of paragraph with hi...
Github user Leemoonsoo commented on the issue: https://github.com/apache/zeppelin/pull/1963 Tested and 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 #1965: [ZEPPELIN-2036] add documentation on separating worksp...
Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/1965 Nice description! \cc @epahomov to help review 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 #1964: [HOTFIX][branch-0.7] Show only VISUALIZATION & APPLICA...
Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/1964 Just realized that #1936 is not merged into `branch-0.7`. So don't need this patch for` branch-0.7`. Sorry for any confusion. --- 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 #1964: [HOTFIX][branch-0.7] Show only VISUALIZATION & ...
Github user AhyoungRyu closed the pull request at: https://github.com/apache/zeppelin/pull/1964 --- 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 #1965: [ZEPPELIN-2036] add documentation on separating...
GitHub user khalidhuseynov opened a pull request: https://github.com/apache/zeppelin/pull/1965 [ZEPPELIN-2036] add documentation on separating workspaces (public/private) ### What is this PR for? This is to add more description in documentation about notebook workspaces. Also some details from user mailing list [here](https://lists.apache.org/thread.html/d94276521942c90cca1325514ea93b737a517679dd0f6f7eb287492a@%3Cusers.zeppelin.apache.org%3E) ### What type of PR is it? Improvement | Documentation ### Todos * [x] - add desc ### What is the Jira issue? [ZEPPELIN-2036](https://issues.apache.org/jira/browse/ZEPPELIN-2036) ### How should this be tested? green CI/ if description clear ### 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/khalidhuseynov/incubator-zeppelin docs/private-workspace Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1965.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 #1965 commit 8703770b420185ab9de51e2b3346223e51c6aa4b Author: Khalid HuseynovDate: 2017-02-01T08:22:17Z add description on separating workspaces commit cec8bbd2c9fa5d5fd5b8d2213c185f2022cfda88 Author: Khalid Huseynov Date: 2017-02-01T08:31:41Z add public vs. private commit c85ee6ec236e932aa1a5579a543ba0b078e7a533 Author: Khalid Huseynov Date: 2017-02-01T08:33:55Z rewording --- 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 #1964: [HOTFIX][branch-0.7] Show only VISUALIZATION & APPLICA...
Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/1964 @minahlee @Leemoonsoo If you don't mind, can you help review 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 pull request #1964: [HOTFIX][branch-0.7] Show only VISUALIZATION & ...
GitHub user AhyoungRyu opened a pull request: https://github.com/apache/zeppelin/pull/1964 [HOTFIX][branch-0.7] Show only VISUALIZATION & APPLICATION type in Helium GUI ### What is this PR for? Currently Helium online package registry file([helium.json](https://s3.amazonaws.com/helium-package/helium.json)) contains both `SPELL` and `VISUALIZATION` pkgs' info. But Zeppelin-0.7 can't include #1940 I guess. Then Zeppelin must show only available package types (`VISUALIZATION` and `APPLICATION`) in 0.7 version. So I made this PR based on `branch-0.7`. ### What type of PR is it? Hot Fix ### What is the Jira issue? [ZEPPELIN-2038](https://issues.apache.org/jira/browse/ZEPPELIN-2038) ### How should this be tested? 1. Run Zeppelin web dev mode under `zeppelin-web` and go to [http://localhost:9000/#/helium](http://localhost:9000/#/helium). ``` $ yarn run dev ``` 2. Check whether `SPELL` type package appears or not. Only `VISUALIZATION`(comes from Helium online registry [https://s3.amazonaws.com/helium-package/helium.json](https://s3.amazonaws.com/helium-package/helium.json)) or `APPLICATION`(if you put `zeppelin-example-clock.json` under `ZEPPELIN_HOME/helium/` dir) should show up with this patch. ### Screenshots (if appropriate) **Before** ![screen shot 2017-02-01 at 5 01 06 pm](https://cloud.githubusercontent.com/assets/10060731/22499100/20529306-e8a0-11e6-9872-7e26d9dbac3f.png) **After** ![screen shot 2017-02-01 at 5 01 35 pm](https://cloud.githubusercontent.com/assets/10060731/22499105/23f3ea6e-e8a0-11e6-81b0-810c61885337.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/AhyoungRyu/zeppelin branch-0.7/ZEPPELIN-2038 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1964.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 #1964 commit 736eb553d08f7c818c27074ee7debe766bf36b5d Author: AhyoungRyuDate: 2017-02-01T07:47:21Z Show only VISUALIZATION & APPLICATION type in Helium GUI --- 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. ---