Github user zhongneu commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/754#issuecomment-189806808
fixed the test
---
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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/754#issuecomment-189802314
btw, it looks like this might be a legitimate test failure, could you take
a look?
https://s3.amazonaws.com/archive.travis-ci.org/jobs/112358128/log.t
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/754#issuecomment-189801164
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 f
Github user AhyoungRyu commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/753#issuecomment-189798899
@mwkang Thx! Looks good : )
---
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 projec
Github user zhongneu commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/754#issuecomment-189788087
@felixcheung great idea. updated & tested. full stack trace will be logged
in the interpreter log
---
If your project is set up for it, you can reply to th
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/754#issuecomment-189787467
thx - let's add logger to capture the full stack before returning with
InterpreterResult?
```
logger.error("Invocation target exception", e);
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/480#issuecomment-189786658
@prabhjyotsingh probably - we could say 'restart this interpreter X - note
that all interpreter states and local variables will be reset' or similar.
Wou
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/713#issuecomment-189785882
looks good - great contribution!
---
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 pull request:
https://github.com/apache/incubator-zeppelin/pull/734#issuecomment-189785823
@doanduyhai is cassandra supported on windows?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user zhongneu commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/754#issuecomment-189785825
@felixcheung definitely. updated based on your comment
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHu
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/753#issuecomment-189785676
looks good
---
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
Sourav: I think this newly merged PR can help you
https://github.com/apache/incubator-zeppelin/pull/703#issuecomment-185582537
On Sat, Feb 27, 2016 at 1:46 PM, Sourav Mazumder <
sourav.mazumde...@gmail.com> wrote:
> Hi Moon,
>
> This looks great.
>
> My only suggestion would be to include a PR/fe
Felix Cheung created ZEPPELIN-704:
-
Summary: Display elapse time for long running paragraph
Key: ZEPPELIN-704
URL: https://issues.apache.org/jira/browse/ZEPPELIN-704
Project: Zeppelin
Issue T
GitHub user zhongneu opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/754
[ZEPPELIN-679] only print the error message for SQL exceptions
### What is this PR for?
Most of the SQL exceptions are syntax errors. Printing the full stack trace
is not neces
This is awesome! Really glad to see that the roadmap is adjusted based on
the community's needs. One feature I hope to see in 0.6.0 is folder
support, which can benefit both "UX improvement" and "Multi-tenacy".
Zhong
On Sat, Feb 27, 2016 at 1:46 PM, Sourav Mazumder <
sourav.mazumde...@gmail.com>
Looks fantastic moon.
Anything in the community with regards to easier debugging with specific
backends? E.g. spark.
Sent from my Verizon Wireless 4G LTE smartphone
Original message
From: moon soo Lee
Date: 02/27/2016 3:48 PM (GMT-05:00)
To: us...@zeppelin.incubator.a
Hi Moon,
This looks great.
My only suggestion would be to include a PR/feature - Support for Running
Concurrent paragraphs/queries in Zeppelin.
Right now if more than one user tries to run paragraphs in multiple
notebooks concurrently through a single Zeppelin instance (and single
interpreter in
It's a great update Moon.
Monday I'll give a talk at Voxxed Days Vienna about Zeppelin, your email
will be helpful to give some hints about the future of Zeppelin
On Sat, Feb 27, 2016 at 9:48 PM, moon soo Lee wrote:
> Hi Zeppelin users and developers,
>
> The roadmap we have published at
> h
Hi Zeppelin users and developers,
The roadmap we have published at
https://cwiki.apache.org/confluence/display/ZEPPELIN/Zeppelin+Roadmap
is almost 9 month old, and it doesn't reflect where the community goes
anymore. It's time to update.
Based on mailing list, jira issues, pullrequests, feedbacks
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/713#issuecomment-189680443
Merge if there're no more discussions.
---
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 Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/703#issuecomment-189678616
Thanks @jongyoul @AhyoungRyu @felixcheung @echarles @khalidhuseynov for
taking a look and review.
Merging it if there're no more discussions.
--
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/753#issuecomment-189678092
Thanks for the documentation.
Looks good to me!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHu
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/739
---
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 fea
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/681#issuecomment-189673562
ZEPPELIN-666 is going to handle portability of notebook authorization
permissions stored in note file.
And about the searchservice @hayssams mentions,
GitHub user mwkang opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/753
[ZEPPELIN-498]Manual upgrade procedure for Zeppelin
### What is this PR for?
Describe Manual upgrade procedure for Zeppelin.
### What type of PR is it?
Documentation
25 matches
Mail list logo
