Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2153
---
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2111
@Remilito I've reverted this PR because it breaks all CI build.
```
$ changedfiles=$(git diff --name-only $TRAVIS_COMMIT_RANGE)
fatal: ambiguous argument '38d0207cd99d...362b7ca3c209':
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2149
---
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2149
Thanks for the review. Will merge it
---
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
GitHub user Leemoonsoo opened a pull request:
https://github.com/apache/zeppelin/pull/2153
[ZEPPELIN-2282] NPE on NotebookServer.java when client send null ticket.
### What is this PR for?
When client (zeppelin-web) send message with null ticket, NotebookServer
does not handle
Lee moon soo created ZEPPELIN-2282:
--
Summary: NPE on NotebookServer.java[onMessage]:356
Key: ZEPPELIN-2282
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2282
Project: Zeppelin
Issue
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2143
LGTM and merge to master if no further comments!
---
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 tinkoff-dwh commented on the issue:
https://github.com/apache/zeppelin/pull/2134
@Leemoonsoo
*location*
I think it's better to display above table because the output can be large
and user will not see message.
*style*
Bootstreap attracts attention and
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2144
Cool improvement!
LGTM and merge master if no further 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 your
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2134
Message location
Because of existing message `Results are limited by X.` and `Output
exceeds 10240. Truncated.` are displayed below the table.
I think showing `Attention!
GitHub user Leemoonsoo opened a pull request:
https://github.com/apache/zeppelin/pull/2152
[MINOR] Display chart by default in basic tutorial notebook
### What is this PR for?
From some point, "Zeppelin Tutorial/Basic Features (Spark)" tutorial
notebook does not display chart
Github user tinkoff-dwh commented on the issue:
https://github.com/apache/zeppelin/pull/2134
@Leemoonsoo
what final version, bootstrap?
---
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 Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2131
Merge to master and branch-0.7 if no further 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 your project does
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2134
In addition to @prabhjyotsingh mentions, there are another type of message
controlled by `ZEPPELIN_INTERPRETER_OUTPUT_LIMIT` env variable.
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2099
@Remilito Thanks for explain.
Let's say `graph: {mode: {...}}` is api A, and `config: {results: [{graph:
mode: {...}}]}` is api B.
When user use api A with multiple results,
Sachin Janani created ZEPPELIN-2281:
---
Summary: If execution of paragrah is aborted then the previous
results are cleared
Key: ZEPPELIN-2281
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2281
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2149
Tested
Per Note, Scoped
Per Note, Isolated
Per User, Scoped
Per User, Isolated
Per User, Scoped + Per Note, Scoped
Per User, Isolated + Per Note, Scoped
nevermind. One of my test is hanging because of a bug somewhere in my code.
On Fri, Mar 17, 2017 at 12:15 PM, Remy Gayet wrote:
> Hello guys,
>
> the second build configuration (env below) is now taking too much time ( >
> 49min) and gets killed, as per travis.org policy (
Github user andreaTP commented on the issue:
https://github.com/apache/zeppelin/pull/2093
Thanks a lot! appreciated this welcoming environment! (I was aiming to
become committer number 200 also )
---
If your project is set up for it, you can reply to this email and have your
reply
Alex Liu created ZEPPELIN-2280:
--
Summary: Spark Default Interpreter Setting Changed in
interpreter.json not Reflected in UI
Key: ZEPPELIN-2280
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2280
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2098
@1ambda Great work!
Let me test this interesting feature in this weekend.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
GitHub user Remilito opened a pull request:
https://github.com/apache/zeppelin/pull/2151
[ZEPPELIN-465] Be able to run paragraph and the following ones
### What is this PR for?
Allow to run a paragraph **and** the ones following. This is useful for
instance if you are
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2093
---
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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2150
It might be due to flaky tests. If so, please just restart failed jobs.
I'v just looked your travis build and it's ok
- https://travis-ci.org/andreaTP/zeppelin/builds/212066501
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2098
I'v just updated the PR description. Please help review this @AhyoungRyu :)
---
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 andreaTP commented on the issue:
https://github.com/apache/zeppelin/pull/2150
Thanks for the feedback @1ambda , travis should be configured properly now,
I will try to dig into but it looks tests spuriously fail, anyhow any help on
getting the right direction is highly
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2150
Hi @andreaTP. Thanks for contribution.
- Zeppelin build system relies on travis. So please setup your travis
account and travis project for Zeppelin.
-
Github user tinkoff-dwh commented on the issue:
https://github.com/apache/zeppelin/pull/2112
CI green, https://travis-ci.org/tinkoff-dwh/zeppelin/builds/208970773 ,
commit is correct 8323392,
but status failed (tried reopen) failed.
---
If your project is set up for it, you can
GitHub user tinkoff-dwh reopened a pull request:
https://github.com/apache/zeppelin/pull/2112
[ZEPPELIN-2228] precode for SparkRInterpreter
### What is this PR for?
Added parameter zeppelin.pyspark.precode to SparkRInterpreter. This is
snippet of code which executes when
Github user tinkoff-dwh closed the pull request at:
https://github.com/apache/zeppelin/pull/2112
---
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
Tinkoff DWH created ZEPPELIN-2279:
-
Summary: Incorrect parsing queries if there are comments
Key: ZEPPELIN-2279
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2279
Project: Zeppelin
Github user andreaTP commented on the issue:
https://github.com/apache/zeppelin/pull/2150
failures looks unrelated ...
---
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
Hello guys,
the second build configuration (env below) is now taking too much time ( >
49min) and gets killed, as per travis.org policy (
https://docs.travis-ci.com/user/customizing-the-build#Build-Timeouts).
SCALA_VER=\"2.11\" SPARK_VER=\"2.1.0\" HADOOP_VER=\"2.6\"
LIVY_VER=\"0.3.0\"
Github user andreaTP commented on the issue:
https://github.com/apache/zeppelin/pull/2093
updated also commit message here
---
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
GitHub user andreaTP opened a pull request:
https://github.com/apache/zeppelin/pull/2150
[ZEPPELIN-2278] Env variable to configure Npm registry
### What is this PR for?
When deploying Zeppelin in private Cloud or within closed networks, it
happens that Npm Registry isn't
Andrea Peruffo created ZEPPELIN-2278:
Summary: Env variable to configure Npm registry
Key: ZEPPELIN-2278
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2278
Project: Zeppelin
Issue
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2141
Seems some review comments are mixed up in github side :(
I just removed some of them and left comment again. Please let me know if
you're confused.
---
If your project is set up for
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2141
@guicaro Thanks for your great contribution!
I left some comments. Could you take a look at them? Please let me know if
there is something that I missed :)
---
If your project is set up
Github user andreaTP commented on the issue:
https://github.com/apache/zeppelin/pull/2093
Yep, opened Jira issue and linked accordingly on PR title.
https://issues.apache.org/jira/browse/ZEPPELIN-2277
@Leemoonsoo thanks!
---
If your project is set up for it, you can
Andrea Peruffo created ZEPPELIN-2277:
Summary: Env variable to configure maven central repo
Key: ZEPPELIN-2277
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2277
Project: Zeppelin
Github user Leemoonsoo closed the pull request at:
https://github.com/apache/zeppelin/pull/2138
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2137
---
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
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2106
@astroshim made [a
pullrequest](https://github.com/astroshim/zeppelin/pull/16) to this branch, to
bringing docker support back . Please take a look and merge if you think it's
okay.
---
If
43 matches
Mail list logo