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
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 o
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
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: Impro
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
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
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:4
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 t
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?
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 messa
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
jongyoul commented on pull request #3827:
URL: https://github.com/apache/zeppelin/pull/3827#issuecomment-650871197
@zjffdu Got it. I'll follow it then, I've committed this PR to `branch-0.9`
as well by cherry-picking it.
Thi
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 th
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
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 a
15 matches
Mail list logo