[ https://issues.apache.org/jira/browse/LIVY-758 ]
Larry McCay deleted comment on LIVY-758:
----------------------------------
was (Author: lmccay):
Due to the pending 2.0.0 release this JIRA has been pushed out to 2.1.0 as part
of a bulk update. If there is a specific reason to pull this back into the
2.0.0 release and you intend to provide a PR in the next few days please
provide justification and reset the Fix Version to 2.0.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.9.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)
