GitHub user cloverhearts opened a pull request:
https://github.com/apache/zeppelin/pull/1397
[ZEPPELIN-1406] modify to load method artifact local path in Helium
application json
### What is this PR for?
Currently contained in the Zeppelin Helium application does not work.
The relative value of the configuration file path does incurring call
normally.
Therefore, it sets the Helium directory you specified in the application
default directory.
An example of the application was to modify the path of helium.
### What type of PR is it?
Bug Fix, Improvement
### Todos
- [x] added setter method for artifact in Helium Packakge class
- [x] if not absolute path for artifact then replace to absolute path for
helium artifact local path
- [x] replace helium example artifact path for json
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1406
### How should this be tested?
step 1.
build
```
mvn clean package -DskipTests -Pbuild-distr -Pexamples -DskipTests
```
step 2.
go to web ui and someone notebook.
write paragraph.
here.
```
%spark
import java.util.Date
new Date();
```
step 3.
choice.
helium application clock.
working well.
### Screenshots (if appropriate)
#### before
does not working.
#### after
### 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/cloverhearts/zeppelin
dev/helium-json-relative-path
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1397.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 #1397
----
commit ad84e5b6f6945bc6e7209ba19d578fd7bf1c0e04
Author: CloverHearts <[email protected]>
Date: 2016-09-02T09:07:20Z
modification to artifact local path in Helium application json
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
