[GitHub] zeppelin pull request #2738: [ZEPPELIN-3182] Support saving notebooks to Goo...

2018-02-13 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/zeppelin/pull/2738


---


[GitHub] zeppelin pull request #2738: [ZEPPELIN-3182] Support saving notebooks to Goo...

2018-02-03 Thread karth295
Github user karth295 closed the pull request at:

https://github.com/apache/zeppelin/pull/2738


---


[GitHub] zeppelin pull request #2738: [ZEPPELIN-3182] Support saving notebooks to Goo...

2018-02-03 Thread karth295
GitHub user karth295 reopened a pull request:

https://github.com/apache/zeppelin/pull/2738

[ZEPPELIN-3182] Support saving notebooks to Google Cloud Storage

### What is this PR for?

Support saving notebooks to Google Cloud Storage, similar to 
implementations for S3 and Azure. It uses the same authentication mechanisms as 
the BigQuery interpreter.

I am new to Maven, so please check my work on the pom.xml files. In 
particular, I upgraded Guava to 23.0, which was required for 
`google-cloud-java`. Going through hello-world with my changes seems to work.

Also, I modified the BigQuery interpreter docs to point to the **latest** 
GCS storage docs. Is it more appropriate to pin to the version you are viewing? 
How can I do that?

### What type of PR is it?
Improvement

### Todos
* [Low priority] Support encryption keys

I don't this is particularly important, at least for v1.

### How should this be tested?
* I added unit tests for the core functionality
* I manually tested the authentication instructions (but that could use a 
second pair of eyes)

### Questions:
* Does the licenses files need update?
  * No idea. `google-cloud-java` is Apache 2: 
https://github.com/GoogleCloudPlatform/google-cloud-java/blob/master/LICENSE
* Is there breaking changes for older versions?
  * Nope.
* Does this needs documentation?
  * Yes, and I tried to update the docs (but there are likely other things 
that need to be updated)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/karth295/zeppelin master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zeppelin/pull/2738.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 #2738


commit 8dc819ee4a322d3616f82f6c720eac221fc32ea0
Author: Karthik Palaniappan 
Date:   2018-01-29T03:10:40Z

Unify logic to clear notebook runtime state on load from storage

commit 68b1693568e49e15d47a1d597a97cb5ee70805be
Author: Karthik Palaniappan 
Date:   2018-01-29T03:21:34Z

[ZEPPELIN-3182] Support saving notebooks to Google Cloud Storage




---


[GitHub] zeppelin pull request #2738: [ZEPPELIN-3182] Support saving notebooks to Goo...

2018-01-28 Thread karth295
GitHub user karth295 reopened a pull request:

https://github.com/apache/zeppelin/pull/2738

[ZEPPELIN-3182] Support saving notebooks to Google Cloud Storage

### What is this PR for?

Support saving notebooks to Google Cloud Storage, similar to 
implementations for S3 and Azure. It uses the same authentication mechanisms as 
the BigQuery interpreter.

I am new to Maven, so please check my work on the pom.xml files. In 
particular, I upgraded Guava to 23.0, which was required for 
`google-cloud-java`. Going through hello-world with my changes seems to work.

Also, I modified the BigQuery interpreter docs to point to the **latest** 
GCS storage docs. Is it more appropriate to pin to the version you are viewing? 
How can I do that?

### What type of PR is it?
Improvement

### Todos
* [Low priority] Support encryption keys

I don't this is particularly important, at least for v1.

### How should this be tested?
* I added unit tests for the core functionality
* I manually tested the authentication instructions (but that could use a 
second pair of eyes)

### Questions:
* Does the licenses files need update?
  * No idea. `google-cloud-java` is Apache 2: 
https://github.com/GoogleCloudPlatform/google-cloud-java/blob/master/LICENSE
* Is there breaking changes for older versions?
  * Nope.
* Does this needs documentation?
  * Yes, and I tried to update the docs (but there are likely other things 
that need to be updated)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/karth295/zeppelin master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zeppelin/pull/2738.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 #2738


commit 00d516cd957188cf872b393d86ec7d80d74b4589
Author: Karthik Palaniappan 
Date:   2018-01-24T07:03:38Z

Unify logic to clear notebook runtime state on load from storage

commit 71adaed0f3ceb319eb2b0064c58743b53790bc3e
Author: Karthik Palaniappan 
Date:   2018-01-29T01:05:52Z

