[GitHub] [zeppelin] zjffdu opened a new pull request #3798: [ZEPPELIN-4837]. Add property to only check some packages for udf finding

2020-06-10 Thread GitBox
zjffdu opened a new pull request #3798: URL: https://github.com/apache/zeppelin/pull/3798 ### What is this PR for? Add property `flink.udf.jars.packages` to specify the packages that would be searched for udf, otherwise all the classes will be check, which might be very time consumi

[jira] [Created] (ZEPPELIN-4881) Incorrect date display on version control

2020-06-10 Thread jinxin (Jira)
jinxin created ZEPPELIN-4881: Summary: Incorrect date display on version control Key: ZEPPELIN-4881 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4881 Project: Zeppelin Issue Type: Bug

[GitHub] [zeppelin] zjffdu opened a new pull request #3797: [ZEPPELIN-4851]. Add property to flink interpreter to allow replace the yarn address

2020-06-10 Thread GitBox
zjffdu opened a new pull request #3797: URL: https://github.com/apache/zeppelin/pull/3797 ### What is this PR for? Trivial PR which add property `flink.webui.yarn.yarnAddress` that allow user to replace the yarn address. This is for some cases that cloud vender would map the int

[GitHub] [zeppelin] zjffdu opened a new pull request #3796: [ZEPPELIN-4877]. text between 2 sql comment is mistaken as comment

2020-06-10 Thread GitBox
zjffdu opened a new pull request #3796: URL: https://github.com/apache/zeppelin/pull/3796 ### What is this PR for? This PR fix the bug in Splitter that text between 2 sql comment is mistaken as comment. Unit test is added in this PR as well. Besides that, this PR also remove the com

[jira] [Created] (ZEPPELIN-4880) spark on kubernetes is Exception in thread "main" java.io.IOException: failure to login

2020-06-10 Thread xianchang.yue (Jira)
xianchang.yue created ZEPPELIN-4880: --- Summary: spark on kubernetes is Exception in thread "main" java.io.IOException: failure to login Key: ZEPPELIN-4880 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4880

[jira] [Created] (ZEPPELIN-4879) Error when using `useAuth` as true in the initiation of Gateway server

2020-06-10 Thread Loghi Perinpanayagam (Jira)
Loghi Perinpanayagam created ZEPPELIN-4879: -- Summary: Error when using `useAuth` as true in the initiation of Gateway server Key: ZEPPELIN-4879 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4879

[GitHub] [zeppelin] zjffdu opened a new pull request #3795: [ZEPPELIN-4878]. Unable to run flink 1.10.1 in yarn mode due to FLINK-17788

2020-06-10 Thread GitBox
zjffdu opened a new pull request #3795: URL: https://github.com/apache/zeppelin/pull/3795 ### What is this PR for? Flink interpreter doesn't work with flink 1.10.1 in yarn mode due to FLINK-17788, this PR fix it in zeppelin side. Because in scala shell, flink only support yarn sessi

[jira] [Created] (ZEPPELIN-4878) Unable to run flink 1.10.1 in yarn mode due to FLINK-17788

2020-06-10 Thread Jeff Zhang (Jira)
Jeff Zhang created ZEPPELIN-4878: Summary: Unable to run flink 1.10.1 in yarn mode due to FLINK-17788 Key: ZEPPELIN-4878 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4878 Project: Zeppelin

[GitHub] [zeppelin] zjffdu opened a new pull request #3794: [ZEPPELIN-4873]. Display rich duration info for insert into flink job

2020-06-10 Thread GitBox
zjffdu opened a new pull request #3794: URL: https://github.com/apache/zeppelin/pull/3794 ### What is this PR for? Trivial PR which display rich duration info instead of just x seconds. See screenshot below. ### What type of PR is it? [ Improvement ] ### Todos

Re: Best practices for unit/integration test

2020-06-10 Thread Jeff Zhang
Agree, I also meet such issues before, we may also need to create utility class for that. e.g. assertSuccess(interpreterResult) Alex Ott 于2020年6月10日周三 下午8:17写道: > Hi all > > I was debugging multiple issues over the last day, and I've noticed that > it's very hard to debug asserts like this: >

Best practices for unit/integration test

2020-06-10 Thread Alex Ott
Hi all I was debugging multiple issues over the last day, and I've noticed that it's very hard to debug asserts like this: assertEquals(InterpreterResult.Code.SUCCESS, interpreterResult.code()); because it doesn't say what is the reason for it, just a difference. It would be much simpler to debu

[GitHub] [zeppelin] asfgit closed pull request #3792: [ZEPPELIN-4865]. Allow specify jobName as paragraph local properties

2020-06-10 Thread GitBox
asfgit closed pull request #3792: URL: https://github.com/apache/zeppelin/pull/3792 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

[jira] [Created] (ZEPPELIN-4877) Cannot submit paragraph When there is a comment in the paragraph

2020-06-10 Thread jinxin (Jira)
jinxin created ZEPPELIN-4877: Summary: Cannot submit paragraph When there is a comment in the paragraph Key: ZEPPELIN-4877 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4877 Project: Zeppelin

[GitHub] [zeppelin] asfgit closed pull request #3793: [ZEPPELIN-4864] Cleanup Travis-CI config

2020-06-10 Thread GitBox
asfgit closed pull request #3793: URL: https://github.com/apache/zeppelin/pull/3793 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