Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1861
LGTM.
what is the bug in LivySparkSQLInterpreter - should we have a JIRA for it?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user minahlee commented on the issue:
https://github.com/apache/zeppelin/pull/1879
Tested, 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
GitHub user zjffdu opened a pull request:
https://github.com/apache/zeppelin/pull/1880
ZEPPELIN-1918. Fix build with Spark 2.1.0
### What is this PR for?
It's my misunderstanding of `SPARK_VER` in travis. It is only used for
downloading spark distribution. We need to specify
GitHub user cloverhearts reopened a pull request:
https://github.com/apache/zeppelin/pull/1879
[HOTFIX : ZEPPELIN-1932] paragraph blur error
### What is this PR for?
When one or more hidden editors are present, clicking on the editor will
cause a blur error.
This means that
Github user cloverhearts closed the pull request at:
https://github.com/apache/zeppelin/pull/1879
---
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 asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1850
---
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 prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1845
@astroshim do you have some cycle to review 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
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1787
Sure, let me fix 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
enabled and wishes
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1787
Let's get this fix ASAP - we are going to cut 0.7 release in 2 days
---
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
Hi,
It's been almost 3 month since we did 0.6.2 release and there were number
of improvements and bug fixes.
Most of the items that we planned for 0.7.0 release [1] are ready
so I am planning to cut branch-0.7 on 10th Jan 11pm(PST).
After branch cut, bug fixes, documentation patches and issues
GitHub user cloverhearts opened a pull request:
https://github.com/apache/zeppelin/pull/1879
[HOTFIX : ZEPPELIN-1932] paragraph blur error
### What is this PR for?
When one or more hidden editors are present, clicking on the editor will
cause a blur error.
This means that
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1787
ping @ejono Do you want to contribute it ? If not, I will fix 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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1842
Let me review this PR. I wil comment again :)
---
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 commented on the issue:
https://github.com/apache/zeppelin/pull/1842
Awesome! 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 cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1877
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 Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1877
LGTM and merge to master 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 your project does
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1875
@Leemoonsoo I moved all font-related licenses from `bin_license` to
`/LICENSE`
Aldo remove rat exclusion in `zeppeiln-web/pom.xml` for `google-fonts.css`
because it is managed by us now.
---
Github user khalidhuseynov commented on the issue:
https://github.com/apache/zeppelin/pull/1877
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
GitHub user cloverhearts opened a pull request:
https://github.com/apache/zeppelin/pull/1878
add yarn_error.log in gitignore
### What is this PR for?
Currently zeppelin is built from yarn.
Therefore, we need to add a log to gitignore.
### What type of PR is it?
CloverHearts created ZEPPELIN-1931:
--
Summary: we should be add yarn_error.log on gitignore.
Key: ZEPPELIN-1931
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1931
Project: Zeppelin
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1789
Tested and LGTM. Thanks @cuspymd for the nice optimization!
Merge to master if no more discussions.
---
If your project is set up for it, you can reply to this email and have your
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1852
Thanks @1ambda for the fix.
LGTM and merge if no more 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
GitHub user astroshim reopened a pull request:
https://github.com/apache/zeppelin/pull/1877
[ZEPPELIN-1930](HotFix) PythonInterpreter syntax error.
### What is this PR for?
This PR fixes syntax error of PythonInterpreter.
### What type of PR is it?
Bug Fix
Github user astroshim closed the pull request at:
https://github.com/apache/zeppelin/pull/1877
---
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 astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1877
@agoodm pyspark interpreter is working well.
---
If your project is set up
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1877
I faced the same problem too. Thanks for fix!
---
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 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1868
@Leemoonsoo Thanks for review!
If https://github.com/apache/zeppelin/pull/1874 is merged soon, I can
rewrite the whole `conda env *` commands based on #1874
since current
Github user agoodm commented on the issue:
https://github.com/apache/zeppelin/pull/1877
I am on vacation right now so I can't thoroughly examine this, but have you
confirmed that this isn't a problem for the pyspark interpreter?
---
If your project is set up for it, you can reply
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 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 bitchelov commented on the issue:
https://github.com/apache/zeppelin/pull/1747
@lresende is it right?
---
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 Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1846
@zjffdu Thanks for the patch!
I also think this PR deserves a unittest to make sure correct restart
behavior, like @felixcheung mentioned, if it is not too much difficult.
---
If
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1877
Thanks for the fix. \cc @agoodm
How about add an unittest for this case in
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1860
LGTM and merge to 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 project does not have
GitHub user astroshim opened a pull request:
https://github.com/apache/zeppelin/pull/1877
[ZEPPELIN-1930](HotFix) PythonInterpreter syntax error.
### What is this PR for?
This PR fixes syntax error of PythonInterpreter.
### What type of PR is it?
Bug Fix
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1812
---
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 soralee commented on the issue:
https://github.com/apache/zeppelin/pull/1834
@AhyoungRyu I updated the filter of Navbar.
But, the folder of notes in navbar don't have previous status. Because If
using the hidden value of the note, it works together both the filter in
Shim HyungSung created ZEPPELIN-1930:
Summary: SyntaxError on PythonInterpreter
Key: ZEPPELIN-1930
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1930
Project: Zeppelin
Issue Type:
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1872
You don't have to make two PRs for adopting multiple branches. We can merge
it into several branches with one commit if there's no conflict. Can you please
close this PR?
---
If your project
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1861
Tested locally, 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 this feature
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 jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1875
@1ambda Does it reduce the build time of web module?
---
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/1874
LGTM and merge to 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 project does not
Shim HyungSung created ZEPPELIN-1929:
Summary: need to fix the output format of PythonInterpreter
Key: ZEPPELIN-1929
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1929
Project: Zeppelin
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1868
Great improvement! Tested and LGTM.
Is it on purpose not supporting `conda env remove` ?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1861
@felixcheung I have addressed the comments and also fix one bug in
LivySparkSQLInterpreter, and update the screenshot of testing in PR
description.
---
If your project is set up for it, you can
Github user minahlee commented on the issue:
https://github.com/apache/zeppelin/pull/1838
Thx for the fix. I will merge this one as temporary fix, but I will keep
the jira issue open until we come up with better solution.
---
If your project is set up for it, you can reply to this
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1876
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 AlexanderShoshin commented on the issue:
https://github.com/apache/zeppelin/pull/1758
Sorry, I was not able to work on this issue during last weeks.
@AhyoungRyu, I will make the corrections soon.
Thanks
---
If your project is set up for it, you can reply to this
Github user ChrisAdvance commented on the issue:
https://github.com/apache/zeppelin/pull/1030
Does the "Connection refused" problem fixed yet?
---
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 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1875
@Leemoonsoo Thanks for detailed explanation. I will take a look.
---
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 Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1875
This PR makes zeppelin source distribution package contains font files.
Therefore, related font license should be moved from
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1838
@cloverhearts The last travis doesn't look related error.
---
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
53 matches
Mail list logo
