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
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
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1867
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/1869
Thanks for comment @AhyoungRyu :)
Also, CI failed but irrelevant.
---
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 astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1862
Tested and LGTM!
Thanks @jongyoul
---
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 zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1845
I don't think it make sense to have a fixed minimum table size. It should
also take into account the output row number. Anyway, we can improve it in a
followup ticket.
---
If your project is
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1845
Yes, that is our default minimum size of display table.
CI fails [#9847.5](https://travis-ci.org/apache/zeppelin/jobs/189775789);
which is not relevant to this. Will merge this if
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1853
@felixcheung You're right! `evaluate` is dependency package of `knitr`.
Thanks for pointing out. It's my misunderstood.
Let me close this PR.
---
If your project is set up for it, you
Github user astroshim closed the pull request at:
https://github.com/apache/zeppelin/pull/1853
---
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 AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1869
Yeah I removed this line in my local since I can't start debug mode in
IntelliJ with `there is no zeppelin-web/dist` error.
LGTM ð
---
If your project is set up for it, you can reply
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1855
---
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 asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1851
---
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/1869
\cc @Leemoonsoo for 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 feature
enabled and
GitHub user 1ambda opened a pull request:
https://github.com/apache/zeppelin/pull/1869
[MINOR] fix: DON'T clean in npm run dev since useless
### What is this PR for?
Removed clean task in npm run dev because webpack-dev-server uses in-memory
build :)
This was annoying
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1813
---
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 opened a pull request:
https://github.com/apache/zeppelin/pull/1868
[ZEPPELIN-1917] Improve python.conda interpreter
### What is this PR for?
Add missing commands to the `python.conda` interpreter
- `conda info`
- `conda list`
- `conda
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1862
It's good idea to make it but, for now, we cannot do it because we have
zombie process problem when we test it. I think we can do it after we solve
that former problem.
---
If your project is
Github user khalidhuseynov closed the pull request at:
https://github.com/apache/zeppelin/pull/1566
---
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/1842
It's ok of you to have a plan to divide them. Thanks.
---
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 Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1812
Thanks for explanation. LGTM and merge 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. If your project
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1862
Great! I guess I was asking if it's possible to have automated tests so it
wouldn't break in the future.
---
If your project is set up for it, you can reply to this email and
Egor Pahomov created ZEPPELIN-1923:
--
Summary: I can build project with scala 2.10, but not scala 2.11.
Key: ZEPPELIN-1923
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1923
Project: Zeppelin
Egor Pahomov created ZEPPELIN-1922:
--
Summary: Wrong version of jackson fails spark code
Key: ZEPPELIN-1922
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1922
Project: Zeppelin
Issue
GitHub user cloverhearts reopened a pull request:
https://github.com/apache/zeppelin/pull/1721
[ZEPPELIN-969] order by note name in job menu
### What is this PR for?
we can sort by note name in job menu.
Sorting supports ascending and descending order.
Sort by note name.
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1814
Fixed done.
CI is green :)
---
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 felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1422
where are we on this?
---
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 felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1867
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
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1787
this #1856 should help too
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1856
---
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 asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1837
---
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/1842
@jongyoul I think helium related code can be extracted from
zeppelin-zengine to a new module, zeppelin-helium. However, extracting code and
create new module is not this PR's scope. that can
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1863
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 Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1865
Tested and 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
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1866
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 zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1845
LGTM, but I notice there's one large blank area before this exception. Is
it expected ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/1867
[MINOR][ZEPPELIN-1919] Reduce markdown intp's plain text font size
### What is this PR for?
Currently Zeppelin `%md` result style is using
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1845
@zjffdu How about this ? On error show output of previous successfully run
query.
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1845
`What if one query fails ?`
There is no change in that. When it fails and doesn't continue.
Before:
GitHub user minahlee opened a pull request:
https://github.com/apache/zeppelin/pull/1866
[MINOR] Remove redundant log4j license
### What is this PR for?
Remove redundant log4j license:
GitHub user minahlee opened a pull request:
https://github.com/apache/zeppelin/pull/1865
[ZEPPELIN-1723] Math formula support library path error
### What is this PR for?
When user set `ZEPPELIN_SERVER_CONTEXT_PATH`, web cannot find MathJax
library because root location is set
GitHub user cloverhearts reopened a pull request:
https://github.com/apache/zeppelin/pull/1814
[ZEPPELIN-1869] changed the API response to generate to 200.
### What is this PR for?
A few sentences describing the overall goals of the pull request's commits.
First time? Check
Github user cloverhearts closed the pull request at:
https://github.com/apache/zeppelin/pull/1814
---
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 cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1864
I was change Linked list to Linked HashSet.
---
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 commented on the issue:
https://github.com/apache/zeppelin/pull/1787
Oh, sorry I also didn't check it carefully. I'll check it manually when you
guys create new PR for handling a new issue
---
If your project is set up for it, you can reply to this email and
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1858
@astroshim still some missing in the $routeProvider.
Otherwise I just want to point out that the original goal of the cache
buster is to add a hash in the file name so that it is different
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1864
Hello @jongyoul.
Could you please review for 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
GitHub user cloverhearts opened 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
CloverHearts created ZEPPELIN-1921:
--
Summary: Code bug, closeAndRemoveInterpreterGroup method of
InterpreterSetting partially closes
Key: ZEPPELIN-1921
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1921
GitHub user minahlee opened a pull request:
https://github.com/apache/zeppelin/pull/1863
[ZEPPELIN-1920] Fail to load app.js when ZEPPELIN_SERVER_CONTEXT_PATH is set
### What is this PR for?
If user set env variable `ZEPPELIN_SERVER_CONTEXT_PATH`, web fails to load
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1845
@prabhjyotsingh What if one query fails ? Would it continue to run the
remaining queries or abort ? And since this is a new feature, we might better
to add document for it.
---
If your project
Mina Lee created ZEPPELIN-1920:
--
Summary: Fail to load app.js when ZEPPELIN_SERVER_CONTEXT_PATH is
set
Key: ZEPPELIN-1920
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1920
Project: Zeppelin
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1799
@rasehorn @zjffdu
Thank you very much!
I understand the function wait.
I will try to organize it again based on your opinion.
Thank you for your kind comments.
---
If your
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1862
Hello @felixcheung
I have created and tested a remote interpreter.
1. Go to zeppelin/bin.
2. Run the following:
   `bin/bash ./interpreter.sh -d ../interpreter/python -p
Ahyoung Ryu created ZEPPELIN-1919:
-
Summary: Font size of markdown interpreter is too big
Key: ZEPPELIN-1919
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1919
Project: Zeppelin
Issue
54 matches
Mail list logo
