You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by zjffdu <gi...@git.apache.org> on 2017/09/26 11:52:03 UTC
[GitHub] zeppelin pull request #2600: ZEPPELIN-2953 Allow custom http header for livy...
GitHub user zjffdu opened a pull request:
https://github.com/apache/zeppelin/pull/2600
ZEPPELIN-2953 Allow custom http header for livy interpreter
### What is this PR for?
This PR is trying to allow user to add custom http headers when calling livy rest api. Use just need to specify `zeppelin.livy.http.headers` in livy interpreter setting
### What type of PR is it?
[Feature]
### Todos
* [ ] - Task
### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-2953
### 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
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zjffdu/zeppelin ZEPPELIN-2953
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2600.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 #2600
----
commit 12e2a0c5fa666175a1b3f53e6340fcafaa182eeb
Author: Jeff Zhang <zj...@apache.org>
Date: 2017-09-26T02:12:48Z
ZEPPELIN-2953 Allow custom http header for livy interpreter
----
---
[GitHub] zeppelin pull request #2600: ZEPPELIN-2953 Allow custom http header for livy...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2600
---
[GitHub] zeppelin issue #2600: ZEPPELIN-2953 Allow custom http header for livy interp...
Posted by zjffdu <gi...@git.apache.org>.
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2600
Custom http headers is needed when integrating knox with livy interpreter.
---