[ZEPPELIN-3182] Support saving notebooks to Google Cloud Storage




---


[GitHub] zeppelin pull request #2738: [ZEPPELIN-3182] Support saving notebooks to Goo...

2018-01-28 Thread karth295
Github user karth295 closed the pull request at:

https://github.com/apache/zeppelin/pull/2738


---


[GitHub] zeppelin pull request #2738: [ZEPPELIN-3182] Support saving notebooks to Goo...

2018-01-24 Thread karth295
Github user karth295 closed the pull request at:

https://github.com/apache/zeppelin/pull/2738


---


[GitHub] zeppelin pull request #2738: [ZEPPELIN-3182] Support saving notebooks to Goo...

2018-01-24 Thread karth295
GitHub user karth295 reopened a pull request:

https://github.com/apache/zeppelin/pull/2738

[ZEPPELIN-3182] Support saving notebooks to Google Cloud Storage

### What is this PR for?

Support saving notebooks to Google Cloud Storage, similar to 
implementations for S3 and Azure. It uses the same authentication mechanisms as 
the BigQuery interpreter.

I am new to Maven, so please check my work on the pom.xml files. In 
particular, I upgraded Guava to 23.0, which was required for 
`google-cloud-java`. Going through hello-world with my changes seems to work.

Also, I modified the BigQuery interpreter docs to point to the **latest** 
GCS storage docs. Is it more appropriate to pin to the version you are viewing? 
How can I do that?

### What type of PR is it?
Improvement

### Todos
* [Low priority] Support encryption keys

I don't this is particularly important, at least for v1.

### How should this be tested?
* I added unit tests for the core functionality
* I manually tested the authentication instructions (but that could use a 
second pair of eyes)

### Questions:
* Does the licenses files need update?
  * No idea. `google-cloud-java` is Apache 2: 
https://github.com/GoogleCloudPlatform/google-cloud-java/blob/master/LICENSE
* Is there breaking changes for older versions?
  * Nope.
* Does this needs documentation?
  * Yes, and I tried to update the docs (but there are likely other things 
that need to be updated)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/karth295/zeppelin master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zeppelin/pull/2738.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 #2738


commit 72d1f54b33b1a249e094461fd5d2c80bc8b67fed
Author: Karthik Palaniappan 
Date:   2018-01-24T07:03:38Z

Move common logic to clear notebook runtime state into NotebookRepo

commit 2b7e9930f8260cea492defc9d1cd404ec94a2d38
Author: Karthik Palaniappan 
Date:   2018-01-16T07:52:12Z

[ZEPPELIN-3182] Support saving notebooks to Google Cloud Storage




---


[GitHub] zeppelin pull request #2738: [ZEPPELIN-3182] Support saving notebooks to Goo...

2018-01-21 Thread karth295
GitHub user karth295 opened a pull request:

https://github.com/apache/zeppelin/pull/2738

[ZEPPELIN-3182] Support saving notebooks to Google Cloud Storage

### What is this PR for?

Support saving notebooks to Google Cloud Storage, similar to 
implementations for S3 and Azure. It uses the same authentication mechanisms as 
the BigQuery interpreter.

I am new to Maven, so please check my work on the pom.xml files. In 
particular, I upgraded Guava to 23.0, which was required for 
`google-cloud-java`. Going through hello-world with my changes seems to work.

Also, I modified the BigQuery interpreter docs to point to the **latest** 
GCS storage docs. Is it more appropriate to pin to the version you are viewing? 
How can I do that?

### What type of PR is it?
Improvement

### Todos
* [Low priority] Support encryption keys

I don't this is particularly important, at least for v1.

### How should this be tested?
* I added unit tests for the core functionality
* I manually tested the authentication instructions (but that could use a 
second pair of eyes)

### Questions:
* Does the licenses files need update?
  * No idea. `google-cloud-java` is Apache 2: 
https://github.com/GoogleCloudPlatform/google-cloud-java/blob/master/LICENSE
* Is there breaking changes for older versions?
  * Nope.
* Does this needs documentation?
  * Yes, and I tried to update the docs (but there are likely other things 
that need to be updated)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/karth295/zeppelin master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zeppelin/pull/2738.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 #2738


commit 494aa606c15d7d08c7de6a8e4350be6d7384c931
Author: Karthik Palaniappan 
Date:   2018-01-16T07:52:12Z

[ZEPPELIN-3182] Support saving notebooks to Google Cloud Storage




---