Re: .NET for Apache Spark interactive interpreter support

> > > https://github.com/dotnet/spark/tree/master/deployment/HDI-Spark/Notebooks > > > > > > > > > available > > > > that adds support for a Spark *Dotnet **interactive session* and I > > would > > > > like to know if the Livy community would be interested in adding this > > > > feature to the main code base. If so, please let me know and I can > > work > > > on > > > > creating this PR. > > > > > > > > For now, I've created a Jira item > > > > <https://issues.apache.org/jira/browse/LIVY-742> to track this. > > > > > > > > > > > > Regards, > > > > -Steve > > > > > > > > > > -- Best Regards Jeff Zhang

Re: [VOTE] Release Livy 0.7.0 based on RC4

306239d54 > > > > > > The release files can be found here: > > > > > > https://dist.apache.org/repos/dist/dev/incubator/livy/0.7.0-incubating-rc4/ > > > > > > The staged maven artifacts can be found here: > > > https://repository.apache.org/content/repositories/orgapachelivy-1013 > > > > > > The list of resolved JIRAs in this release can be found here: > > > https://issues.apache.org/jira/projects/LIVY/versions/12345179 > > > > > > Thanks > > > Saisai > > > > > > -- Best Regards Jeff Zhang

Re: [Vote][LIVY-718] Support multi-active high availability in Livy

e moved to > > other > > > >active services. > > > > > > > > Please find the design doc here > > > > < > > > > > > > > > > https://docs.google.com/document/d/1bD3qYZpw14_NuCcSGUOfqQ0pqvSbCQsOLFuZp26Ohjc/edit?usp=sharing > > > > >, > > > > which has been reviewed for several weeks. > > > > > > > > This vote is open until next Wednesday (Dec. 18). > > > > > > > > [] +1: Accept the proposal > > > > [] +0 > > > > [] -1: I don't think this is a good idea because ... > > > > > > > > Thank you > > > > > > > > Yiheng > > > > > > > > > > -- Best Regards Jeff Zhang

Re: Plan to cut new branch and prepare to release 0.7

LIVY-689] Deliver stage process message to the end user using thriftserver > > Any thought? > > Thanks > Saisai > -- Best Regards Jeff Zhang

Re: Podling Report Reminder - October 2019

19 > > Note: This is manually populated. You may need to wait a little before > this page is created from a template. > > Note: The format of the report has changed to use markdown. > > Mentors > --- > > Mentors should review reports for their project(s) and sign them off

Re: please join

please send mail to dev-subscr...@livy.incubator.apache.org Jeffrey Rodriguez 于2019年7月19日周五 上午7:15写道： > I want to join dev@livy.incubator.apache.org > Jeff > -- Best Regards Jeff Zhang

Re: Livy Sessions

bout where I might be doing wrong? Is there any > known limitation that I'm unaware of? > > Best, > > Hugo Herlanin > > -- Best Regards Jeff Zhang

Re: Proposal about Livy Client

user, backend livy server can change spark > dependency > >at realtime and user has no need to know that. > >- Livy-Client is more lightweight than spark client and has no > >dependency, moreover spark job running in cluster mode will not occupy > >memory and calculation resources in local machine. > >- All jobs submited by Livy-Client will run in cluster mode which is > >more convenient to shoot the trouble > > > > For more information about Livy client, please see Livy client design doc > > < > https://docs.google.com/document/d/1Sc-EHLBhLhmqVn7kQqUexxZ1vwEomb8lW-Vvlpj2Gmc/edit?usp=sharing > > > > or discuss with us in issue link > > <https://issues.apache.org/jira/browse/LIVY-596>. > > > -- Best Regards Jeff Zhang

Re: We're using Livy!

around docker deployment, job log > > enhancements, some optional job argument preprocessing) and (2) getting > off > > of our fork by isolating our very specific code elsewhere. > > > > I also see a LOT of interesting work in the PRs and JIRA, so I'm keenly > > inter

