Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1861
@felixcheung @minahlee Could any of you help to merge it into branch-0.7 as
well ? Since this is only livy interpreter specific, so I don't think it would
affect the 0.7 release.
---
If your pro
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1861
@felixcheung @minahlee , Sorry my mistake, I has been merged into
branch-0.7. @minahlee I notice you make the jira fixversion as 0.8, I add 0.7
as well.
---
If your project is set up for it, you
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1905
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 feat
GitHub user minahlee opened a pull request:
https://github.com/apache/zeppelin/pull/1906
[DOCS] Update interpter installation guide
### What is this PR for?
* Update Scio interpreter's artifact name from `scio` to `scio_2.11`, which
will be used for installing scio interpreter f
GitHub user cuspymd opened a pull request:
https://github.com/apache/zeppelin/pull/1907
[MINOR] Add enough padding at the bottom of notebook
### What is this PR for?
It is inconvenient to edit last paragraph.
So I added enough padding at the bottom of notebook.
### W
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1883
LGTM. Since branch-0.7 is already created, shell we merge this guy asap?
---
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/1905
Thanks @1ambda for taking a look.
Merge to master if 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
GitHub user Leemoonsoo opened a pull request:
https://github.com/apache/zeppelin/pull/1908
[ZEPPELIN-1976] Text-Output too large, causing crash
### What is this PR for?
This PR implements interpreter output message limit.
`ZEPPELIN_INTERPRETER_OUTPUT_LIMIT` env variable
Github user cloverhearts closed the pull request at:
https://github.com/apache/zeppelin/pull/1864
---
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 featur
GitHub user cloverhearts reopened a pull request:
https://github.com/apache/zeppelin/pull/1864
[ZEPPELIN-1921] missing close in closeAndRemoveInterpreterGroup method
### What is this PR for?
The problem is that some code in the closeAndRemoveInterpreterGroup method
of Interprete
Sherif Akoush created ZEPPELIN-1977:
---
Summary: spark 2.1 uses a more recent commons-lang3
Key: ZEPPELIN-1977
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1977
Project: Zeppelin
Issue
Khalid Huseynov created ZEPPELIN-1978:
-
Summary: Corrupt notebook authorization file breaks zeppelin
server start
Key: ZEPPELIN-1978
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1978
Projec
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1902
great Contribution for elasticsearch interpreter! This PR helps us to
support ES 5.0 easily!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
GitHub user khalidhuseynov opened a pull request:
https://github.com/apache/zeppelin/pull/1909
[ZEPPELIN-1978] Let Zeppelin server start if authorization file is corrupt
### What is this PR for?
This is to let Zeppelin server start even when the notebook authorization
file is c
Should we disable these flaky test now ? CI seems become more unstable
recently. It is almost useless for me, I never see a success CI recently.
Here's one screenshot of recent closed PRs. Most of them has CI failure.
IMO, this is pretty bad, especially for new contributors.
[image: pasted1]
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1796
@jongyoul @felixcheung Could you help merge it into branch-0.7 and master ?
CI failure is not relevant.
```
Failed tests:
NotebookTest.testAbortParagraphStatusOnInterpreterResta
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1864
@jongyoul
Shows that a part of the test case is forcibly terminated.
I would like to suspend merge until this issue is resolved. :)
---
If your project is set up for it, you can repl
Github user jcam3ron commented on the issue:
https://github.com/apache/zeppelin/pull/1466
Any update on whether this might be merged 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
GitHub user cloverhearts reopened a pull request:
https://github.com/apache/zeppelin/pull/1864
[ZEPPELIN-1921] missing close in closeAndRemoveInterpreterGroup method
### What is this PR for?
The problem is that some code in the closeAndRemoveInterpreterGroup method
of Interprete
Github user cloverhearts closed the pull request at:
https://github.com/apache/zeppelin/pull/1864
---
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 featur
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1864
fixed
---
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 t
Github user doanduyhai commented on the issue:
https://github.com/apache/zeppelin/pull/1466
Let me redo the PR and merge with the above remarks included
---
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 minahlee commented on the issue:
https://github.com/apache/zeppelin/pull/1906
Merge if there is 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 does not have this feature
enable
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1796
CI was green I think https://travis-ci.org/apache/zeppelin/builds/189432940
---
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 asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1796
---
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 zjffdu opened a pull request:
https://github.com/apache/zeppelin/pull/1910
ZEPPELIN-1977. spark 2.1 uses a more recent commons-lang3
### What is this PR for?
The issue is that spark 2.1 use `commons-lang3` 3.5 while
`zeppelin-interpreter` use 3.4. We can not just upg
Github user sotnich commented on the issue:
https://github.com/apache/zeppelin/pull/1886
Don't think CI errors are related to this PR.
---
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 fea
27 matches
Mail list logo