Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1624
Merge to master if there're 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
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1657
Re-triggered CI and failure is irrelevant to this change.
Merge if there're no more comments.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1652
Merge to master if there're 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 project does not have this
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1645
Merge 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 not have this
Github user felizbear commented on the issue:
https://github.com/apache/zeppelin/pull/1659
@1ambda great analysis!
> Basically, we use node as a tool. not the runtime
This makes a lot of sense
---
If your project is set up for it, you can reply to this email and
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1659
@bzz Thanks for review! Things you pointed out are very important. So I'v
done some research about node and npm
Github user felizbear commented on the issue:
https://github.com/apache/zeppelin/pull/1659
I don't really have a strong opinion about node / npm versions. @bzz what's
the reasoning behind consolidating versions with other apache projects?
---
If your project is set up for it, you
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1639
Regarding to
- selecting proper version of node and npm
- centeralizing bulild tasks through npm scripts section
are being discussed in #1659. It would be helpful to give a
Github user felizbear commented on the issue:
https://github.com/apache/zeppelin/pull/1639
@1ambda wow GREAT WORK! Thanks a lot for your effort!
---
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 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1659
rebased interactively not to contain the same commits in #1639
---
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/1659
rebased
---
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 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1639
@bzz I will do that 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
enabled and
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1659
@1ambda great effort!
As mentioned in #1639 - could you please re-purpose (interactive rebase,
basically) this PR to contain only CI improvements?
One question on Node version
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1639
@1ambda great job!
Could you please re-purpose (interactive rebase, basically) #1639 to
contain only CI improvements, so it does not include anything from this PR?
Then we can
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1639
Short Summary of #1659
1. it seems that travis only accepts `.mavenrc`
2. even with MAVEN_OPTIONS, maven-assembly-plugins caused OOM error, so
update it to 3.0.0 (usually
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@mfelgamal
First of all, I really appreciate this PR. This definitely helps users to
install and start zeppelin in one-command.
As you replied, you have automatically built
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1653
merge to master if there're 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
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1625
---
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/1605
@minahlee Thanks for the update and unittest.
LGTM and merge to master if there're no further comments.
---
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/1655
Looks good to me!
Merge to master if there're 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.
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1648
Great work @1ambda !!
LGTM and merge to master if there's 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
GitHub user 1ambda reopened a pull request:
https://github.com/apache/zeppelin/pull/1659
CI TEST for PR #1639
CI TEST for PR #1639
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/1ambda/zeppelin pr/1639
Alternatively you can
Github user 1ambda closed the pull request at:
https://github.com/apache/zeppelin/pull/1659
---
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 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1657
an dependencies error
```
// https://api.travis-ci.org/jobs/177097181/log.txt?deansi=true
[INFO] Zeppelin ... FAILURE [
0.279 s]
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1648
@Leemoonsoo @bzz
I think this can help others to pass CI faster. Could you review this PR?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user 1ambda closed the pull request at:
https://github.com/apache/zeppelin/pull/1659
---
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 1ambda reopened a pull request:
https://github.com/apache/zeppelin/pull/1659
CI TEST for PR #1639
CI TEST for PR #1639
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/1ambda/zeppelin pr/1639
Alternatively you can
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1659
```
// https://api.travis-ci.org/jobs/177226860/log.txt?deansi=true
[INFO] Zeppelin: Server ... SUCCESS [
15.562 s]
[INFO] Zeppelin: Packaging
Github user tae-jun closed the pull request at:
https://github.com/apache/zeppelin/pull/1630
---
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 reopened a pull request:
https://github.com/apache/zeppelin/pull/1630
[ZEPPELIN-1629] Enable renaming folder from the main page
### What is this PR for?
This PR will enable renaming folder from the main page.
I wrote some codes. Hope this PR is the
Github user tae-jun commented on the issue:
https://github.com/apache/zeppelin/pull/1630
@AhyoungRyu Thanks for your kind review. I appreciate it.
Actually, I didn't test with Shiro ^^; and didn't know what `op` parameter
means. So thanks very much.
I changed
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1339
CI is green now, so ready for review.
I updated related docs again based on #1615 and @tae-jun 's feedback as
well.
@bzz Could you take a look this again?
As I mentioned in
Github user minahlee commented on the issue:
https://github.com/apache/zeppelin/pull/1605
@bzz @Leemoonsoo Ready 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
GitHub user AhyoungRyu reopened a pull request:
https://github.com/apache/zeppelin/pull/1339
[ZEPPELIN-1332] Remove spark-dependencies & suggest new way
### What is this PR for?
Currently, Zeppelin's embedded Spark is located under `interpreter/spark/`.
For whom **builds
Github user AhyoungRyu closed the pull request at:
https://github.com/apache/zeppelin/pull/1339
---
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
35 matches
Mail list logo