Re: [VOTE] Release Livy 0.6.0 based on RC2

>> > > > > >> > > > This vote is held according to Apache Incubator release policy: > >> > > > https://incubator.apache.org/policy/incubation.html#releases > >> > > > > >> > > > The RC is based on tag v0.6.0-incubating-rc2: > >> > > > https://github.com/apache/incubator-livy/commit/28be98cabc > >> > > > > >> > > > The release files can be found here: > >> > > > > >> > > > >> > https://dist.apache.org/repos/dist/dev/incubator/livy/0.6.0-incubating-rc2/ > >> > > > > >> > > > The staged maven artifacts can be found here: > >> > > > > >> https://repository.apache.org/content/repositories/orgapachelivy-1008 > >> > > > > >> > > > The list of resolved JIRAs in this release can be found here: > >> > > > https://issues.apache.org/jira/projects/LIVY/versions/12342736 > >> > > > > >> > > > > >> > > > -- > >> > > > Marcelo > >> > > > >> > > > >> > > > >> > > -- > >> > > Marcelo > >> > > > >> > >> > >> > >> -- > >> Marcelo > >> > > > -- Best Regards Jeff Zhang

Re: New Livy release

t;> > >>> On Wed, Nov 7, 2018 at 10:46 AM Bikas Saha wrote: > >>>> Hi all, > >>>> > >>>> Given the Apache Spark 2.4 release and the resolution of LIVY-518, > >> should we trigger the next Apache Livy release so users have Spark 2.

Re: [DISCUSS] Getting rid of old stuff

+1 Alex Bozarth 于2018年9月14日周五 上午6:26写道： > I agree with all of Marcelo's points. The last time we discussed this was > when Spark 2.2 was new and it was decided that it was probably too soon, > but that was awhile ago now. I've been in support of deprecating and > removing support for older

Re: Development in Intellij IDEA

Regarding the multiple scala version, here's my hack in intellij. 1. make a soft link from parent src folder to current project folder 2. Add source folder via intellij Here's the project structure of my livy repl module in intellj - repl - scala-2.10 - repl-parent-src (this is

Re: Podling Report Reminder - February 2018

Great, thanks Alex Alex Bozarth 于2018年1月30日周二 下午12:57写道： > As I mentioned earlier this month I will take care of this, but I plan to > wait until the results of the PMC vote on 0.5 so as to include that in our > update. > > > *Alex Bozarth* > Software Engineer > Spark

Can anyone get email about livy jira change

Hi all, I can get email notification about jira changes of other apache projects, but never receive email about livy ticket. Can anyone get email about livy jira change ? Or does it need some configuration on the jira system ?

Re: The process of Livy 0.4.0-incubating release

I think we'd better to announce after the artifacts are published. Saisai Shao 于2017年8月31日周四 上午8:35写道： > Hi Alex, > > I think you can update the website PR firstly to link to the correct > download URL (since the package is already available) and doc. > > I'm working on

Re: Apache JIRA up and running

Awesome Alex Bozarth 于2017年8月19日周六 上午3:07写道： > > > Hey team, > > As of this morning the Livy project is now in the Apache JIRA, so you can > now open new issues at: > > https://issues.apache.org/jira/projects/LIVY > > A big thanks the Apache INFRA team, specifically Gavin,

Re: To release a first Apache version Livy

+1 for making the first apache release. Saisai Shao 于2017年7月28日周五 下午3:42写道： > Hi Team, > > We have already done most of the migration works to Apache, I think it > would be better to have a first Apache release based on the current code. > What do you think? > > Thanks >

Re: Livy Slack and the move to Apache

+1 for using apache user mail list. Alex Bozarth 于2017年7月20日周四 上午10:21写道： > > > With our move to Apache I looked into and discussed with Luciano how we > should handle the Livy Slack that we link to on the README and came to the > following answer: > > I petition