Great job zeppelin communities!!
and Thank you mina~
2017년 4월 1일 (토) 오전 11:01, Mina Lee 님이 작성:
> The Apache Zeppelin community is pleased to announce the availability of
> the 0.7.1 release.
>
> Zeppelin is a collaborative data analytics and visualization tool for
> distributed, general-purpose d
Github user benoyantony commented on the issue:
https://github.com/apache/zeppelin/pull/2201
It should not break anything as the property name remains same as before.
The documentation had a typo in it. It was missing 'sql' in it.
If it's confusing, I can do it as a separat
The Apache Zeppelin community is pleased to announce the availability of
the 0.7.1 release.
Zeppelin is a collaborative data analytics and visualization tool for
distributed, general-purpose data processing system such as Apache Spark,
Apache Flink, etc.
The community put significant effort into
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2209
---
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 e
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2203
Great improvement! LGTM
\cc @cloverhearts @astroshim
---
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 no
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2113
---
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 e
Github user prabhjyotsingh closed the pull request at:
https://github.com/apache/zeppelin/pull/2034
---
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 feat
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2209
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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2199
@markito I mean, this PR not the JIRA ticket :)
---
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 fe
Github user markito commented on the issue:
https://github.com/apache/zeppelin/pull/2199
@1ambda can you please confirm if the reopened JIRA triggered Jenkins
properly ? Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
GitHub user 1ambda opened a pull request:
https://github.com/apache/zeppelin/pull/2210
[ZEPPELIN-2088] Evaluate helium bundle one by one
### What is this PR for?
Evaluate helium bundle one by one. Because
- Bundling them in one file is not good idea because the whol
Github user minahlee commented on the issue:
https://github.com/apache/zeppelin/pull/2209
Merge if there is no more discussion for new release publish
---
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 n
The vote passes with 6 binding +1 votes, 9 non-binding +1 votes, and no +0
or -1 votes. Thanks for everyone who verified rc and voted.
+1:
Jeff Zhang
DuyHai Doan
Hyung Sung Shim
Mina Lee*
Windy Qin
CloverHeartsDev
Jongyoul Lee*
Jun Kim
Anthony Corbacho*
Ahyoung Ryu
Khalid Huseynov
Feli
Sofiane Cherchalli created ZEPPELIN-2338:
Summary: If Notebook execution fails, Notbook API should return a
500 code with meaningful reason, such as the error message or stacktrace
Key: ZEPPELIN-2338
URL:
Github user FRosner commented on the issue:
https://github.com/apache/zeppelin/pull/2176
I get what you are saying and I agree. My only point was that you need to
be aware that this change only does the following thing:
**Before**: Who persists the local changes earlier, wins
Dhayanithi Subramanian created ZEPPELIN-2337:
Summary: java.lang.NoClassDefFoundError:
org/glassfish/jersey/message/internal/HeaderUtils on lens query
Key: ZEPPELIN-2337
URL: https://issues.apache.org/
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2178
---
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 e
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2176
@FRosner Thanks for detailed reply.
We can't get the ultimate feature at once.
- locking
- realtime notification
- ...
IMO, This is just the first step. Then other
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2207
I think a more thorough solution is to separate the namespace between
python process and python repl. Only `ZeppelinContext` should be `available` in
python repl namespace. It would be better to s
Github user FRosner commented on the issue:
https://github.com/apache/zeppelin/pull/2176
I am not sure if this change helps. We still have a race condition and
conflict resolution is still "forceful overwrite and don't notify". If I see it
correctly:
*Before*: Who persists th
20 matches
Mail list logo
