Maybe I missed something, but is LIVY-596 just the design doc? Not sure what is getting merged into trunk? I checked open PR/issues on the Github project and LIVY-596 and only found the design doc linked.
I like the idea of a Livy client and how it could "replace" spark client in a lot of cases. I had a similar idea about 2 years ago but never pursued it. Kevin Risden On Wed, Jun 12, 2019 at 6:10 AM Marco Gaido <marcogaid...@gmail.com> wrote: > Thanks for starting the vote. The feature looks very interesting as it may > spreard livy's adoption IMHO, so I am +1. > Thanks. > > Il giorno mer 12 giu 2019 alle ore 10:46 Yang Jiandan < > succeedin2...@gmail.com> ha scritto: > > > Thanks Jassy Wang for starting the discussion. > > This feature is very useful. > > I'm +1 for this feature. > > > > Jassy Wang <jassywang1...@gmail.com> 于2019年6月12日周三 下午4:31写道： > > > > > 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 > > > > > >
