[
https://issues.apache.org/jira/browse/KNOX-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689773#comment-16689773
]
Jesus Alvarez commented on KNOX-1148:
-------------------------------------
+1 LGTM , works with the old /v1 and with /livy.
This definitely helps clear some of the confusion as to "What does v1" refer to
for the livy endpoint.
!image-2018-11-16-10-05-25-088.png!
For some HDP clusters with multiple versions of spark, there still remains a
bit of a version confusion -
Currently the best approach for Multiple Spark Versions is to "cp -R
data/services/livy data/services/livyspark2" , and change all service URL names
from LIVYSERVER to LIVYSERVER2, such that the topology can then point to each
Livy respectively.
For HDP 3, maybe not as much concern as it was for HDP 2.6.x, which supported
Spark 1 and spark 2.. But something to think about if HDP is going to support
multiple versions of Spark( And thus multiple Livy servers, 1 per spark)
+1 on this Jira to clear some of the confusion though
!/jira/images/icons/emoticons/smile.png|width=16,height=16!
> 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: Kevin Risden
> Priority: Major
> Fix For: 1.3.0
>
> Attachments: KNOX-1148.patch, image-2018-11-16-09-59-21-519.png,
> image-2018-11-16-10-05-25-088.png
>
>
> [https://livy.incubator.apache.org/]
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
