You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@livy.apache.org by "Gyorgy Gal (Jira)" <ji...@apache.org> on 2025/11/10 17:13:03 UTC

[jira] [Updated] (LIVY-758) Java API should be able to connect to existing session

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

Gyorgy Gal updated LIVY-758:
----------------------------
    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.

> Java API should be able to connect to existing session
> ------------------------------------------------------
>
>                 Key: LIVY-758
>                 URL: https://issues.apache.org/jira/browse/LIVY-758
>             Project: Livy
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: 0.6.0, 0.7.0
>            Reporter: Antonio Murgia
>            Priority: Major
>              Labels: api, client, java
>             Fix For: 0.10.0
>
>   Original Estimate: 4h
>          Time Spent: 40m
>  Remaining Estimate: 3h 20m
>
> The current Java client automatically creates a new session upon connection, unless an uri with a session is passed (i.e. passing [http://localhost:8999/sessions/3] as URI will attach to session 3). This is not documented at all and I think it should be documented more explicitly. Also I purpose to add a method to LivyClientBuilder in order to explicitly set the session id to be used, without removing the actual solution that can still be used anyway. If the session id is set both in the property and the URI, an exception will be thrown.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)