### What is this PR for?
[ZEPPELIN-2491] fix: Bump spell package version too
### What type of PR is it?
[Bug Fix]
### Todos
NONE
### What is the Jira issue?
[ZEPPELIN-2491](https://issues.apache.org/jira/browse/ZEPPELIN-2491)
### How should this be tested?
1. ` ./dev/change_zeppelin_version.sh 0.8.0-SNAPSHOT 0.8.0`
2. Check `/zeppelin-web/src/app/spell/package.json`
### Screenshots (if appropriate)
NONE
### Questions:
* Does the licenses files need update? - NO
* Is there breaking changes for older versions? - NO
* Does this needs documentation? - NO
Author: 1ambda <1amb4a@gmail.com>
Closes#2315 from 1ambda/ZEPPELIN-2491/bump-spell-package-version-too and squashes the following commits:
20a8fae [1ambda] fix: Bump spell package version too
### What is this PR for?
Use single `Dockerfile` for each release since [apache infra uses tag pushes](https://issues.apache.org/jira/browse/INFRA-12781) to build an image.
- https://issues.apache.org/jira/browse/INFRA-12781
After release process finishes, dockerhub will build using the pushed tag.
### What type of PR is it?
[Improvement]
### What is the Jira issue?
[ZEPPELIN-2492](https://issues.apache.org/jira/browse/ZEPPELIN-2492)
### How should this be tested?
1. `./dev/change_zeppelin_version.sh 0.8.0-SNAPSHOT 0.7.1`
2. Check that version is properly set: `vi scrtips/docker/zeppelin/bin/Dockerfile`
3. Build docker image `cd scripts/docker/zeppelin/bin; docker build -t zeppelin:0.7.1 ./`
4. Run the image: `docker run -p 8080:8080 --rm --name zeppelin zeppelin:0.7.1`
### Screenshots (if appropriate)
NONE
### Questions:
* Does the licenses files need update? - NO
* Is there breaking changes for older versions? - NO
* Does this needs documentation? - NO
Author: 1ambda <1amb4a@gmail.com>
Closes#2318 from 1ambda/ZEPPELIN-2492/use-single-dockerfile-for-each-tag and squashes the following commits:
483bec3 [1ambda] docs: Update README for Dockerfile
5826c8c [1ambda] fix: Use single dockerfile for tag push
### What is this PR for?
Currently users who build Zeppelin from source need to include `-Pyarn` build profile to enable Yarn for embedded local Spark. This PR is to remove `-Pyarn` and make Yarn related libraries can be automatically downloaded without the profile during build time.
### What type of PR is it?
just removed Yarn build profile in `spark-dependencies/pom.xml`
### What is the Jira issue?
[ZEPPELIN-2373](https://issues.apache.org/jira/browse/ZEPPELIN-2373)
### How should this be tested?
1. apply this patch and build Zeppelin with below command
```
mvn clean package -DskipTests -pl 'zeppelin-server, spark-dependencies, spark' --am
```
2. check `spark-yarn_${scala.binary.version}.jar` is downloaded(or included) during build time
```
[INFO] Including org.apache.spark:spark-yarn_2.10🫙2.1.0 in the shaded jar.
```
In current master, the above line won't be shown if you don't use `-Pyarn` build profile. But with this patch, it will be shown without the profile.
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
Author: AhyoungRyu <fbdkdud93@hanmail.net>
Closes#2232 from AhyoungRyu/ZEPPELIN-2373/includeYarnByDefault and squashes the following commits:
59eb2b5 [AhyoungRyu] Remove -Pyarn build profile
### What is this PR for?
Currently users who build Zeppelin from source need to include `-Psparkr` to use `%r` with embedded local Spark. But it's quite inconvenient to write this build profile every time we build i think. So I removed `-Psparkr` and make `r` related libraries automatically downloaded when we build Zeppelin like I did #2213
### What type of PR is it?
Improvement
### Todos
* [x] - remove the rest of `-Psparkr` build profile in `dev/create_release.sh`, `dev/publish_release.sh`, and `docs/install/build.md` after #2213 merged
### What is the Jira issue?
[ZEPPELIN-2341](https://issues.apache.org/jira/browse/ZEPPELIN-2341)
### How should this be tested?
1. Apply this patch
2. Build source with below command
```
mvn clean package -DskipTests -pl 'zeppelin-interpreter, zeppelin-zengine, zeppelin-server, zeppelin-display, spark, spark-dependencies'
```
Aftr this step, there will be `R` dir under `ZEPPELIN_HOME/interpreter/spark`. Before this PR, only `dep` dir and `zeppelin-spark_2.10-0.8.0-SNAPSHOT.jar` is generated without `-Psparkr` build profile.
4. Restart Zeppelin. To make sure, run R tutorial note under `Zeppelin Tutorial` folder
It should be run successfully without any error
### Screenshots (if appropriate)
If we build without `-Psparkr`
- before : R related properties are not activated by default in Spark interpreter
- after
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
Author: AhyoungRyu <fbdkdud93@hanmail.net>
Author: Ahyoung Ryu <ahyoungryu@apache.org>
Closes#2215 from AhyoungRyu/ZEPPELIN-2341/includeSparkRByDefault and squashes the following commits:
8db18cc [AhyoungRyu] Remove the rest of '-Psparkr' in docs & sh files
f891fd4 [Ahyoung Ryu] Merge branch 'master' into ZEPPELIN-2341/includeSparkRByDefault
445be3e [AhyoungRyu] Add SPARKR env to check each test case need to download r dep or not
67af02a [AhyoungRyu] Remove -PsparkR in travis file
a00466c [AhyoungRyu] Remove sparkr build profile in pom files
### What is this PR for?
Currently users who build Zeppelin from source need to include `-Ppyspark` to use `%pyspark` with embedded local Spark. But it's quite inconvenient to write this build profile every time we build i think. So I removed `-Ppyspark` and make pyspark related libraries automatically downloaded when we build Zeppelin.
### What type of PR is it?
Improvement
### Todos
* [x] - remove the rest of `-Ppyspark` build profile in `dev/create_release.sh`, `dev/publish_release.sh`, and `docs/install/build.md` after getting feedback
### What is the Jira issue?
[ZEPPELIN-2298](https://issues.apache.org/jira/browse/ZEPPELIN-2298)
### How should this be tested?
1. Apply this patch
2. Build source with below command
```
mvn clean package -DskipTests -pl 'zeppelin-interpreter, zeppelin-zengine, zeppelin-server, zeppelin-display, spark, spark-dependencies'
```
Aftr this step, there will be `pyspark` dir under `ZEPPELIN_HOME/interpreter/spark`. Before this PR, only `dep` dir and `zeppelin-spark_2.10-0.8.0-SNAPSHOT.jar` is generated without `-Ppyspark` build profile.
4. Restart Zeppelin. To make sure, run any python code e.g.
```
%pyspark
print("Hello "+z.input("name"))
```
It should be run successfully without any error
### Screenshots (if appropriate)
tl;dr Without `-Ppyspark` profile
- Before
<img width="856" alt="screen shot 2017-04-02 at 2 50 57 pm" src="https://cloud.githubusercontent.com/assets/10060731/24584778/0e8ec6b0-17b4-11e7-9f0d-f2599fd7bd63.png">
- After
<img width="893" alt="screen shot 2017-04-02 at 2 28 21 pm" src="https://cloud.githubusercontent.com/assets/10060731/24584779/10b7ed68-17b4-11e7-90d4-aa95eb9bba2d.png">
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
I want to include `SparkR` by default(= remove `-PsparkR` build profile) like this as a next step. I want to ask how Zeppelin community think about this.
Author: AhyoungRyu <fbdkdud93@hanmail.net>
Closes#2213 from AhyoungRyu/ZEPPELIN-2298/includePysparkByDefault and squashes the following commits:
f7bcf06 [AhyoungRyu] Remove -Ppyspark in virtual_machine.md
458ac02 [AhyoungRyu] Remove the rest of -Ppyspark in blind side of Zeppelin :)
cee1e87 [AhyoungRyu] Change py4j.version -> python.py4j.version
ce43158 [AhyoungRyu] Change py4j.version -> spark.py4j.version
fa4fb36 [AhyoungRyu] Remove the rest of -Ppyspark
30aac81 [AhyoungRyu] Remove -Ppyspark build flag
### What is this PR for?
Fix wrong variable name in tag script
### What type of PR is it?
Hot Fix
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
Author: Mina Lee <minalee@apache.org>
Closes#2171 from minahlee/hotfix/tag-script and squashes the following commits:
d84a72c1 [Mina Lee] FIx tag script wrong variable nome
### What is this PR for?
Simple script that deploy Apache Zeppelin artifact to snapshot repository
### What type of PR is it?
[Improvement ]
### What is the Jira issue?
* [ZEPPELIN-2001](https://issues.apache.org/jira/browse/ZEPPELIN-2001)
### How should this be tested?
Simply run `./dev/publish_release.sh 0.7.0-SNAPSHOT branch-0.7`
### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? YES
Author: Anthony Corbacho <corbacho.anthony@gmail.com>
Closes#1934 from anthonycorbacho/ZEPPELIN-2001 and squashes the following commits:
8ada9817 [Anthony Corbacho] Added beam and maven.repo.local to snapshot
7367653c [Anthony Corbacho] Fix typo
f5fad908 [Anthony Corbacho] Publish SNAPSHOT artifact
1be49dad [Anthony Corbacho] Add flag for snapshot publishing
### What is this PR for?
pom variables such as `${scala.version}` are not replaced to value when you do `mvn install`.
This makes leaf poms to look for this value in parent pom, which is always `2.10.5` for `${scala.version}` and it causes scala library dependency conflict. For example, zeppelin-flink_2.11 will have scala 2.10.5 as dependency.
This PR fixes this problem by using maven flatten plugin.
### What type of PR is it?
Bug Fix
### What is the Jira issue?
[ZEPPELIN-2139](https://issues.apache.org/jira/browse/ZEPPELIN-2139)
### How should this be tested?
```
$ ./dev/change_scala_version.sh 2.11
$ mvn clean install -pl 'zeppelin-server,zeppelin-zengine,zeppelin-interpreter,flink' -am -DskipRat -DskipTests -Pscala-2.11
```
Open `~/.m2/repository/org/apache/zeppelin/zeppelin-flink_2.11/0.8.0-SNAPSHOT/zeppelin-flink_2.11-0.8.0-SNAPSHOT.pom` file and see if scala related libraries dependency version is set to 2.11.7
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
Author: Mina Lee <minalee@apache.org>
Closes#2059 from minahlee/ZEPPELIN-2139 and squashes the following commits:
62d852a [Mina Lee] Change <scala.version> property in parent pom file
489c843 [Mina Lee] Use maven flatten plugin to make pom.xml variables to be replaced by value
783c014 [Mina Lee] Fix indentation and add default properties to be used in flattened-pom
### What is this PR for?
Fix failure of script execution on Windows 10
### What type of PR is it?
[Bug Fix]
### Todos
### What is the Jira issue?
[ZEPPELIN-1781](https://issues.apache.org/jira/browse/ZEPPELIN-1781)
### How should this be tested?
Run 'test_zeppelin_pr.py' on Windows 10.
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No
Author: Myoungdo Park <cuspymd@gmail.com>
Closes#1742 from cuspymd/test-pr and squashes the following commits:
c468212 [Myoungdo Park] Make it runnable on Python 2/3
eb4b567 [Myoungdo Park] Fix failure of script execution on Windows 10
### What is this PR for?
Removing docker build and push from release script.
Docker managed by community will be supported sooner or later through https://hub.docker.com/r/apache/ or official docker hub repository, and either way doesn't need push from release script.
### What type of PR is it?
Build
### What is the Jira issue?
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
Author: Mina Lee <minalee@apache.org>
Closes#1926 from minahlee/remove_docker_build and squashes the following commits:
6ea789e [Mina Lee] Publish beam interpreter in maven central repo
3a9b64e [Mina Lee] Remove docker build
### What is this PR for?
It's my misunderstanding of `SPARK_VER` in travis. It is only used for downloading spark distribution. We need to specify spark profile explicitly for building with specific version of spark. This PR add new profile for spark 2.1 and fix the build issue with spark 2.1.0 because `SecurityManager` changes its constructor signature in spark 2.1
### What type of PR is it?
[Bug Fix ]
### Todos
* [ ] - Task
### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-1918
### How should this be tested?
Build with spark 2.1.0 and tested it manually as below screenshot.
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No
Author: Jeff Zhang <zjffdu@apache.org>
Closes#1880 from zjffdu/ZEPPELIN-1918 and squashes the following commits:
8f87459 [Jeff Zhang] update release script
34772e0 [Jeff Zhang] update build doc for spark 2.1
5efdb11 [Jeff Zhang] fix unit test and address comments
def502f [Jeff Zhang] ZEPPELIN-1918. Fix build with Spark 2.1.0
### What is this PR for?
* Change hadoop profile from `hadoop-2.4` to `hadoop-2.6`
* Use `SCALA_VERSION` variable instead of hardcoding
* Specify projects to be built for netinst package instead of excluding unnecessary projects.
### What type of PR is it?
Build
### What is the Jira issue?
### How should this be tested?
Outline the steps to test the PR here.
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
Author: Mina Lee <minalee@apache.org>
Closes#1890 from minahlee/update/release_script and squashes the following commits:
a97b5fe [Mina Lee] Remove one r interpreter profile as only one will take effect
1479d26 [Mina Lee] Use scala variable instead of hardcoding Specify project to build for net-inst package instead of adding exluding projects everytime zeppelin have new interpreter
da9080a [Mina Lee] Update hadoop profile from 2.4 to 2.6
### What is this PR for?
This PR is for making docker images for zeppelin releases. It contains a script for building image for each release. Another script is used for publishing images to zeppelin Dockerhub account.
This repo, https://github.com/mfelgamal/zeppelin-dockers, is a demonstration of this PR. It contains zeppelin-base image and an image for each zeppelin release.
### What type of PR is it?
[Feature]
### Todos
- Review Comments
- Documentation
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1386
### How should this be tested?
- run create_release script or publish_release script.
### Screenshots (if appropriate)
### Questions:
- Does the licenses files need update? no
- Is there breaking changes for older versions? no
- Does this needs documentation? yes
Author: mahmoudelgamal <mahmoudf.elgamal@gmail.com>
Author: mfelgamal <mahmoudf.elgamal@gmail.com>
Author: Mahmoud Elgamal <mahmoudf.elgamal@gmail.com>
Author: 1ambda <1amb4a@gmail.com>
Closes#1538 from mfelgamal/zeppelin-dockers and squashes the following commits:
cc8493f [Mahmoud Elgamal] Merge pull request #3 from 1ambda/fix/remove-startzeppelinsh
d48ecef [1ambda] fix: Remove start-zeppelin.sh
b64c680 [mahmoudelgamal] Remove gcc and g++ for decreasing the size
1f093d4 [mahmoudelgamal] Add script start-zeppelin to zeppelin-base
d2c744e [mahmoudelgamal] add scala to zeppelin-base
fd23970 [mahmoudelgamal] remove bash erorr message.
e1d4b77 [mahmoudelgamal] add R and python to zeppelin-base
e731cb4 [mahmoudelgamal] Add java-cacerts to zeppelin-base
e642309 [mahmoudelgamal] Add documentation and some modifications
231a414 [mahmoudelgamal] Add zeppelin-base image
ac06f3a [mahmoudelgamal] Make docker image for zeppelin release
48d0a01 [mfelgamal] Merge pull request #1 from apache/master
### What is this PR for?
While removing duplication of specifying build profile in #1321, build profile has been changed from `-Ppublish-distr` to `-Pbuild-distr`. We need to restore this change and use `-Ppublish-distr` profile to publish `*.javadoc.jar ` and `*.sources.jar`.
### What type of PR is it?
Hot Fix
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
Author: Mina Lee <minalee@apache.org>
Closes#1506 from minahlee/build_profile and squashes the following commits:
b84b371 [Mina Lee] Change build profile for distributing artifact to maven repository
### What is this PR for?
In `dev/publish_release.sh` there are two mvn build. Second build fails with follow error:
```
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (start-zeppelin) on project zeppelin-server: An Ant BuildException has occured: The directory /private/tmp/zeppelin-release/zeppelin/zeppelin-server/${zeppelin.daemon.package.base} does not exist
[ERROR] around Ant part ...<exec spawn="true" dir="${zeppelin.daemon.package.base}" executable="./zeppelin-daemon.sh">... 4:94 in /private/tmp/zeppelin-release/zeppelin/zeppelin-server/target/antrun/build-main.xml
```
This PR skip tests to fix this issue as hotfix. In addition, it will reduce build time
### What type of PR is it?
Build
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
Author: Mina Lee <minalee@apache.org>
Closes#1321 from minahlee/build_skipTests and squashes the following commits:
c1aa845 [Mina Lee] Add -DskipTests property to reduce build time
### What is this PR for?
Remove bigquery interpreter from netinst package
### What type of PR is it?
Build
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
Author: Mina Lee <minalee@apache.org>
Closes#1306 from minahlee/netinst/remove_bigquery and squashes the following commits:
0604840 [Mina Lee] Remove bigquery interpreter from netinst package
### What is this PR for?
- build distribution package with Spark 2.0 and Scala 2.11
- change travis profile to use spark 2.0 instead of 2.0.0-preview by removing `-Dspark.version=2.0.0-preview` property
- Change profile activation rule
* current way of profile activation is not proper for supporting more than three scala version
* -Pscala-2.11 activates both scala-2.10 and scala-2.11 profile without this patch
### What type of PR is it?
Build
### What is the Jira issue?
[ZEPPELIN-1256](https://issues.apache.org/jira/browse/ZEPPELIN-1256)
### How should this be tested?
**Before**
Run `mvn help:active-profiles -Pscala-2.11`:
```
Active Profiles for Project 'org.apache.zeppelin:zeppelin:pom:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-interpreter:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-zengine:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-display_2.11🫙0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin-display_2.11:0.7.0-SNAPSHOT)
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-spark-dependencies_2.11🫙0.7.0-SNAPSHOT':
The following profiles are active:
- spark-2.0 (source: org.apache.zeppelin:zeppelin-spark-dependencies_2.11:0.7.0-SNAPSHOT)
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-spark_2.11🫙0.7.0-SNAPSHOT':
The following profiles are active:
- exclude-sparkr (source: org.apache.zeppelin:zeppelin-spark_2.11:0.7.0-SNAPSHOT)
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-markdown:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-angular:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-shell:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-livy:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-hbase:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-postgresql:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-jdbc:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-file:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-flink_2.11🫙0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-ignite_2.11🫙0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-kylin:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-python:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-lens:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-cassandra_2.11🫙0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-elasticsearch:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-alluxio:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-web:war:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-server:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin-server:0.7.0-SNAPSHOT)
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-distribution:pom:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin-distribution:0.7.0-SNAPSHOT)
- scala-2.10 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
```
**After**
Run `mvn help:active-profiles -Dscala-2.11`:
```
Active Profiles for Project 'org.apache.zeppelin:zeppelin:pom:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-interpreter:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-zengine:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-display_2.11🫙0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin-display_2.11:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-spark-dependencies_2.11🫙0.7.0-SNAPSHOT':
The following profiles are active:
- spark-2.0 (source: org.apache.zeppelin:zeppelin-spark-dependencies_2.11:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-spark_2.11🫙0.7.0-SNAPSHOT':
The following profiles are active:
- exclude-sparkr (source: org.apache.zeppelin:zeppelin-spark_2.11:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-markdown:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-angular:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-shell:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-livy:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-hbase:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-postgresql:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-jdbc:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-file:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-flink_2.11🫙0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-ignite_2.11🫙0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-kylin:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-python:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-lens:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-cassandra_2.11🫙0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-elasticsearch:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-alluxio:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-web:war:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-server:jar:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin-server:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
Active Profiles for Project 'org.apache.zeppelin:zeppelin-distribution:pom:0.7.0-SNAPSHOT':
The following profiles are active:
- scala-2.11 (source: org.apache.zeppelin:zeppelin-distribution:0.7.0-SNAPSHOT)
- scala-2.11 (source: org.apache.zeppelin:zeppelin:0.7.0-SNAPSHOT)
```
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? yes (for scala 2.11 build)
Author: Mina Lee <minalee@apache.org>
Closes#1251 from minahlee/ZEPPELIN-1256 and squashes the following commits:
ff034c6 [Mina Lee] change scala-2.10 and scala-2.11 profile activation rule
99d91bf [Mina Lee] Update interpreter installation for the user who use Spark version <= 1.6.2
4ca3e7f [Mina Lee] Build distribution package with Spark 2.0 and Scala 2.11
### What is this PR for?
- Update publish_release.sh to publish scala 2.10 and scala 2.11 artifacts to maven repository.
- Set build spark version to 2.0
This PR supposed to work once #1186 and #1195 is merged
### What type of PR is it?
Improvement
### What is the Jira issue?
[ZEPPELIN-1180](https://issues.apache.org/jira/browse/ZEPPELIN-1180)
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
Author: Mina Lee <minalee@apache.org>
Closes#1209 from minahlee/ZEPPELIN-1180 and squashes the following commits:
40e5718 [Mina Lee] Use underscore as word separator in file name for consistency
0a91932 [Mina Lee] Include all module for scala 2.11 artifact build
c1d6439 [Mina Lee] publish 2.11 artifact to maven
a7918f0 [Mina Lee] Fix mod from 755 to 644
bca1af1 [Mina Lee] Fix indentation
### What is this PR for?
Now that we have support for both Scala 2.10 and 2.11 we need to append Scala version to the maven artifact id in order to properly publish artifacts for both Scala releases.
### What type of PR is it?
[Improvement]
### What is the Jira issue?
[ZEPPELIN-1179](https://issues.apache.org/jira/browse/ZEPPELIN-1179)
Author: Luciano Resende <lresende@apache.org>
Closes#1186 from lresende/scala-version and squashes the following commits:
27ec9fe [Luciano Resende] [ZEPPELIN-1179] Properly set scala version during builds
4594607 [Luciano Resende] [ZEPPELIN-1179] Append scala version to remaining maven artifacts
7bed3ec [Luciano Resende] [ZEPPELIN-1179] Append scala version to maven artifacts
### What is this PR for?
Maven artifact publish script fails to close staging repository programmatically because of the duplicate closing braces.
### What type of PR is it?
Bug Fix
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
Author: Mina Lee <minalee@apache.org>
Closes#1127 from minahlee/hotfix/removeDuplBrace and squashes the following commits:
608d648 [Mina Lee] Remove duplicate closing brace
### What is this PR for?
- Add sparkr, r profile to netinst release build
- Exit release_publish.sh in case creating staging repository fails
### What type of PR is it?
Hot Fix
### Questions:
* Does the licenses files need update?
* Is there breaking changes for older versions?
* Does this needs documentation?
Author: Mina Lee <minalee@apache.org>
Closes#1098 from minahlee/fix/release_script and squashes the following commits:
bf25d5b [Mina Lee] remove quote to make sed works properly
2fee082 [Mina Lee] Add sparkr, r profile to netinst binary package build
### What is this PR for?
Implementation of bin/install-interpreter.sh for netinst package which suggested in the [discussion](http://apache-zeppelin-users-incubating-mailing-list.75479.x6.nabble.com/Ask-opinion-regarding-0-6-0-release-package-tp3298p3314.html).
Some usages will be
```
# download all interpreters provided by Apache Zeppelin project
bin/install-interpreter.sh --all
# download an interpreter with name (for example markdown interpreter)
bin/install-interpreter.sh --name md
# download an (3rd party) interpreter with specific maven artifact name
bin/install-interpreter.sh --name md -t org.apache.zeppelin:zeppelin-markdown:0.6.0-SNAPSHOT
```
If it looks fine, i'll continue the work (refactor code, and add test)
### What type of PR is it?
Feature
### Todos
* [x] - working implementation
* [x] - refactor
* [x] - add test
### What is the Jira issue?
* Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/
* Put link here, and add [ZEPPELIN-*Jira number*] in PR title, eg. [ZEPPELIN-533]
### How should this be tested?
Outline the steps to test the PR here.
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update?
* Is there breaking changes for older versions?
* Does this needs documentation?
Author: Lee moon soo <moon@apache.org>
Author: AhyoungRyu <fbdkdud93@hanmail.net>
Closes#1042 from Leemoonsoo/netinst and squashes the following commits:
f81d16e [Lee moon soo] address mina's comment
049bc89 [Lee moon soo] Update docs
7307c67 [Lee moon soo] Merge remote-tracking branch 'AhyoungRyu/netinst-docs' into netinst
7e749ad [Lee moon soo] Address mina's comment
0eedd2a [AhyoungRyu] Address @minahlee feedback
13f2d04 [Lee moon soo] generate netinst package
03c664e [AhyoungRyu] Add a new line
5d0a971 [AhyoungRyu] Revert install.md to latest version
13899fb [AhyoungRyu] Reorganize interpreter installation docs
4c1f029 [Lee moon soo] Proxy support
9079580 [Lee moon soo] fix artifact name
1077296 [Lee moon soo] update test
aebca17 [Lee moon soo] Add docs
d547551 [Lee moon soo] Remove test entries
6ee06b8 [Lee moon soo] Make DependencyResolver in zeppelin-interpreter module not aware of ZEPPELIN_HOME
7b1b36a [Lee moon soo] update usage
49f0568 [Lee moon soo] Add conf/interpreter-list
1b558fd [Lee moon soo] update some text
ec7d152 [Lee moon soo] add tip
2c81a3f [Lee moon soo] update
78a7c52 [Lee moon soo] Refactor and add test
47f5706 [Lee moon soo] Install multiple interpreters at once
38e2556 [Lee moon soo] Initial implementation of install-interpreter.sh
### What is this PR for?
This PR is to automate release publish to maven repository.
We used to use maven-deploy-plugin and maven-release-plugin for release but somehow it didn't work well with Zeppelin so 0.5.5 and 0.5.6 haven't been published to maven repository.
Publishing release to maven repository will eventually help zeppelin to reduce binary package size by leading users to use Dynamic interpreter loading(#908).
Originally below modules were skipped for maven release
- all interpreters(except spark)
- zeppelin-display
- zeppelin-server
- zeppelin-distribution
on the other hand this pr will skip only:
- zeppelin-distribution
### What type of PR is it?
Infra
### Todos
- [x] Include SparkR/R interpreter in release
- [x] Create common_release.sh to remove build configuration duplication
- [x] Check curl networking failure
### What is the Jira issue?
[ZEPPELIN-986](https://issues.apache.org/jira/browse/ZEPPELIN-986)
### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? Yes, https://cwiki.apache.org/confluence/display/ZEPPELIN/Preparing+Zeppelin+Release will be updated accordingly once this pr is merged.
Author: Mina Lee <minalee@apache.org>
Closes#994 from minahlee/ZEPPELIN-986 and squashes the following commits:
b0e8e67 [Mina Lee] Revert "Add geode, scalding profile in maven artifact build"
cd4cbcd [Mina Lee] curl failure check
c0ea07c [Mina Lee] Fix wrong indentation
a88bc1d [Mina Lee] Add geode, scalding profile in maven artifact build
2cced61 [Mina Lee] Add r to binary package and maven build
903bc12 [Mina Lee] Move duplicate code to common_release.sh
a3eb676 [Mina Lee] Include zeppelin-server module in publish artifiact
48d338f [Mina Lee] Rollback mistakenly removed plugin
aafaf42 [Mina Lee] Follow google shell style guide
30dcc65 [Mina Lee] remove deploy plugin from pom since custom script will be used instead for deploy
cd1f08c [Mina Lee] Refactor create release script
e764f5f [Mina Lee] Add maven publish release script
### What is this PR for?
git repo infra have moved from incubator-zeppelin to zeppelin
### What type of PR is it?
Hot Fix
### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No
Author: Mina Lee <minalee@apache.org>
Closes#983 from minahlee/ZEPPELIN-980 and squashes the following commits:
7542c31 [Mina Lee] remove travis url after travis migration is done
3793b38 [Mina Lee] Move git repository from incubator-zeppelin to zeppelin
### What is this PR for?
Changed the regex to find a issue number from title. This doesn't change any code about Zeppelin, but this will effect helper script for committers
### What type of PR is it?
[Bug Fix]
### Todos
* [x] - Fixed the bug
### What is the Jira issue?
N/A
### How should this be tested?
```
>>> import re
>>> re.findall("ZEPPELIN-[0-9]{3,4}", "ZEPPELIN-123")
['ZEPPELIN-123']
>>> re.findall("ZEPPELIN-[0-9]{4,5}", "ZEPPELIN-123")
[]
>>> re.findall("ZEPPELIN-[0-9]{3,4,5}", "ZEPPELIN-123")
[]
>>> re.findall("ZEPPELIN-[0-9]{3}", "ZEPPELIN-123")
['ZEPPELIN-123']
>>> re.findall("ZEPPELIN-[0-9]{3,5}", "ZEPPELIN-123")
['ZEPPELIN-123']
>>> re.findall("ZEPPELIN-[0-9]{4,5}", "ZEPPELIN-123")
[]
>>> re.findall("ZEPPELIN-[0-9]{3,5}", "ZEPPELIN-123")
['ZEPPELIN-123']
```
### Screenshots (if appropriate)
N/A
### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No
Author: Jongyoul Lee <jongyoul@gmail.com>
Closes#936 from jongyoul/minor-find-issue-number-from-title and squashes the following commits:
63f37af [Jongyoul Lee] [MINOR] fixed logic to find issue number from title
c16117b [Jongyoul Lee] [MINOR] fixed logic to find issue number from title
### What is this PR for?
When using merge_zeppelin_pr.py utility the comment that shows up on issues.apache.org is wrong. The URL that prints is "pulls", it should be "pull"
It shows up as :
Issue resolved by pull request 874
https://github.com/apache/incubator-zeppelin/pulls/874
It should be :
Issue resolved by pull request 874
https://github.com/apache/incubator-zeppelin/pull/874
### What type of PR is it?
[Bug Fix]
### Todos
N/A
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-843
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
Author: Prabhjyot Singh <prabhjyotsingh@gmail.com>
Closes#879 from prabhjyotsingh/ZEPPELIN-843 and squashes the following commits:
189f468 [Prabhjyot Singh] fix : Comment showing up on issues.apache.org is wrong
Small update - jira package name has changed
Author: Felix Cheung <felixcheung_m@hotmail.com>
Closes#674 from felixcheung/mergescript and squashes the following commits:
384868b [Felix Cheung] update merge script
### What is this PR for?
Change embedded Spark dependency in binary package for the release from 1.5 to 1.6.
### What type of PR is it?
Improvement
### Todos
### Is there a relevant Jira issue?
### How should this be tested?
build package using dev/create_release.sh and run created package with default configuration. And see output of 'sc.version' if it is based on spark 1.6
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
Author: Lee moon soo <moon@apache.org>
Closes#618 from Leemoonsoo/create_release.sh and squashes the following commits:
dc4e2a3 [Lee moon soo] change build profile for binary package release from -Pspark-1.5 to -Pspark-1.6
This PR address https://issues.apache.org/jira/browse/ZEPPELIN-484.
We've got discussions recently about impasse of pullrequest and speeding up of accepting pullrequest.
This small utility can be used when reviewer want to test the pullrequest.
Usage is
```
dev/test.py [#PR]
```
for example
```
dev/test.py 500
```
will create local branch `pr500` and add remote repository of contribution, fetch and merge it for the test.
This script will help reduce small bit of time of reviewing.
Author: Lee moon soo <moon@apache.org>
Closes#513 from Leemoonsoo/ZEPPELIN-484 and squashes the following commits:
76f0ddf [Lee moon soo] Add description
e8a0e8e [Lee moon soo] Rename
1adb356 [Lee moon soo] Handle non-ascii char
39d81ba [Lee moon soo] Add utility for pr test
#407 addressed https://issues.apache.org/jira/browse/ZEPPELIN-406 and merged into branch-0.5.5
This PR applies it to the master branch
Author: Lee moon soo <moon@apache.org>
Closes#424 from Leemoonsoo/ZEPPELIN-406-master and squashes the following commits:
64b6550 [Lee moon soo] Add apache header and inline json message example into doc
ba72645 [Lee moon soo] ZEPPELIN-406 Handle license issue found in 0.5.5-incubating rc2
https://issues.apache.org/jira/browse/ZEPPELIN-397
Activate spark-1.5 and hadoop-2.4 by default
That'll enable use sc.textFile("s3...") with default configuration without specify SPARK_HOME.
Author: Lee moon soo <moon@apache.org>
This patch had conflicts when merged, resolved by
Committer: Lee moon soo <moon@apache.org>
Closes#397 from Leemoonsoo/ZEPPELIN-397 and squashes the following commits:
9855dde [Lee moon soo] Activate spark-1.5 and hadoop-2.4 by default
https://issues.apache.org/jira/browse/ZEPPELIN-396
Add -Ppyspark to enable pyspark in default configuration (without SPARK_HOME specified).
Author: Lee moon soo <moon@apache.org>
Closes#396 from Leemoonsoo/ZEPPELIN-396 and squashes the following commits:
4e599af [Lee moon soo] Add -Pypspark profile for release binary
This PR addresses https://issues.apache.org/jira/browse/ZEPPELIN-366
This patch creates single binary package instead of multiple binary package with different version of Spark / Hadoop combinations.
Also it's removing redundant directory structure from it's tar archive.
Author: Lee moon soo <moon@apache.org>
Closes#373 from Leemoonsoo/ZEPPELIN-366 and squashes the following commits:
366bbf4 [Lee moon soo] Create a single binary package with default build flags. Remove redundant directory structure in binary package.
Zeppelin currently embeds all spark dependencies under interpreter/spark and loading them on runtime.
Which is useful because of user can try Zeppelin + Spark with local mode without installation and configuration of spark.
However, when user has existing spark and hadoop installation, it'll be really helpful to just pointing them instead of build zeppelin with specific version of spark and hadoop combination.
This PR implements ability to use external spark and hadoop installation, by doing
* spark-dependencies module packages spark/hadoop dependencies under interpreter/spark/dep, to support local mode (current behavior)
* When SPARK_HOME and HADOOP_HOME is defined, bin/interpreter.sh exclude interpreter/spark/dep from classpath and include system installed spark and hadoop into the classpath.
This patch makes Zeppelin binary independent from spark version. Once Zeppelin is been built, SPARK_HOME can point any version of spark.
Author: Lee moon soo <moon@apache.org>
Closes#244 from Leemoonsoo/spark_provided and squashes the following commits:
654c378 [Lee moon soo] use consistant, simpler expressions
57b3f96 [Lee moon soo] Add comment
eb4ec09 [Lee moon soo] fix reading spark-*.conf file
bacfd93 [Lee moon soo] Update readme
3a88c77 [Lee moon soo] Test use explicitly %spark
5a17d9c [Lee moon soo] Call sqlContext.sql using reflection
615c395 [Lee moon soo] get correct method
0c28561 [Lee moon soo] call listenerBus() using reflection
62b8c45 [Lee moon soo] Print all logs
5edb6fd [Lee moon soo] Use reflection to call addListener
af7a925 [Lee moon soo] add pyspark flag
5f8a734 [Lee moon soo] test -> package
a0150cf [Lee moon soo] not use travis-install for mvn test
cd4519c [Lee moon soo] try sys.stdout.write instead of print
6304180 [Lee moon soo] enable 1.2.x test
797c0e2 [Lee moon soo] enable 1.3.x test
8de7add [Lee moon soo] trying to find why travis is not closing the test
cf0a61e [Lee moon soo] rm -rf only interpreter directory instead of mvn clean
2606c04 [Lee moon soo] bringing travis-install.sh back
df8f0ba [Lee moon soo] test more efficiently
9d6b40f [Lee moon soo] Update .travis
2ca3d95 [Lee moon soo] set SPARK_HOME
2a61ecd [Lee moon soo] Clear interpreter directory on mvn clean
f1e8789 [Lee moon soo] update travis config
9e812e7 [Lee moon soo] Use reflection not to use import org.apache.spark.scheduler.Stage
c3d96c1 [Lee moon soo] Handle ZEPPELIN_CLASSPATH proper way
0f9598b [Lee moon soo] py4j version as a property
1b7f951 [Lee moon soo] Add dependency for compile and test
b1d62a5 [Lee moon soo] Add scala-library in test scope
c49be62 [Lee moon soo] Add hadoop jar and spark jar from HADOOP_HOME, SPARK_HOME when they are defined
2052aa3 [Lee moon soo] Load interpreter/spark/dep only when SPARK_HOME is undefined
54fdf0d [Lee moon soo] Separate spark-dependency into submodule
Author: caofangkun <caofangkun@gmail.com>
Closes#186 from caofangkun/zeppelin-207 and squashes the following commits:
a2d155a [caofangkun] ZEPPELIN-207: travis-ci build log is too long to be displayed
713ce5a [caofangkun] ZEPPELIN-207: travis-ci build log is too long to be displayed
3ee6a15 [caofangkun] ZEPPELIN-207: travis-ci build log is too long to be displayed
aa2568d [caofangkun] ZEPPELIN-207: travis-ci build log is too long to be displayed
e5b0067 [caofangkun] ZEPPELIN-207: travis-ci build log is too long to be displayed
https://issues.apache.org/jira/browse/ZEPPELIN-174
* [x] change suffix to sha512
* [x] change to sha512sum command verifiable format
Author: Lee moon soo <moon@apache.org>
Closes#161 from Leemoonsoo/ZEPPELIN-174 and squashes the following commits:
7ba4577 [Lee moon soo] Create sha512sum command verifiable format checksum
fee7757 [Lee moon soo] sha512 suffix for sha checksum
It'll be nice Zeppelin projects has tool that helps making releases. https://issues.apache.org/jira/browse/ZEPPELIN-130
* [x] Ability to create a source release.
* [x] Ability to create binary releases.
Author: Lee moon soo <moon@apache.org>
Closes#119 from Leemoonsoo/release_tool and squashes the following commits:
4c55022 [Lee moon soo] Make and sign bin packages
0a48cfc [Lee moon soo] create source release
Since apache/incubator-zeppelin is a mirror, we can not simply click merge button for pull request.
Here's pullrequest merge tool, i modified little bit for Zeppelin, based on Spark's one.
Author: Lee moon soo <moon@apache.org>
Closes#3 from Leemoonsoo/merge_tool and squashes the following commits:
918e85f [Lee moon soo] Change JIRA project name to ZEPPELIN
1a70af5 [Lee moon soo] Add pull request merge tool
