You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by astroshim <gi...@git.apache.org> on 2016/07/25 16:00:10 UTC
[GitHub] zeppelin pull request #1227: [ZEPPELIN-1198][Spark Standalone] Documents for...
GitHub user astroshim opened a pull request:
https://github.com/apache/zeppelin/pull/1227
[ZEPPELIN-1198][Spark Standalone] Documents for running zeppelin on production environments.
### What is this PR for?
This PR is for documentation for running zeppelin on production environments.
### What type of PR is it?
Documentation
### Todos
- [x] Spark Standalone
- [ ] Spark on Mesos
- [ ] Spark on YARN
- [ ] CDH
- [ ] EMR
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1198
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/astroshim/zeppelin ZEPPELIN-1198/standalone
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1227.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1227
----
commit 83fdef6e2b6eec8280b566c33a25ee4de2946c7f
Author: astroshim <hs...@nflabs.com>
Date: 2016-07-25T15:43:59Z
doc for spark standalone
----
---
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 enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin issue #1227: [ZEPPELIN-1198][Spark Standalone] Documents for runnin...
Posted by AhyoungRyu <gi...@git.apache.org>.
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1227
CI failure with below error
```
Summary
-------
Generated at: 2016-07-25T16:46:38+00:00
Notes: 3
Binaries: 152
Archives: 0
Standards: 108
Apache Licensed: 106
Generated Documents: 0
JavaDocs are generated and so license header is optional
Generated files do not required license headers
2 Unknown Licenses
*******************************
Unapproved licenses:
scripts/docker/spark-cluster-managers/spark_standalone/Dockerfile
scripts/docker/spark-cluster-managers/spark_standalone/entrypoint.sh
```
It will be gone if you add apache license header to each docker files :)
---
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 enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin issue #1227: [ZEPPELIN-1198][Spark Standalone] Documents for runnin...
Posted by bzz <gi...@git.apache.org>.
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1227
Added fix version and assigner to JIRA
---
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 enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin pull request #1227: [ZEPPELIN-1198][Spark Standalone] Documents for...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1227
---
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 enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin issue #1227: [ZEPPELIN-1198][Spark Standalone] Documents for runnin...
Posted by bzz <gi...@git.apache.org>.
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1227
Looks great to me! Merging if there is no further discussion.
> Does this needs documentation? no
I think it does ;)
---
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 enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin issue #1227: [ZEPPELIN-1198][Spark Standalone] Documents for runnin...
Posted by astroshim <gi...@git.apache.org>.
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1227
@AhyoungRyu Thank you for review this. I will fix them.
---
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 enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin issue #1227: [ZEPPELIN-1198][Spark Standalone] Documents for runnin...
Posted by astroshim <gi...@git.apache.org>.
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1227
@bzz 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 the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin issue #1227: [ZEPPELIN-1198][Spark Standalone] Documents for runnin...
Posted by AhyoungRyu <gi...@git.apache.org>.
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1227
@astroshim Cool! Is this PR only for Spark standalone mode? If so, why don't you edit TODO list?
---
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 enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---