[GitHub] [zeppelin] zjffdu opened a new pull request #3829: [ZEPPELIN-4927]. Use the original order of interpreter properties from backend
zjffdu opened a new pull request #3829: URL: https://github.com/apache/zeppelin/pull/3829 ### What is this PR for? The interpreter properties returned from backend is already ordered as the ordering of `interpreter-setting.json`, frontend should not order it again by alphabeta. We already fix it in the interpreter listing page, but didn't fix it in the creating interpreter page. This PR fix that. ### What type of PR is it? [ Improvement ] ### Todos * [ ] - Task ### What is the Jira issue? * https://issues.apache.org/jira/browse/ZEPPELIN-4927 ### How should this be tested? * Manually tested ### Screenshots (if appropriate) Before  After  ### Questions: * Does the licenses files need update? No * Is there breaking changes for older versions? No * Does this needs documentation? No This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (ZEPPELIN-4927) Use the original order of interpreter properties from backend
Jeff Zhang created ZEPPELIN-4927: Summary: Use the original order of interpreter properties from backend Key: ZEPPELIN-4927 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4927 Project: Zeppelin Issue Type: Improvement Components: zeppelin-web Affects Versions: 0.9.0 Reporter: Jeff Zhang interpreter properties from backend is already ordered, we should not sort it again in frontend. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [zeppelin] zjffdu commented on pull request #3827: [ZEPPELIN-4924]. Add params to note run rest api
zjffdu commented on pull request #3827: URL: https://github.com/apache/zeppelin/pull/3827#issuecomment-650872260 Thanks @jongyoul for helping merge it This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [zeppelin] zjffdu closed pull request #3805: [ZEPPELIN-4884]. Support all sql of flink 1.11
zjffdu closed pull request #3805: URL: https://github.com/apache/zeppelin/pull/3805 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [zeppelin] zjffdu commented on pull request #3827: [ZEPPELIN-4924]. Add params to note run rest api
zjffdu commented on pull request #3827: URL: https://github.com/apache/zeppelin/pull/3827#issuecomment-650865959 Yes，nothing changed @jongyoul This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [zeppelin] jongyoul commented on pull request #3827: [ZEPPELIN-4924]. Add params to note run rest api
jongyoul commented on pull request #3827: URL: https://github.com/apache/zeppelin/pull/3827#issuecomment-650860979 Hello, BTW, I've used Github's merge function because I remembered it worked properly but are we still using our python script to merge some PRs? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [zeppelin] jongyoul merged pull request #3827: [ZEPPELIN-4924]. Add params to note run rest api
jongyoul merged pull request #3827: URL: https://github.com/apache/zeppelin/pull/3827 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [Announce] New Zeppelin Committer: Philipp Dallig
Congrats and welcome! From: Xun Liu Sent: Saturday, June 27, 2020 8:58:34 AM To: dev Cc: users ; philipp.dal...@gmail.com Subject: Re: [Announce] New Zeppelin Committer: Philipp Dallig That's great news! Welcome aboard Philipp! :-) On Sat, Jun 27, 2020 at 8:43 AM Yadong Xie mailto:vthink...@gmail.com>> wrote: welcome! On Saturday, June 27, 2020, Alex Ott mailto:alex...@gmail.com>> wrote: > That's great news! Welcome aboard Philipp! > > On Fri, Jun 26, 2020 at 8:23 AM Jeff Zhang > mailto:zjf...@gmail.com>> wrote: > > > > > The Project Management Committee (PMC) for Apache Zeppelin > > has invited Philipp Dallig to become a committer and we are very pleased > > to announce that he has accepted. > > > > We greatly appreciate all of Philipp Dallig's hard work and generous > > contributions to the project. We look forward to continued involvement in > > the project. > > > > Congratulations & Welcome aboard Philipp Dallig ! > > > > > > -- > > Best Regards > > > > Jeff Zhang > > > > > -- > With best wishes,Alex Ott > http://alexott.net/ > Twitter: alexott_en (English), alexott (Russian) >
[GitHub] [zeppelin] morningmemo opened a new pull request #3828: [ZEPPELIN-4926] Fix null pointer exception when the repository's url …
morningmemo opened a new pull request #3828: URL: https://github.com/apache/zeppelin/pull/3828 …protocol is http ### What is this PR for? This PR is to fix null pointer exception when the interpreter repository's url protocol is http. ### What type of PR is it? [ Bug Fix ] ### Todos * [ ] - Task ### What is the Jira issue? * https://issues.apache.org/jira/browse/ZEPPELIN-4926 ### How should this be tested? * Unit test is added. ### Screenshots (if appropriate) ### Questions: * Does the licenses files need update? NO * Is there breaking changes for older versions? NO * Does this needs documentation? NO ### What is this PR for? A few sentences describing the overall goals of the pull request's commits. First time? Check out the contributing guide - https://zeppelin.apache.org/contribution/contributions.html ### What type of PR is it? [Bug Fix | Improvement | Feature | Documentation | Hot Fix | Refactoring] ### Todos * [ ] - Task ### What is the Jira issue? * Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/ * Put link here, and add [ZEPPELIN-*Jira number*] in PR title, eg. [ZEPPELIN-533] ### How should this be tested? * First time? Setup Travis CI as described on https://zeppelin.apache.org/contribution/contributions.html#continuous-integration * Strongly recommended: add automated unit tests for any new or changed behavior * Outline any manual steps to test the PR here. ### Screenshots (if appropriate) ### Questions: * Does the licenses files need update? * Is there breaking changes for older versions? * Does this needs documentation? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (ZEPPELIN-4926) Fix null pointer exception when the interpreter repository's url protocol is http
lee jong hyun created ZEPPELIN-4926: --- Summary: Fix null pointer exception when the interpreter repository's url protocol is http Key: ZEPPELIN-4926 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4926 Project: Zeppelin Issue Type: Bug Components: Interpreters Affects Versions: 0.8.2 Reporter: lee jong hyun Fix For: 0.9.0 Correct the phenomenon that there couldn't access when the url protocol of repository is http. If the repository's url protocol is http, it tries to access the repository through LightweightHttpWagon. Inside the LightweightHttpWagon, the authenticator is referenced. At this time, the authenticator is null referenced, resulting in a null pointer exception. Set the LightweightHttpWagonAuthenticator in the part that creates LightweightHttpWagon to solve the problem. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ZEPPELIN-4925) Only display note job info for owner
Jeff Zhang created ZEPPELIN-4925: Summary: Only display note job info for owner Key: ZEPPELIN-4925 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4925 Project: Zeppelin Issue Type: Improvement Components: zeppelin-server Affects Versions: 0.9.0 Reporter: Jeff Zhang For now, all the note job info are displayed, we should only display the display note job info for the owner -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [zeppelin] asfgit closed pull request #3823: [ZEPPELIN-4868]. Display hive job execution info when running hive sql in jdbc interpreter
asfgit closed pull request #3823: URL: https://github.com/apache/zeppelin/pull/3823 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [zeppelin] zjffdu opened a new pull request #3827: [ZEPPELIN-4924]. Add params to note run rest api
zjffdu opened a new pull request #3827: URL: https://github.com/apache/zeppelin/pull/3827 ### What is this PR for? This PR add params to note run rest api, so that user can specify params for each note run. E.g. user can specify the date to run regular ETL job. ### What type of PR is it? [Feature ] ### Todos * [ ] - Task ### What is the Jira issue? * https://issues.apache.org/jira/browse/ZEPPELIN-4924 ### How should this be tested? * Unit test is added in `NotebookRestApiTest` ### Screenshots (if appropriate) ### Questions: * Does the licenses files need update? No * Is there breaking changes for older versions? No * Does this needs documentation? NO This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [zeppelin] zjffdu opened a new pull request #3826: [ZEPPELIN-4922]. Use original flink web url for job progress polling
zjffdu opened a new pull request #3826: URL: https://github.com/apache/zeppelin/pull/3826 ### What is this PR for? For flink job progress polling, we should still use the original web url. Otherwise the replaced flink job url won't work. ### What type of PR is it? [Bug Fix] ### Todos * [ ] - Task ### What is the Jira issue? * https://issues.apache.org/jira/browse/ZEPPELIN-4922 ### How should this be tested? * CI pass ### Screenshots (if appropriate) ### Questions: * Does the licenses files need update? No * Is there breaking changes for older versions? No * Does this needs documentation? No This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (ZEPPELIN-4924) Add params to note run rest api
Jeff Zhang created ZEPPELIN-4924: Summary: Add params to note run rest api Key: ZEPPELIN-4924 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4924 Project: Zeppelin Issue Type: New Feature Components: zeppelin-server Affects Versions: 0.9.0 Reporter: Jeff Zhang -- This message was sent by Atlassian Jira (v8.3.4#803005)
