[
https://issues.apache.org/jira/browse/KNOX-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16316839#comment-16316839
]
Larry McCay commented on KNOX-1148:
-----------------------------------
Moving this out to 1.1.0.
We will need to ensure that whatever change is made here is done so with
backward compatibility in mind. Either through versioning of the service
definition or by allowing both paths within the same service def. Where the
former is probably preferred though will break any topologies from 0.14.0 and
1.0.0.
Perhaps, we make some statement of deprecation for the current service def in
1.0.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
> Fix For: 1.1.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
(v6.4.14#64029)
