[
https://issues.apache.org/jira/browse/LIVY-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyorgy Gal updated LIVY-55:
---------------------------
Fix Version/s: 0.10.0
(was: 0.9.0)
This issue has been moved to the 0.10.0 release as part of a bulk update. If
you feel this is moved out inappropriately, feel free to provide justification
and reset the Fix Version to 0.9.0.
> Exposing YARN ID and YARN logs
> ------------------------------
>
> Key: LIVY-55
> URL: https://issues.apache.org/jira/browse/LIVY-55
> Project: Livy
> Issue Type: Improvement
> Components: API
> Affects Versions: 0.2
> Reporter: Alex Man
> Priority: Minor
> Fix For: 0.10.0
>
>
> Exposing YARN ID and YARN logs
> Exposing YARN ID and YARN logs will improve the manageability of Livy. As
> they are YARN specific, they should be separated to a new nested interface.
> I think we can add nested resource {{cluster}} in {{batch}} & {{session}} to
> expose these cluster manager specific APIs.
> Example response:
> {noformat}
> GET /sessions/{{id}}/cluster
> {
> "type": "yarn",
> "applicationId": "application_xx_yy_zz"
> }
> GET /sessions/{{id}}/cluster/log
> {
> "from":..,
> "total":..,
> "log":[]
> }
> Optionally, we can automatically return cluster specific information in the
> {{batch}} & {{session}} objects:
> GET /sessions/{{id}}
> {
> id:..,
> state:..
> kind:..,
> log: []
> cluster: {
> "type": "yarn",
> "applicationId": "application_xx_yy_zz"
> }
> }
> {noformat}
> Interface definitions:
> {noformat}
> interface Cluster {
> val type: String
> }
> interface YarnCluster extends Cluster {
> val applicationId: String
> def log(): String
> }
> {noformat}
> applicationId and log APIs will only be available when cluster.type == "yarn"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
