[
https://issues.apache.org/jira/browse/KNOX-976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16093496#comment-16093496
]
Jesus Alvarez commented on KNOX-976:
------------------------------------
Same issue on latest trunk code-
Date: Wed, 19 Jul 2017 17:52:21 GMT
< Content-Type: application/json; charset=UTF-8
< Server: TornadoServer/4.4.2
< Content-Length: 71
<
* Connection #0 to host x.x.x.x left intact
{"message": "Invalid JSON in body of request", "reason": "Bad Request"}
Adding policies allows it to go through successfully though, should probably
log that defect separately
> Add Jupyter Kernel Gateway Service Definitions
> ----------------------------------------------
>
> Key: KNOX-976
> URL: https://issues.apache.org/jira/browse/KNOX-976
> Project: Apache Knox
> Issue Type: Task
> Reporter: Jesus Alvarez
> Assignee: Jesus Alvarez
> Fix For: 0.13.0
>
> Attachments: jkg-knox.png, KNOX-976-2.patch, KNOX-976.patch
>
>
> Jupyter Kernel Gateway is a web server that provides headless access to
> Jupyter kernels.
> This allows remote Jupyter notebooks to connect to a kernel gateway running
> in an HDP cluster, and spawn the kernel/spark driver on the kernel gateway
> host.
> https://jupyter-kernel-gateway.readthedocs.io/en/latest/
> Jupyter Kernel Gateway uses on HTTP and Websocket, hence dependency link to
> KNOX-776.
> There are other Jupyter ecosystem projects which could highly benefit/use
> Knox in the future, such as Jupyter Hub.
> The layout which we have currently is similar to zeppelinui/zeppelinws:
>
> gateway-service-definitions/src/main/resources/services/jkg/1.1.2/*.xml
> gateway-service-definitions/src/main/resources/services/jkgws/1.1.2/*.xml
> If there is a preferred naming structure for the 2 services please advise
> (Such as
> gateway-service-definitions/src/main/resources/services/jupyterkernelgateway/1.1.2/*.xml
> )
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
