Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1210
@mwpenny With the way we include the css, there is still a risk of not
being able to get the css, but having the JS file just fine.
Which end up in the map not showing, and no error message
Github user minahlee commented on the issue:
https://github.com/apache/zeppelin/pull/1321
Merge if there is 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 have this feature
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1193
@astroshim great! Small suggestion above. And what is with CI here? May be
it's worth to `git rebase master` and force push?
---
If your project is set up for it, you can reply to this email and
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1321
Looks great to me @minahlee !
---
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 bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1248
Thanks! In my experience, if in case of CI failure PR author posts the
failure result from logs - that speeds us review a lot!
CI fails now on Spark 1.6 Scala 2.10 and Scala 2.11 profiles
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1254
@khalidhuseynov `git rebase master` to re-trigger CI?
---
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 bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1318
Docs looks great to me, thank you @astroshim !
---
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 felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1314
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 as well. If your project does not have this feature
enabled
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1318
cool. hadoop versions in distributions:
CDH: 2.6.0
HDP/Azure: 2.7.1
EMR: 2.7.2
GCP Dataproc: 2.7.2
---
If your project is set up for it, you can reply to this email and have
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1322
shouldn't interpreter process be impersonating the user logging onto the
web front end?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1264
---
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 mwpenny commented on the issue:
https://github.com/apache/zeppelin/pull/1210
@corneadoug I'm all to familiar with that magic when trying to reproduce
bugs ;)
I've made the changes.
* __Small popup:__ The side and bottom margins of the popup are present
Kshitij Badani created ZEPPELIN-1322:
Summary: zeppelin.ssl.truststore is getting configured to keystore
by default if truststore is empty
Key: ZEPPELIN-1322
URL:
Yesha Vora created ZEPPELIN-1321:
Summary: Zeppelin HTTP and HTTPS port should be managed seperately
Key: ZEPPELIN-1321
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1321
Project: Zeppelin
GitHub user khalidhuseynov reopened a pull request:
https://github.com/apache/zeppelin/pull/1254
[ZEPPELIN-1257] storage - fix get note revision api
### What is this PR for?
Getting revision of note requires only unique revision id and the whole
revision object isn't required.
Github user khalidhuseynov commented on the issue:
https://github.com/apache/zeppelin/pull/1304
@bzz exactly, that's the point i was trying to make in #1254.
@anthonycorbacho i'm completely agree with you, and that was the original
starting premise.
I'm happy that everyone
GitHub user prabhjyotsingh opened a pull request:
https://github.com/apache/zeppelin/pull/1322
[ZEPPELIN-1320] Security fix for Shell/Spark and Python Interpreter
### What is this PR for?
While running a Notebook using shell, spark, python uses same user as which
zeppelin
GitHub user minahlee reopened a pull request:
https://github.com/apache/zeppelin/pull/1320
[ZEPPELIN-1287][branch-0.6] No need to call print to display output in
PythonInterpreter
### What is this PR for?
Implement #1278 to merge branch-0.6
### What type of PR is it?
Github user minahlee closed the pull request at:
https://github.com/apache/zeppelin/pull/1320
---
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 minahlee opened a pull request:
https://github.com/apache/zeppelin/pull/1321
[BUILD][HOTFIX] Add -DskipTests property to reduce build time
### What is this PR for?
In `dev/publish_release.sh` there are two mvn build. Second build fails
with follow error:
```
Github user mwkang commented on the issue:
https://github.com/apache/zeppelin/pull/1248
@bzz Thanks for your review. I rebase on to master and force push.
---
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 bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1304
@corneadoug thank you for explaining!
So we are talking about WS API to fetch full notebook state from the
history by it's revision? Wich on client-side looks like
Github user minahlee commented on the issue:
https://github.com/apache/zeppelin/pull/1294
Merge if there is 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 have this feature
GitHub user minahlee reopened a pull request:
https://github.com/apache/zeppelin/pull/1320
[ZEPPELIN-1287][branch-0.6] No need to call print to display output in
PythonInterpreter
### What is this PR for?
Implement #1278 to merge branch-0.6
### What type of PR is it?
Github user minahlee commented on the issue:
https://github.com/apache/zeppelin/pull/1264
Merge if there is 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 have this feature
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1248
This looks like an issue fixed in master 10h ago:
```
[31m- should provide onclick method *** FAILED ***[0m
[31m The code passed to eventually never returned normally. Attempted 1
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1320
@minahlee I think we also need to set appropriate "fix for" versions in
JIRA before merging #1278 otherwise it will be very hard for you, as release
manager to figure out changelog and attributions
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1301
Thank you for explanation! Makes sense.
Looks great to me.
May be it's worth to `git rebase master` as CI seems to be recently fixed.
---
If your project is set up for it, you can
Github user minahlee commented on the issue:
https://github.com/apache/zeppelin/pull/1320
\cc @zjffdu 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 minahlee opened a pull request:
https://github.com/apache/zeppelin/pull/1320
[ZEPPELIN-1287][branch-0.6] No need to call print to display output in
PythonInterpreter
### What is this PR for?
Implement #1278 to merge branch-0.6
### What type of PR is it?
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1257
@astroshim your changes look awesome to me!
There is one more improvement on Java side noted above, other than that -
looks good to merge.
---
If your project is set up for it, you can
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1193
@bzz I added log and tested. Thank you for taking care of 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
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1319
Good catch, LGTM!
CI failure looks unrelated.
---
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 astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1318
Spark2.0 & hadoop2.3 is working well.
---
If your project is set up for it,
GitHub user r-kamath opened a pull request:
https://github.com/apache/zeppelin/pull/1319
ZEPPELIN-1319 Use absolute path for ssl truststore and keystore when
available
### What is this PR for?
Use absolute path for ssl truststore and keystore when available
### What
Renjith Kamath created ZEPPELIN-1319:
Summary: Use absolute path for ssl truststore and keystore when
available
Key: ZEPPELIN-1319
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1319
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1193
Looks great to me, modulo the timeout logging issue noted about.
@astroshim plz ping when it's addressed and I'll be happy to merge it.
---
If your project is set up for it, you can reply to
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1168
Got it. Let's may be change PR title to WIP or even may be close it for now
but keep the branch and create a dedicated JIRA issue and link this work there?
It's a bigger effort that we
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1311
Thank you for prompt review!
Merging _to master_ if there is no further discussion
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1318
Do you know what version of spark is popular? I will test 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 zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1265
@jongyoul Does that mean the login user is the process owner ? Because it
matters for security reason.
e.g.
* For spark interpreter, it would be better to launch the yarn app as the
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1265
@jongyoul this looks very interesting! Could you plz help me to understand
- does this changes mean for Zeepelin to run a new separate interpreter process
for every user and schedulle only his jobs
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1310
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/1318
It's hard to say - I think one approach would be latest (spark 2.0 & Hadoop
2.7); another approach would be the most popular ones
---
If your project is set up for it, you can reply to
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1278
---
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/1303
---
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 cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1218
@bzz Okay!
---
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,
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1210
@mwpenny latest changes I promise haha
If you resize the paragraph to the smallest height allowed, the popup is
crushed and unusable, however there is plenty of space on top and bottom
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1314
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/1316
It would probably be a good idea to have a click-through terms of service.
Should we also display the zeppelin version?
---
If your project is set up for it, you can reply to this email
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1310
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 asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1317
---
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 jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1283
I've a few comment on your comments. Please check 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
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1317
Merge it into master and branch-0.6 as a hotfix
---
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 prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1315
Thank you @rconline for taking care of this. 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
Github user qinzl1 commented on the issue:
https://github.com/apache/zeppelin/pull/681
thanks @AhyoungRyu
---
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
56 matches
Mail list logo
