You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Kevin Risden (JIRA)" <ji...@apache.org> on 2018/11/07 19:51:00 UTC

[jira] [Updated] (KNOX-1148) Fix Livy Service Definition to align with Livy API (Spark REST Service)

     [ https://issues.apache.org/jira/browse/KNOX-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Risden updated KNOX-1148:
-------------------------------
    Fix Version/s:     (was: 1.2.0)
                   1.3.0

> Fix Livy Service Definition to align with Livy API (Spark REST Service) 
> ------------------------------------------------------------------------
>
>                 Key: KNOX-1148
>                 URL: https://issues.apache.org/jira/browse/KNOX-1148
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: Server
>            Reporter: Larry McCay
>            Assignee: Larry McCay
>            Priority: Major
>             Fix For: 1.3.0
>
>
> http://livy.io/
> The initial contribution for Livy REST API includes a deviation from the actual Livy server API in that it requires a "v1" where the actual API does not. This may cause confusion for end users and possible incompatibilities with existing Livy clients that don't expect that.
> We need to remove the need for the "v1" for the 1.0.0 release as it implies an extended level of backward compatibility commitment.
> Here is an example of a Livy Knox service implementation:
> https://community.hortonworks.com/articles/70499/adding-livy-server-as-service-to-apache-knox.html
> The Livy service will need to support Kerberos and load balancing



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)