[
https://issues.apache.org/jira/browse/LIVY-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyorgy Gal updated LIVY-367:
----------------------------
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.
> Globally unique session ID / exposing user-defined session name in REST API
> ---------------------------------------------------------------------------
>
> Key: LIVY-367
> URL: https://issues.apache.org/jira/browse/LIVY-367
> Project: Livy
> Issue Type: Improvement
> Components: API
> Affects Versions: 0.3
> Reporter: Ivan
> Priority: Major
> Fix For: 0.10.0
>
>
> Working with an in-house install of Livy 0.3 (standalone) and also
> Azure-based HDInsight. Somewhat of a newbie, so if I am missing something
> obvious here, please direct to the relevant source/docs. My use case is
> interactive: sessions/statements.
> What I observed is the lack of any apparent globally unique session
> identifier; don't think one could count the current numeric "id" as one, even
> in [potentially] HA scenarios. For YARN installations there is "appId" (which
> can probably be treated as unique for practical purposes), but obviously does
> not extend to standalone mode.
> Then there is the "name" field when creating a session that unsurprisingly
> assigns a name to the session. I thought "that's it - a place to put a GUID
> for session tracking" - however, strangely the name is not returned as part
> of the session description by the REST API.
> Tracking the lifetime of multiple sessions over time and syncing them to the
> client-side counterparts is part of my use case. It is somewhat surprising
> that robust session identification is not part of the API, leading me to an
> assumption that I am missing something obvious here...
> Either way, the minor improvement request is to expose the session name
> (already controllable by the API user in POST /sessions { "kind": "spark",
> "name" : "my session label" }) to the session definitions returned by
> /sessions REST endpoint. This seems like a useful field for arbitrary
> user-driven label/description/identifier.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
