GitHub user vgmartinez reopened a pull request:
https://github.com/apache/incubator-zeppelin/pull/154
Notebook Storage in S3
Storage the notebook in s3, is necesary set the enviroment variable
AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY.
In s3 create a folder structure as follows:
bucket/youUserName/notebook/
In zeppelin-env.sh set the bucket name and userName...
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vgmartinez/incubator-zeppelin master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-zeppelin/pull/154.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 #154
----
commit 07ae304434a5d8924d84fc86dcdd0a02dfaa2812
Author: Victor <[email protected]>
Date: 2015-07-13T07:50:40Z
s3 notebook storage
commit 4ccc5c6f98fc34c1d887a758c05adbd69d44aeec
Author: Victor <[email protected]>
Date: 2015-07-13T08:55:19Z
set variable in zeppelin-env.sh
commit 08b0675d369ba9eb915955ff9e255c6024b25c0f
Author: Victor <[email protected]>
Date: 2015-07-13T09:30:01Z
fix the version of eirslett
commit a6d4dff0394d4592f41dc2d6c71f62f927e66cb5
Author: Victor <[email protected]>
Date: 2015-07-13T10:55:35Z
change class storage to VFSNotebookRepo
commit aecff8e1467f01472a69654af7603d0dc3873165
Author: Victor <[email protected]>
Date: 2015-07-13T11:54:29Z
add licensed
commit 518ee797c7bd4459add405d1a80c5efa3e8733ba
Author: Victor <[email protected]>
Date: 2015-07-14T07:25:18Z
renaming variables
commit 2781621963e24a95840a6af336b58c5a3ed668d7
Author: Victor <[email protected]>
Date: 2015-07-16T08:40:19Z
change the property name
commit 6b8abcd2c8e8f225e0f88f58446b1b2956937d21
Author: Victor <[email protected]>
Date: 2015-07-20T08:53:57Z
add description to properties
----
---
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.
---
