Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1887
I will open another PR for this. Too many conflicts ð
---
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 ha
Github user 1ambda closed the pull request at:
https://github.com/apache/zeppelin/pull/1887
---
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 wary commented on the issue:
https://github.com/apache/zeppelin/pull/2196
ok, After get off workï¼I will remove the comments and explain detail for
this PR, thx
---
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 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2178
@felixcheung It's not that noisy. Because
1. The logs occurs only when user enable / disable helium packages.
2. And it is not usual action.
---
If your project is set up for it, you c
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2181
Just rebased and CI is green now.
---
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 zjffdu opened a pull request:
https://github.com/apache/zeppelin/pull/2197
ZEPPELIN-2324. Add property zeppelin.spark.unSupportedVersionCheck for
trying new spark version
### What is this PR for?
For now, every time when I want to try new spark version, I have to cha
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2113
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 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2174
@AhyoungRyu Sorry for confusing. It works as described. maybe i mixed
commits ð
- It would be nice if we hide `<<` and `>>` when users don't need it. (e.g
less than 5 pages)
Jeff Zhang created ZEPPELIN-2324:
Summary: Add property zeppelin.spark.unSupportedVersionCheck for
trying new spark version
Key: ZEPPELIN-2324
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2324
Github user soralee commented on the issue:
https://github.com/apache/zeppelin/pull/2196
Thanks @wary for fixing this!
But, could you explain detail this PR such as `what is this PR for` and
`How should this be test`?
---
If your project is set up for it, you can reply to this e
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2196
Hi @wary Thanks for contribution.
- Zeppelin build system relies on travis. So please setup your travis
account and travis project for Zeppelin.
-
https://zeppelin.apache.org/contrib
GitHub user wary opened a pull request:
https://github.com/apache/zeppelin/pull/2196
fix bugs for timer saver
### What is this PR for?
A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide -
https://zeppelin.
Github user del680202 commented on the issue:
https://github.com/apache/zeppelin/pull/2191
I check this PR, it works well, 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 have this feature
Github user wary closed the pull request at:
https://github.com/apache/zeppelin/pull/2193
---
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 ena
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2195
@meniluca I am a little conservative for adding new public api in
ZeppelinContext. As new api means more overhead to maintain it and keep
backward compatibility. Could you describe the scenario of
GitHub user meniluca opened a pull request:
https://github.com/apache/zeppelin/pull/2195
[ZEPPELIN-2319] new methods for ZeppelinContext
### What is this PR for?
Adds new methods to ZeppelinContext to run paragraphs in a more
user-friendly mode.
```java
z.runAllBefo
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2135
Thanks @dlukyanov for the contribution.
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 h
Github user dlukyanov commented on the issue:
https://github.com/apache/zeppelin/pull/2135
@Leemoonsoo , done. waiting for travis.
---
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 commented on the issue:
https://github.com/apache/zeppelin/pull/2188
Merged to master, but didn't merged to branch-0.7 because of conflict.
---
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 pr
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2188
---
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 Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2192
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 soralee commented on the issue:
https://github.com/apache/zeppelin/pull/2186
Let's move on #2194 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 feature
enabled and wishe
Github user soralee closed the pull request at:
https://github.com/apache/zeppelin/pull/2186
---
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/2186
I closed this PR. Because In the better way which keeps on the latest
version, @Remilito suggested #2194, I think we don't need to talk about this PR
any more.
---
If your project is set up for
Github user soralee commented on the issue:
https://github.com/apache/zeppelin/pull/2194
@Remilito Sounds great! It looks good to me.
With this PR, we can keep on using the latest version of the nvd3.
Personally, I like your annotations per code spot. Because it can keep remind
us
Github user soralee commented on the issue:
https://github.com/apache/zeppelin/pull/2191
Tested and It works as your described, 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 feat
Github user Remilito commented on the issue:
https://github.com/apache/zeppelin/pull/2186
@soralee , @AhyoungRyu , @anthonycorbacho : proposal of workaround here,
https://github.com/apache/zeppelin/pull/2194 . Feedbacks welcome!
---
If your project is set up for it, you can reply to
GitHub user Remilito opened a pull request:
https://github.com/apache/zeppelin/pull/2194
[ZEPPELIN-2229] Providing workaround for nvd3 voronoi
### What is this PR for?
After bumping nvd3 to 1.8.5, an error was spotted due to a bug in nvd3.
This PR provides a workaround until the
Github user soralee commented on the issue:
https://github.com/apache/zeppelin/pull/2193
@wary This branch is fault and not regarding of ZEPPELIN-2323. Could you
close this PR and make sure your branch?
---
If your project is set up for it, you can reply to this email and have your
GitHub user wary opened a pull request:
https://github.com/apache/zeppelin/pull/2193
Branch 0.7
### What is this PR for?
A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide -
https://zeppelin.apache.org/con
LeiWang created ZEPPELIN-2323:
-
Summary: edited paragraphs are not saved in a timely manner
Key: ZEPPELIN-2323
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2323
Project: Zeppelin
Issue Typ
sulphide created ZEPPELIN-2322:
--
Summary: how can i turn off scala and just default to %pyspark
Key: ZEPPELIN-2322
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2322
Project: Zeppelin
Issu
I cherry-picked ZEPPELIN-1984. We, however, have more issues to be merged
as an hotfix
On Fri, Mar 24, 2017 at 4:52 PM, Jeff Zhang wrote:
> Sorry, I need to -1 again, as I just found that ZEPPELIN-1984 is also
> needed to backport. Otherwise no error message displayed in frontend when
> interpre
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2174
@felixcheung Let me check again for that part.
---
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 thi
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2174
@1ambda It's wired. This is what I can see when I build my branch.
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2163
@Leemoonsoo Thanks!
Merge into master and branch-0.7 if there are no more comments
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub a
GitHub user Remilito opened a pull request:
https://github.com/apache/zeppelin/pull/2192
[ZEPPELIN-2320] fixing test + modifying map browsing
### What is this PR for?
fixing String comparison and improving map browsing
### What type of PR is it?
Bug Fix
###
Github user soralee commented on the issue:
https://github.com/apache/zeppelin/pull/2186
@Remilito @anthonycorbacho Thanks for opinions!
Yeah, I think whatever we use 1.7.1 version or 1.8.5 versions, we have a
lot of bugs. `nvd3` release process is too slow and, I'm not sure 1.8.5
richard.lee created ZEPPELIN-2321:
-
Summary: zeppelin hungup when executing cronjob
Key: ZEPPELIN-2321
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2321
Project: Zeppelin
Issue Type: B
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2182
I got one error from travis. It seems to be related issue
---
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 asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2187
---
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 soralee commented on the issue:
https://github.com/apache/zeppelin/pull/2186
@AhyoungRyu I checked [your comment about translate
error](https://github.com/apache/zeppelin/pull/2186#issuecomment-289178564).
The error seems to be caused by incompatibility with the 1.7.1 v
Github user anthonycorbacho commented on the issue:
https://github.com/apache/zeppelin/pull/2186
I will agree with @Remilito on this one.
I think we can come up with a workaround and keep 1.8.5.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1976
@del680202 Thanks, if you finish to test it, we will make a new rc
including it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user del680202 commented on the issue:
https://github.com/apache/zeppelin/pull/1976
@jongyoul Thanks, I will test it later
---
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 jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1976
@del680202 I've made a PR for handling what you found. Can you please test
it with that PR? #2191
---
If your project is set up for it, you can reply to this email and have your
reply appear on
GitHub user jongyoul opened a pull request:
https://github.com/apache/zeppelin/pull/2191
[HOTFIX] Keep interpreter group when save and restart
### What is this PR for?
Not removing interpreter group reference while editing and saving
interpreter setting.
### What type o
Remy Gayet created ZEPPELIN-2320:
Summary: Fix flaky test in rest api testing
Key: ZEPPELIN-2320
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2320
Project: Zeppelin
Issue Type: Bug
Github user tinkoff-dwh closed the pull request at:
https://github.com/apache/zeppelin/pull/2134
---
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 tinkoff-dwh reopened a pull request:
https://github.com/apache/zeppelin/pull/2134
[ZEPPELIN-2257] notification about incompleteness of data
### What is this PR for?
Added notification about exceeding the limit in the result.
### What type of PR is it?
Imp
Github user Remilito commented on the issue:
https://github.com/apache/zeppelin/pull/2186
My 2 cts here:
Yep the scatter chart bug in 1.8.5 is annoying, and unfortunately nvd3 does
not seem to release very frequently ( 2-3 times a year or so). However I am not
sure reverting the l
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2176
@FRosner
**How do I get the remote changes / discard my local changes**
- Zeppelin will synchronize text automatically. That's the reason why it
doesn't have button for that.
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2177
@FRosner Anything would be greatly appreciated. For example trying this PR,
suggestion for how to write test code for this, and so on.
regarding to triggering auto-save, Zeppelin send `star
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2174
@AhyoungRyu pagination DOM should be located outside of `ng-repeat` for
helium containers.
https://cloud.githubusercontent.com/assets/4968473/24344271/9e910240-1305-11e7-86f1-51438b9a76c3.p
54 matches
Mail list logo
