You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@livy.apache.org by "Jeff Zhang (JIRA)" <ji...@apache.org> on 2019/05/18 13:15:00 UTC

[jira] [Comment Edited] (LIVY-596) Livy Client which support to submit job with shell

    [ https://issues.apache.org/jira/browse/LIVY-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16843158#comment-16843158 ] 

Jeff Zhang edited comment on LIVY-596 at 5/18/19 1:14 PM:
----------------------------------------------------------

[~runlin] Thanks for the proposal, this is a very interesting idea. Could you also send discussion thread in livy dev mail list to gather more feedback and comment ?


was (Author: zjffdu):
[~runlin] Thanks for the proposal, this is a very interesting idea. Could you also send discussion mail in livy dev mail list to gather more feedback and comment ?

> Livy Client which support to submit job with shell
> --------------------------------------------------
>
>                 Key: LIVY-596
>                 URL: https://issues.apache.org/jira/browse/LIVY-596
>             Project: Livy
>          Issue Type: New Feature
>    Affects Versions: 0.6.0
>            Reporter: Zhefeng Wang
>            Priority: Minor
>         Attachments: Livy Client.docx
>
>
> Many users have previously used the spark client to submit spark task with scripts. When users want to try Livy, Livy currently only provides the programming interface and REST api. For individual users, it is not convenient to submit tasks and view tasks progress info.
> To solve this problem, Livy client is developed and adapted parameter formation of spark client, so that the user can easily switch from spark to Livy without modifying the original submit script, Also Livy client print the progress of the task in the console. To avoid the user calling the tedious rest api.
> ----
> [Livy Client Design Doc|https://docs.google.com/document/d/1Sc-EHLBhLhmqVn7kQqUexxZ1vwEomb8lW-Vvlpj2Gmc/edit?usp=sharing]



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