livy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Meisam Fathi <meisam.fa...@gmail.com>
Subject Re: [VOTE]: Support Livy client for script submitting Solution
Date Wed, 12 Jun 2019 22:45:48 GMT
+1


Thanks,
Meisam

On Wed, Jun 12, 2019, 10:44 AM Alex Bozarth <ajbozart@us.ibm.com> wrote:

> +1 from me, looking forward to seeing the implementation of this great idea
>
>
> *Alex Bozarth*
> Software Engineer
> Center for Open-Source Data & AI Technologies
> ------------------------------
> *E-mail:* *ajbozart@us.ibm.com* <ajbozart@us.ibm.com>
> *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
>
>
> 505 Howard Street
> San Francisco, CA 94105
> United States
>
>
>
> [image: Inactive hide details for Jassy Wang ---06/12/2019 01:31:46
> AM---Hi All, Given the positive response to the design doc [1],]Jassy
> Wang ---06/12/2019 01:31:46 AM---Hi All, Given the positive response to the
> design doc [1], here is the
>
> From: Jassy Wang <jassywang1994@gmail.com>
> To: dev@livy.incubator.apache.org
> Date: 06/12/2019 01:31 AM
> Subject: [EXTERNAL] [VOTE]: Support Livy client for script submitting
> Solution
> ------------------------------
>
>
>
> Hi All,
>
>   Given the positive response to the design doc [1], here is the
> formal vote thread to merge LIVY-596 in to trunk.
>
>   Summary of code changes:
>   1. Add support of submitting by script for Livy server
>   2. Code changes for this branch are done in livy-client project, and
> there is no impact to current livy
>   3. Add Parameter Support for specify session
>
>   We are willing to accept more new ideas and communicate about this
> feature, and this is our design doc:
>
>   The vote will run for 7 days(including 5 weekdays), ending Sat June
> 19th. I will start this
> vote with my +1.
>
> Regards,
> Zhefeng Wang
>
> Reference
> [1]
>
> https://docs.google.com/document/d/1Sc-EHLBhLhmqVn7kQqUexxZ1vwEomb8lW-Vvlpj2Gmc/edit?usp=sharing
>
> [2] https://issues.apache.org/jira/browse/LIVY-596
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message