Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1995
@1ambda Sorry for my late response. Tested and could see what you
described. Looks good ð
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2025
@felixcheung @prabhjyotsingh Please help 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
GitHub user jongyoul opened a pull request:
https://github.com/apache/zeppelin/pull/2028
[MINOR] Supported old note format in case of not having name of note
### What is this PR for?
Supporting old format of note which doesn't have name inside. Long time
ago, when creating note
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/2021
Ran this couple of time on my local, works a expected.
---
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
Narasimma varman created ZEPPELIN-2126:
--
Summary: How to create zeppelin notebook like kibana,Hue dashboard
with more effective widgets
Key: ZEPPELIN-2126
URL:
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1995
Thanks @AhyoungRyu. This definitely help to write and check test easily.
---
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
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2021
LGTM
Waiting for CI and
merging if no more comment
---
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
20170216-161237_625814895 is
finished
INFO [2017-02-16 17:29:05,932] ({pool-2-thread-61}
SchedulerFactory.java[jobFinished]:137) - Job
paragraph_1487232757101_-941163964 finished by scheduler
org.apache.zeppelin.interpreter.remote.RemoteInterpretershared_session1298915037
INFO [2017-02-16 17:29
I think it's good idea. :-)
On Thu, Feb 16, 2017 at 7:54 PM, Jeff Zhang wrote:
> Great, can't wait to try this.
>
>
>
> moon soo Lee 于2017年2月16日周四 下午6:35写道:
>
> > Hi Apache Zeppelin contributors!
> >
> > Recently, it's not very difficult to see pullrequest is
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2026
Looks nice ð
---
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,
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2024
In case that you encounter conflicts, you have to rebase your changes onto
the base branch you start working on. AFAIK, ASF doesn't allow write permission
through Github.
---
If your project
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
Incompatible with https://github.com/apache/zeppelin/pull/2016
---
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
Github user DmytroShkvyra closed the pull request at:
https://github.com/apache/zeppelin/pull/2002
---
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
Github user DmytroShkvyra closed the pull request at:
https://github.com/apache/zeppelin/pull/2024
---
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2024
I'm not sure who think what now, I just let you know the history. If you
really want to move JDK8, open discussion and reach a "consensus" with
community first. I think moving to JDK8 doesn't
Lee moon soo created ZEPPELIN-2123:
--
Summary: Scale-out CI capacity by leveraging individual
contributor's travis account
Key: ZEPPELIN-2123
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2123
GitHub user Leemoonsoo opened a pull request:
https://github.com/apache/zeppelin/pull/2026
[ZEPPELIN-2123] Travis build status check script
### What is this PR for?
This script is designed to check contributors travis CI build state when
pullrequest is created.
GitHub user Remilito reopened a pull request:
https://github.com/apache/zeppelin/pull/2023
[ZEPPELIN-2114]: adding reload endpoint + fixing test
### What is this PR for?
Adding endpoint in NotebookRepoRestApi to trigger reload and broadcast of
the note list.
Sending a GET
Great, can't wait to try this.
moon soo Lee 于2017年2月16日周四 下午6:35写道:
> Hi Apache Zeppelin contributors!
>
> Recently, it's not very difficult to see pullrequest is waiting more than
> 10 hours to get travis-ci build slot.
>
> It's because of all ASF project shares the same
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2024
And concerning your contribution, we discussed it before and concluded it's
too early to move JDK8. If you think it's right time to move on, please start
discussion again in dev@ and user@
---
Github user Remilito closed the pull request at:
https://github.com/apache/zeppelin/pull/2023
---
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
Hi Apache Zeppelin contributors!
Recently, it's not very difficult to see pullrequest is waiting more than
10 hours to get travis-ci build slot.
It's because of all ASF project shares the same travis account and the
account's capability is limited. Although ASF assigned 5 concurrent build
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2024
@jongyoul Should I close ZEPPELIN-411 as "wont fix"?
---
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2024
You don't have to do it because we eventually will move to further JDK
version
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2024
@jongyoul May be make sense just create PR only for try moving to JDK8 and
test this with Travis? Anyway nobody will not merge it to zeppelin without
approve.
---
If your project is set
Frank Rosner created ZEPPELIN-2124:
--
Summary: Missing dependencies array in interpreter.json after
upgrade from 0.6.2 to 0.7.0
Key: ZEPPELIN-2124
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2124
Hoon Park created ZEPPELIN-2125:
---
Summary: Download helium.json when really needed
Key: ZEPPELIN-2125
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2125
Project: Zeppelin
Issue Type:
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2015
I will review this 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
GitHub user astroshim reopened a pull request:
https://github.com/apache/zeppelin/pull/1985
[ZEPPELIN-2075] Can't stop infinite `while` statement in pyspark
Interpreter.
### What is this PR for?
If following code runs with Pyspark Interpreter, there is no way to cancel
except
GitHub user DmytroShkvyra opened a pull request:
https://github.com/apache/zeppelin/pull/2027
[ZEPPELIN-791] Build infra: move all RAT to root pom.xml
### What is this PR for?
Is is better have a single place where we manage project-wise RAT
exclusions for a contributions under
30 matches
Mail list logo