You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@livy.apache.org by "Marcelo Vanzin (JIRA)" <ji...@apache.org> on 2018/11/29 18:10:00 UTC

[jira] [Resolved] (LIVY-503) Move RPC classes used in thrifserver in a separate module

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

Marcelo Vanzin resolved LIVY-503.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 0.6.0

Issue resolved by pull request 118
[https://github.com/apache/incubator-livy/pull/118]

> Move RPC classes used in thrifserver in a separate module
> ---------------------------------------------------------
>
>                 Key: LIVY-503
>                 URL: https://issues.apache.org/jira/browse/LIVY-503
>             Project: Livy
>          Issue Type: Sub-task
>            Reporter: Marco Gaido
>            Priority: Major
>             Fix For: 0.6.0
>
>
> As suggested in the discussion for the original PR (https://github.com/apache/incubator-livy/pull/104#discussion_r212806490), we should move the RPC classes which need to be uploaded to the Spark session in a separate module, in order to upload as few classes as possible and avoid eventual interaction with the Spark session created.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)