Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1395
Merging if there is 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 not have this
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1363
Let's try to rebase this one, and review 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
Semet created ZEPPELIN-1419:
---
Summary: PySpark dependencies support
Key: ZEPPELIN-1419
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1419
Project: Zeppelin
Issue Type: Improvement
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1334
@mfelgamal to address 1-2 can you please try to update `.travis.yml`: `-pl
\!beam` -> `-pl !beam` ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1380
---
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 tae-jun closed the pull request at:
https://github.com/apache/zeppelin/pull/1381
---
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/1395
@corneadoug
rebase is done.
ci is green!
Thank you.
---
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 zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1333
@Leemoonsoo @bzz I just fix the unit test. The root cause is that
`HeliumApplicationFactoryTest` will also register these interpreters. And all
these unit tests are in the same JVM. So I change
GitHub user zjffdu opened a pull request:
https://github.com/apache/zeppelin/pull/1413
[MINOR] Format Fix for InterpreterResultTest.java
### What is this PR for?
Java code style format fix. Seems lots of tabs are in the source code
### What type of PR is it?
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1413
@Leemoonsoo Please help 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
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1334
Looks great to me, thank you @mfelgamal !
I think it's ready to be merged.
The only minor thing that looks a bit off - re-formatted `pom.xml` is not
consistent with the other
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1265
@jongyoul Yes I think hiding "per user" make sense, and it can be a fair
assumption if user == "anonymous" then shiro is not enabled.
---
If your project is set up for it, you can reply
Github user minahlee commented on the issue:
https://github.com/apache/zeppelin/pull/1381
CI is green now. Shall we merge this guy?
---
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 lobamba opened a pull request:
https://github.com/apache/zeppelin/pull/1414
filter applied to graph
### What is this PR for?
We were looking for a Business Intelligence tools that allow to make data
analysis with nice charting.
We decided to use zeppelin that
Github user mfelgamal commented on the issue:
https://github.com/apache/zeppelin/pull/1334
@bzz the changes are done, could you take a look at pom file and 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
Github user kavinkumarks commented on the issue:
https://github.com/apache/zeppelin/pull/1408
Could someone please review this?
Thanks,
Kavin
MailTo: kavin.ku...@imaginea.com
---
If your project is set up for it, you can reply to this email and have your
reply appear
GitHub user minahlee opened a pull request:
https://github.com/apache/zeppelin/pull/1415
[ZEPPELIN-1026] set syntax highlight based on default bound interpreter
### What is this PR for?
This is complete work of #1148. Comments and tasks on #1148 has been
handled in this PR.
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1333
Great work @zjffdu!
Looks good to me!
---
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/1381
Let's merge!
---
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 Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1400
@lresende In the [issue
description](https://issues.apache.org/jira/browse/ZEPPELIN-1407), your build
command used `-Dscala-2.11` when you get those errors.
I could reproduce the
Github user doanduyhai commented on the issue:
https://github.com/apache/zeppelin/pull/1369
@astroshim @AhyoungRyu
Ok I've found the issue, it's my bad:
```javascript
for (var setting = 0; setting < $scope.interpreterSettings.length;
setting++) {
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1358
@mikhaildubkov `dev` doesn't exists on 0.6.x so you should use `master`
branch for this.
Thanks.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1395
---
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 mikhaildubkov commented on the issue:
https://github.com/apache/zeppelin/pull/1358
@astroshim ,
Once I checkout branch-0,6 I'm unable to build project due to compilation
error:
[ERROR] Failed to execute goal
Github user mikhaildubkov commented on the issue:
https://github.com/apache/zeppelin/pull/1358
@astroshim i guess it would be better just replace
ZeppelinDevServer.DEFAULT_TEST_INTERPRETER_PORT by its int value for branch-0.6
to avoid necessary change for project build.
---
If your
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1400
But unfortunately this wasn't what maven was enforcing, and Scala 2.11
build was failing when -PScala2.11 was being used, and when invoking
dependency:tree with -Pscala2.11 there were few
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1404
Thanks @zjffdu for the contribution. Actually, we do have some tests for
pyspark already.
Please see
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1406
---
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 corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1412
@AhyoungRyu Could you do a small typo/style 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 project does not
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1414
Thanks @lobamba for the contribution.
It's interesting feature!
It'll be great if we can have more feedbacks and opinions here from the
people, since this kind of feature has been
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1400
I'm sorry my comment is bit late. code is already been merged.
But let my write it for the records
Because of all our documents and scripts uses `-Pscala-2.xx` instead of
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1400
Done. master and branch-0.6 - 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
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1400
@lresende You can see followings from
http://maven.apache.org/guides/introduction/introduction-to-profiles.html.
```
All profiles that are active by default are automatically
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1400
---
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 lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1400
BTW, the properties on the profile activation, only enables the "default"
to be activated by default, so mvn clean install will not have properties
defined, so will start Scala 2.10...
---
If
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1404
could you kick off CI again? Let's merge this after
---
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 lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1400
@Leemoonsoo The issue wasn't about -P versus -D, but that the Scala 2.10
was with activation true by default, so even when you did only -Pscala2.11 the
Scala 2.10 profile was being activated.
GitHub user rfilmyer opened a pull request:
https://github.com/apache/zeppelin/pull/1416
Rewrite of "Quick Start" page.
### 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 -
Prasad Wagle created ZEPPELIN-1420:
--
Summary: java.util.ConcurrentModificationException caused by
calling remove inside foreach loop
Key: ZEPPELIN-1420
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1420
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1400
@felixcheung @Leemoonsoo @bzz Any more comments here ? Should we merge this
to 0.6 branch and master, as it's kind blocking to 2.11
---
If your project is set up for it, you can reply to this
Hi ,
Is there ant doc on design and implementation of Zeppelin. ? If it is can
any body please share ?
--
_
The information contained in this communication is intended solely for the
use of the individual or entity to whom it is
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1404
I tested this branch with given example, but it doesn't work for me.
On my machine, it hangs on `sqlContext.createDataFrame()` and end up with
errors like
```
kqueue: Too many
Github user khalidhuseynov commented on the issue:
https://github.com/apache/zeppelin/pull/1393
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 bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1334
CI is still failing.
Sorry for confusion, after a bit more thinking it looks like simplest way
here actually will be - to follow the same convention as with any other
interpreters, like
Github user khalidhuseynov commented on the issue:
https://github.com/apache/zeppelin/pull/1330
@mwkang could you 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 this feature
GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/1418
[gh-pages][ZEPPELIN-990] Add header anchor to gh-pages branch
### What is this PR for?
I applied header anchor to Zeppelin's docs website with #995 . It would be
good if `gh-pages` also
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1359
ping
---
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 corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1417
Tested, its also the only link that was not relative.
Merging if there is no more discussions
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1416
Hi @rfilmyer, thanks for your first contribution to Zeppelin! I've just
looked through the changes, definitely better. So LGTM I think ð
Since this change is just for
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1381
Tested on HDP2.5, on executing both spark and pyspark `sc.version` prints
`res0: String = 2.0.0.2.5.0.0-1245` and works as expected.
LGTM
---
If your project is set up for it, you can
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1417
@minahlee Please help 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
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1412
Fixed, Merging if there is 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 not have
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1417
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 khalidhuseynov commented on the issue:
https://github.com/apache/zeppelin/pull/1408
@kavinkumarks thanks for contribution. the idea of propagating error to the
user is a good one and definitely improves users experience. However, in your
implementation you basically
54 matches
Mail list logo
