Jeff Zhang created ZEPPELIN-1900:
Summary: Paragraph's top right area overlap with markdown output
Key: ZEPPELIN-1900
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1900
Project: Zeppelin
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1818
---
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/1824
---
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/1823
---
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
Jeff Zhang created ZEPPELIN-1899:
Summary: Fail to plot in pyspark interpreter
Key: ZEPPELIN-1899
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1899
Project: Zeppelin
Issue Type: Bug
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1587
---
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
Jeff Zhang created ZEPPELIN-1898:
Summary: White spaces in the beginning is stripped in pyspark
interpreter
Key: ZEPPELIN-1898
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1898
Project:
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1787
---
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 AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1758
@AlexanderShoshin Seems the below two things need to be done before merge
1. revert the last commit
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1820
---
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/1815
---
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/1822
@AhyoungRyu Thanks~ 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
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1834
@soralee Thanks for the improvement. I've also seen those issues when I was
using filter. Let me test this :)
---
If your project is set up for it, you can reply to this email and have your
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1822
@Leemoonsoo I've just updated as you said and the PR description as well.
Please take a look :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1816
Merge if there are no more comments 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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1828
@sotnich Thanks!! Please link this issue into the new 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
nirav patel created ZEPPELIN-1897:
-
Summary: REST API - Update API for paragraphs
Key: ZEPPELIN-1897
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1897
Project: Zeppelin
Issue Type:
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1809
Cool. ~~It also looks like CI is passing.~~ Hmm, I guess not..
Merging if no more comment.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1832
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 1ambda opened a pull request:
https://github.com/apache/zeppelin/pull/1835
[MINOR][DOCS] Add troubleshooting section to spark_cluster_mode.md
### What is this PR for?
I faced problems while executing docker image for spark on mesos described
in [Spark on Mesos
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1812
@Leemoonsoo
1. `yarn remove` and `yarn add` will update package.json as well.
2. But some people might not know how to use yarn, so it would be better to
- remove
Github user rasehorn commented on the issue:
https://github.com/apache/zeppelin/pull/1799
As far as I remember another discussion the paragraph IDs will change if
you export/import or copy a notebook (not sure which one applies). If that is
the case the workflow will be broken after
CloverHearts created ZEPPELIN-1896:
--
Summary: The ability to remove the result of a paragraph from your
code.
Key: ZEPPELIN-1896
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1896
Project:
CloverHearts created ZEPPELIN-1895:
--
Summary: Get paragraph status in code
Key: ZEPPELIN-1895
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1895
Project: Zeppelin
Issue Type: Sub-task
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1799
Yes, apart from workflow, this feature is essential. (Get paragraph status)
I want to separate getZeppelinJobStatus () into a separate PR, and I want
to improve the workflow by
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1799
@Leemoonsoo
Yes it seems to be good, I will make a new change.
---
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/1775
Tested and LGTM. Thanks @khalidhuseynov for the improvement.
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
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1799
```
z.getZeppelinJobStatus("execute note id", "execute paragraph
id").getJobStatus()
```
How about not repeating `Job`, `Status` and omit `Zeppelin` (while `z.`
represents
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1822
@Leemoonsoo Addressed your comment in
[d7d0087](https://github.com/apache/zeppelin/pull/1822/commits/d7d00872859d8d4f91e11875bbcd8e1012c8e2a6).
Please check if you have time.
---
If your
GitHub user soralee reopened a pull request:
https://github.com/apache/zeppelin/pull/1834
[ZEPPELIN-1864] Improvement to show folder and note after searching note
### What is this PR for?
This PR is for improvement to show folder and note after using the filter.
And I found
Github user soralee closed the pull request at:
https://github.com/apache/zeppelin/pull/1834
---
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
Jeff Zhang created ZEPPELIN-1894:
Summary: Matplotlib is very slow in python interpreter
Key: ZEPPELIN-1894
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1894
Project: Zeppelin
Issue
Github user sotnich commented on the issue:
https://github.com/apache/zeppelin/pull/1828
@jongyoul , sure, I will do it. I'll close this PR and will open a new one.
---
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 jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1828
@sotnich Thanks for the contribution. We, however, merged all functions of
PSQLInterpreter into JDBCInterpreter and will remove PSQLInterpreter sooner.
I'm very happy to adopt this function into
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1807
Flaky test. Will merge it if there're no more discussion.
---
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 cuspymd closed the pull request at:
https://github.com/apache/zeppelin/pull/1811
---
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 cuspymd commented on the issue:
https://github.com/apache/zeppelin/pull/1811
I've checked it is resolved at latest commit.
Thanks for your check.
---
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 sotnich commented on the issue:
https://github.com/apache/zeppelin/pull/1828
Looks like CI error does not have any relation with my PR. Could anyone
confirm that?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Jeff Zhang created ZEPPELIN-1893:
Summary: Extra non-necessary info is output in python interpreter
when using matplotlib
Key: ZEPPELIN-1893
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1893
Github user rasehorn commented on the issue:
https://github.com/apache/zeppelin/pull/1799
I'm also a little bit confused what this PR really is about - the pictures
above point to paragraph execution order and control but the discussion also
points to Notebook execution workflows.
Github user rasehorn commented on the issue:
https://github.com/apache/zeppelin/pull/1799
From my point of view this kind of functionality shall be provided by the
core framework.
I do not have created many notebooks but what I've done always is: create
one paragraph after the
41 matches
Mail list logo
