Re: Podling Report Reminder - July 2017

Hi team, This is the draft of podling report, I'm new to Apache process, please review and shepherd, thanks! Livy Livy is web service that exposes a REST interface for managing long running Apache Spark contexts in your cluster. With Livy, new applications can be built

Re: Scala 2.11 and Hive

Hi Mobin, Livy supports Scala 2.11 as well as Spark 2.0+. Can you please elaborate your problem? Thanks Jerry On Sun, Jul 2, 2017 at 9:19 PM, Mobin Ranjbar wrote: > Hi there, > > > I have a problem around using Livy and Apache Spark(Scala 2.10). I have > Apache Hive that does not support Spark

Podling Report for review

Hi team, Here is the draft of podling report, please help to review. @Mentors, would you please sign off this draft and append to https://wiki.apache.org/incubator/July2017, greatly appreciated. Thanks Jerry Livy Livy is web service that exposes a REST interface for man

Re: Podling Report Reminder - July 2017

wrote: > Thanks for putting this together. The report is now past due though, and > this looks like a fine "first report." If you need access to the incubator > wiki to post, please shout. > > On 2017-07-03 22:20 (-0400), Saisai Shao wrote: > > Hi team, > > &g

Re: Podling Report Reminder - July 2017

#x27;ll need to separately > register. > > > > John > > > > On 2017-07-07 17:50 (-0400), Saisai Shao wrote: > > > Thanks John for your reply. Please do make me accessible to incubator > wiki, > > > my account id is: jshao. I will append the report to W

Re: Another approach for Livy Website

I think this is great. Looking from the previous thread our major concern is to keep the contribution history/credits, will this break the history/credits? If not I think this probably be better. On Thu, Jul 13, 2017 at 1:33 PM, Luciano Resende wrote: > While looking at the current website, it s

Re: Another approach for Livy Website

rrent concerns about history/credits. > > On Thu, Jul 13, 2017 at 1:45 PM, Saisai Shao > wrote: > > > I think this is great. Looking from the previous thread our major concern > > is to keep the contribution history/credits, will this break the > > history/cre

Re: Another approach for Livy Website

nology Center > -- > *E-mail:* *ajboz...@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 Sai

Re: Another approach for Livy Website

enter > ------ > *E-mail:* *ajboz...@us.ibm.com* > *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth> > > > 505 Howard Street > San Francisco, CA 94105 > United States > > > > Saisai Shao ---07/13/2017 02:20:04 PM---Mayb

Re: Another approach for Livy Website

stly ready) and, if we want to, can also > open a > > PR to clean up the old site branch so it doesn't include all the old livy > > code, just the old website code. > > > > > > *Alex Bozarth* > > Software Engineer > > Spark Technology Center &

Re: Livy Slack and the move to Apache

+1 for this. On Wed, Jul 19, 2017 at 7:30 PM, Jeff Zhang wrote: > +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

Re: Commit style best practices, was Re: incubator-livy-website git commit: Fix bug in merge_livy_pr.py because incubator-livy-website repo has no branch it's name started with "branch-"

Sorry about it. Basically because I don't know whether JIRA is necessary for incubator-livy-website repo, also where to create JIRA. On Thu, Jul 20, 2017 at 1:20 PM, Alex Bozarth wrote: > +1. I think we've been using close to this format, but with "LIVY-XXX." > instead of "[LIVY-XXX]". I can inc

When Livy JIRA system will be ready?

Hi team, May I ask when Livy JIRA system in Apache will be ready? Currently most of the transition works are done except JIRA, contributors still need to create JIRAs on cloudera.org (which has very limited permission) and submit code to Apache. Thanks Saisai

Re: When Livy JIRA system will be ready?

- > *E-mail:* *ajboz...@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 Saisai Shao ---07/23/2017 11:32:03 > PM---Hi

Re: Setting environment variable in Livy Interactive

I'm not sure if current Livy support setting env variables through REST API. But most of the Spark related environment variables you can find out a corresponding configuration like spark.[driver|executor].extraClasspath, you don't have to use env variables. On Tue, Jul 25, 2017 at 9:34 AM, ayushi

Re: Need input: Location of Livy Documentation

I'm in favor of store the docs in main repo, while put seldom changed frameworks in website repo. I think you already mentioned the reason here (as the Documentation grows and changes from version to version it would be better to store it in the more regularly updated repo). What I saw is that Spa

To release a first Apache version Livy

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 Saisai

Re: Podling Report Reminder - August 2017

Hi Team, I just made a August podling report of Livy (https://wiki.apache.org/ incubator/August2017), please review and sign off. For anything should be changed/updated please let me know. Thanks Saisai On Sun, Jul 30, 2017 at 10:23 PM, wrote: > Dear podling, > > This email was sent by an auto

Re: To release a first Apache version Livy

rowse/LIVY-384>). If others are > fine releasing with these feature partially complete then I'll be okay as > well. > > *Alex Bozarth* > Software Engineer > Spark Technology Center > -- > *E-mail:* *ajboz...@us.ibm.com* > *GitHub: **github.com/ajbozarth* <h

Re: To release a first Apache version Livy

t; *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth> > > > 505 Howard Street > San Francisco, CA 94105 > United States > > > > [image: Inactive hide details for Saisai Shao ---07/31/2017 07:12:11 > PM---Hi Alex, can you please list the JIRAs for UI r

Re: To release a first Apache version Livy

Hi Team, We're planning to release a first Apache version of Livy. Would you please guide us the process of Apache incubating release, is there any doc to follow. Thanks a lot! Best regards Saisai On Tue, Aug 1, 2017 at 11:34 AM, Saisai Shao wrote: > OK, thanks! Let's get thi

Re: To release a first Apache version Livy

> cadence. Should we move to a 3 month or 4 month release cadence such that > release trains are available for features to out when the features are > ready. Or should do feature releases such that releases come out when major > new functionality has added. My preference is a time based rel

Re: red flags in IntelliJ when importing from pom.xml

Hi Nan, Because of supporting multiple scala version makes module hierarchy quite complex, Intellij cannot identify the code which is added through maven plugin. Currently I don't have a good solution to handle it. On Mon, Aug 7, 2017 at 8:05 AM, Nan Zhu wrote: > Hi, all > > I just start lookin

Re: To release a first Apache version Livy

elp make bug > fix releases available. > > > Btw, does anyone know whats holding up the Apache jira process? If not, I > can follow up on that. > > > Bikas > > > From: Saisai Shao > Sent: Thursday, August 3, 2017 7:31:10 PM >

Re: To release a first Apache version Livy

hub.com/ajbozarth* <https://github.com/ajbozarth> > > > 505 Howard Street > San Francisco, CA 94105 > United States > > > > [image: Inactive hide details for Saisai Shao ---08/07/2017 02:17:08 > AM---Hi Team, Today I cut a RC1 release based on branch-0.4, here]Saisai >

Re: To release a first Apache version Livy

ot of git today. > > > > > > On Mon, Aug 7, 2017 at 2:16 AM, Saisai Shao > wrote: > > > Hi Team, > > > > Today I cut a RC1 release based on branch-0.4, here is the link ( > > https://github.com/apache/incubator-livy/releases/tag/ > > v0.4.0-inc

Re: To release a first Apache version Livy

ample) > > http://svn.apache.org/repos/asf/tuscany/sca-java-2.x/ > trunk/distribution/all/src/main/release/bin/LICENSE > > > > But note that, the source release artifact, which should not include any > > dependency jars, should have the LICENSE file similar to what is in the &

Re: To release a first Apache version Livy

was > inspired by the Spark one. > > https://github.com/apache/bahir/blob/master/dev/release-build.sh > > On Mon, Aug 7, 2017 at 6:14 PM, Saisai Shao > wrote: > > > Thanks Marcelo for your comments. I checked create_release.sh in Spark, I > > think I will adopt thi

To support multiple interpreters in one session

Hi Team, I'm working on supporting multiple interpreters in one session, specially to support launching spark, pyspark and sparkr interpreters in one session. This changes the current Livy REPL code a lot, so I'd like to hear your feedback. Here is the design doc https://docs.google.com/document/

Re: To release a first Apache version Livy

top level distribution (e.g. tar.gz should have a proper LICENSE and > NOTES) and it should reflect the included dependencies LICENSE and NOTES. > > On Mon, Aug 7, 2017 at 7:31 PM, Saisai Shao > wrote: > > > Hi Luciano, should we include all the third jar license in a file in

Help to verify Apache Livy 0.4.0-incubating release

Hi all, We're under progress to make a first Apache release of Livy (0.4.0-incubating), we really hope you could verify the RC2[1] release (binary and source) locally and return us the feedbacks. We will call for an incubation vote next week if everything is fine. Thanks a lot for your help. [1

Re: Help to verify Apache Livy 0.4.0-incubating release

> > > Looks good. > > All signatures and checksums match. > > Unit tests pass (after I installed R). > > Livy server starts up and I can see the UI, but didn't try to run > anything on it. > > > On Thu, Aug 17, 2017 at 12:34 AM, Saisai Shao > wrote:

Re: Help to verify Apache Livy 0.4.0-incubating release

I changed the package name to to apache-livy-0.4.0-incubating-[src/bin].zip, please check if it is OK ( https://dist.apache.org/repos/dist/dev/incubator/livy/0.4.0-incubating/). On Fri, Aug 18, 2017 at 9:37 AM, Saisai Shao wrote: > So the name would be "incubator-livy-0.4.0-incubating-

Re: Apache JIRA up and running

Great, I think we left some resolved JIRAs unassigned because of lack of permission, we should fix it now. On Mon, Aug 21, 2017 at 10:06 AM, Jeff Zhang wrote: > Awesome > > > Alex Bozarth 于2017年8月19日周六 上午3:07写道： > > > > > > > Hey team, > > > > As of this morning the Livy project is now in the

Re: [VOTE] Release Livy 0.4.0-incubating based on Livy 0.4.0 RC2

OK, sure, I will remove RC1 from the directory. Thanks Jerry On Tue, Aug 22, 2017 at 7:24 PM, John D. Ament wrote: > Hi, > > Looking at your release, it's confusing what we are voting on. If RC2 is > under vote, please remove RC1 from this directory. > > John > > On Tue, Aug 22, 2017 at 3:33 A

Re: Help to verify Apache Livy 0.4.0-incubating release

--- > > > > > > > > The version of org.apache.httpcomponents:httpclient is different in > > /pom.xml from the version in /client-http/pom.xml > > > > /pom.xml ---> ${httpclient.version} ---> 4.5.2 > > /client-http/pom.xml ---> 4.5.1 >

Re: resolve the scalability problem caused by app monitoring in livy with an actor-based design

Nan, I think Meisam already had a PR about this this, maybe you can discuss with him on the github based on the proposed code. Sorry I didn't follow the long discussion thread, but I think Paypal's solution sounds simpler. On Wed, Aug 23, 2017 at 12:07 AM, Nan Zhu wrote: > based on this result,

Please vote for Apache Livy 0.4.0-incubating release

Hi teams, Would you please help to vote for the Apache Livy release in general incubator mail list. Thanks a lot. http://mail-archives.apache.org/mod_mbox/incubator-general/201708.mbox/%3CCANvfmP8sAoofvRcs9AT5S-VW4LfiWeGfRXP2rhvEP4zyTag%2BYQ%40mail.gmail.com%3E Thanks

The process of Livy 0.4.0-incubating release

Hi mentors, Would you please guide us on how to release the Livy 0.4.0-incubating, including artifact publish. Also regarding push artifacts to repo, are we inclining to change to Maven central repo, or we still use Cloudera repo, any suggestion? Besides, for Python package release, do we need t

Re: The process of Livy 0.4.0-incubating release

- > > > > IIRC it would be maven with the org.apache coordinates. > > > Wait for it to be available via caches. Then we can update the website and > send out a notice email to the lists. > > > Bikas > > ___

Re: Update ASF GitHub Bot Settings?

Hi Alex, Do you want to achieve what Spark did in the JIRA? AFAIK Spark uses a script to sync between github and jira, it doesn't enable gihub robot to mirror everything from github. Thanks Jerry On Tue, Aug 29, 2017 at 5:00 AM, Alex Bozarth wrote: > Opened an INFRA JIRA https://issues.apache.

Re: Update ASF GitHub Bot Settings?

Howard Street > San Francisco, CA 94105 > United States > > > > [image: Inactive hide details for Saisai Shao ---08/28/2017 06:53:28 > PM---Hi Alex, Do you want to achieve what Spark did in the JIRA? A]Saisai > Shao ---08/28/2017 06:53:28 PM---Hi Alex, Do you want to achie

Re: The process of Livy 0.4.0-incubating release

his profile for Livy? Also how can I create this profile? Thanks Jerry On Mon, Aug 28, 2017 at 3:39 PM, Luciano Resende wrote: > On Sun, Aug 27, 2017 at 11:53 PM, Saisai Shao > wrote: > > > Hi mentors, > > > > Would you please guide us on how to release the Livy 0.4.0-

Re: The process of Livy 0.4.0-incubating release

will write a doc as well as release script for the next release. Sorry about it. Best regards, Jerry On Wed, Aug 30, 2017 at 2:10 PM, Saisai Shao wrote: > Hi Luciano, > > I'm trying to push maven artifacts to maven staging repository at > repository.apache.org, seems we

Re: The process of Livy 0.4.0-incubating release

> *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth> > > > 505 Howard Street > San Francisco, CA 94105 > United States > > > > [image: Inactive hide details for Saisai Shao ---08/30/2017 12:05:24 > AM---Looks like I wronged the releasing process,

Re: The process of Livy 0.4.0-incubating release

oward Street > San Francisco, CA 94105 > United States > > > > [image: Inactive hide details for Jeff Zhang ---08/30/2017 05:53:15 PM---I > think we'd better to announce after the artifacts are publis]Jeff Zhang > ---08/30/2017 05:53:15 PM---I think we&#x

Re: The process of Livy 0.4.0-incubating release

gt; *E-mail:* *ajboz...@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 Saisai Shao ---09/01/2017 01:11:03 > AM---Hi all, I just p

[ANNOUNCE] Apache Livy 0.4.0-incubating released

The Apache Livy team is proud to announce Apache Livy version 0.4.0-incubating. This is the first Livy release after entering the Apache Incubator. Livy is web service that exposes a REST interface for managing long running Apache Spark contexts in your cluster. With Livy, new applications can be

Re: Podling Report Reminder - September 2017

Hi Team, I just wrote a podling report, can you please review/update/sign off this report. Thanks a lot! Best regards, Jerry On Wed, Sep 6, 2017 at 9:40 AM, wrote: > Dear podling, > > This email was sent by an automated system on behalf of the Apache > Incubator PMC. It is an initial reminder

Re: user defined sessionId / URI for Livy sessions

If we're using session name, how do we guarantee the uniqueness of this name? Thanks Jerry On Tue, Sep 12, 2017 at 4:51 AM, Alex Bozarth wrote: > I would agree with Marcelo's comment the JIRA that this isn't a good > feature for livy, but I'll take a look at your impl if you open a PR and > see

Re: user defined sessionId / URI for Livy sessions

I see. So based on this, we should manage a data structure in Livy Server to keep all the live sessions' name. Also regarding to session recovery, we should persist this structure to the reliable storage and recover after restart. I'm not pretty sure if it is a good feature or not. First because w

How to get the test logs from travis

Hi Team, Currently it is quite painful to figure out the cause of failure on travis test. Do you know how to get test logs from travis, is there a way supported by travis to either upload environment to some places, or log on to travis to dig the files. Previously we uploaded logs to azure when t

Re: How to get the test logs from travis

t a lot of the logs and > related files which then get appended to the build results. > > https://github.com/apache/zeppelin/blob/master/.travis.yml > > On Wed, Sep 20, 2017 at 8:22 PM, Saisai Shao > wrote: > > > Hi Team, > > > > Currently it is quite pai

Re: Podling Report Reminder - October 2017

Hi Team, Here is the October's podling report, please review and sign-off. https://wiki.apache.org/incubator/October2017 Thanks Jerry On Sun, Oct 1, 2017 at 9:06 PM, wrote: > Dear podling, > > This email was sent by an automated system on behalf of the Apache > Incubator PMC. It is an initia

Re: Can Spark jobs which are submitted via Livy run concurrently?

No, current Livy interactive session doesn't support running statements concurrently. Because Livy doesn't know if multiple statements have dependencies or not, running concurrently will lead to unexpected results. So submitted statements can only be run one by one. Thanks Jerry 2017-12-14 14:25

Re: [DRAFT] Incubator PMC Board Report - January 2018

Sorry I was on paternity leave last two weeks, didn't have time to check it. Maybe you can also help on this next time. Thanks Jerry 2018-01-09 4:32 GMT+08:00 Alex Bozarth : > Saw that we didn't report this month, any reason why, or was everyone just > on holiday? > > > *Alex Bozarth* > Software

Fwd: [apache/incubator-livy] One of your dependencies may have a security vulnerability

Hi Alex, Is it due to your recent changes to add ruby file? Thanks Jerry -- Forwarded message -- From: Greg Stein Date: 2018-01-24 6:14 GMT+08:00 Subject: Fwd: [apache/incubator-livy] One of your dependencies may have a security vulnerability To: priv...@livy.incubator.apache.or

Re: [VOTE] Livy 0.5.0-incubating (RC2)

asc, sha512 and md5 LGTM. Also checked the package, seems everything is landed. Alex, did you also publish Livy artifacts to staging repo? 2018-01-26 8:03 GMT+08:00 Alex Bozarth : > That works for me, voting will be open an extra day for a total of 96 > hours ending on Tuesday January 30th at 12

Re: [VOTE] Livy 0.5.0-incubating (RC2)

Ideally, when a new RC is out, we should put release package on svn, and push artifacts to staging repo. Once vote is passed, just clicking “releas” to publish to maven repo is enough. We can push RC2 artifacts to staging repo for now. Alex Bozarth 于2018年1月27日 周六上午6:32写道： > Just wondering, but s

Re: [VOTE] Livy 0.5.0-incubating (RC2)

Hi Alex, Did you push artifacts to staging repo? I think I mentioned before to push artifacts to staging repo when you initiate a new RC vote. 2018-01-30 10:21 GMT+08:00 Alex Bozarth : > The votes passes with three +1s and a -0. I will be sending an email to > the Incubator PMC for a vote soon.

Re: [VOTE] Livy 0.5.0-incubating (RC2)

; San Francisco, CA 94105 > <https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States&entry=gmail&source=g> > United States > <https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States&entry=gmail&source=g> >

Re: Podling Report Reminder - February 2018

Great, thanks Alex! Best regards, Jerry 2018-02-06 7:56 GMT+08:00 Alex Bozarth : > I've updated the report if a mentor could take a look and sign off (or > give feedback). > > > *Alex Bozarth* > Software Engineer > Spark Technology Center > -- > *E-mail:* *ajboz...@us

Fwd: [apache/incubator-livy] One of your dependencies may have a security vulnerability

Hi Alex, Would you please check again? Thanks! Best regards -- Forwarded message -- From: Apache Security Team Date: 2018-03-06 16:39 GMT+08:00 Subject: Re: [apache/incubator-livy] One of your dependencies may have a security vulnerability To: Saisai Shao Cc: priv

Re: Development in Intellij IDEA

Like what Alex mentioned, due to the support of multi-version Scala in one project, we add some tricks in Maven to make it work. But unfortunately Intellij IDEA is not intelligent enough to recognize such tricks. So it is hard to build and run test in IDEA. Maybe you need to manually add something.

Re: Query on creating multiple livy sessions in parallel

This might be a BUG. If possible can you please create a JIRA to track this issue. Thanks! Best, Jerry 2018-03-19 20:18 GMT+08:00 Rao, Abhishek (Nokia - IN/Bangalore) < abhishek@nokia.com>: > Hi, > > We're trying to create multiple livy sessions in parallel and then using > them. But when we

Re: Podling Report Reminder - April 2018

Thanks a lot Alex, LGTM. Best regards, Jerry 2018-03-29 4:48 GMT+08:00 Alex Bozarth : > If a mentor wants to take a look I've updated the report, as I mentioned > before it's really short this time around. > > > *Alex Bozarth* > Software Engineer > Spark Technology Center > -

About new API set to create interactive and batch session

Hi Team, In our current API design to create interactive / batch session, we assume end user could upload jars, pyFiles and related dependencies to HDFS before creating the session, and we use one POST request to create session. But usually end user may not have the permission to access the HDFS i

Re: bug in livy when jar has been uploaded

Please create a JIRA and put the issues and steps to reproduce on the JIRA. Thanks Jerry Harsch, Tim 于2018年5月26日周六 上午3:49写道： > Hi, > I posted a question on stack overflow (see link below). Livy is throwing > an error for any spark code I try. The error comes after uploading a jar > to the sh

Re: A new link request to my project and one question

Sure, I will merge the website code, thanks! For proxyUser thing, I think there's no particular reason not adding it, maybe we just forgot to add the proxyUser support. It would be better if you could create a JIRA to track this issue. If you're familiar with Livy code, you can also submit a PR a

Re: A new link request to my project and one question

Yes, has a configuration "livy.superusers". Here in this case, the sql server user should be added as a superuser, who can impersonate other different users. Marcelo Vanzin 于2018年6月26日周二 上午9:12写道： > You're talking about another service between the user and the application. > > In that case a par

Re: A new link request to my project and one question

at it allows, but it > would be better to add finer grained permissions. > > On Mon, Jun 25, 2018 at 6:30 PM, Saisai Shao > wrote: > > Yes, has a configuration "livy.superusers". Here in this case, the sql > > server user should be added as a superuser, who can impers

Re: Podling report this month

Sorry I forgot about this, will draft this today. Thanks Saisai Jean-Baptiste Onofré 于2018年7月8日周日 下午1:17写道： > Hi guys, > > we have to report this month: > > https://wiki.apache.org/incubator/July2018 > > Did someone already start a report ? I can bootstrap one if you want. > > Thanks, > Regards

Re: Podling report this month

Updated. Please review and sign off. Thanks Saisai Shao 于2018年7月9日周一 上午8:27写道： > Sorry I forgot about this, will draft this today. > > Thanks > Saisai > > Jean-Baptiste Onofré 于2018年7月8日周日 下午1:17写道： > >> Hi guys, >> >> we have to report this month:

Re: [DISCUSS] Getting rid of old stuff

+1， To support J8, Spark 2.2+ might be the only option. I'm not sure if those vendors will continue to support Spark 2.2-, but IMHO for the community release, I think moving forward would be a better choice. Thanks Saisai Jeff Zhang 于2018年9月14日周五 上午9:39写道： > +1 > > > Alex Bozarth 于2018年9月14日周

Re: Incubator Podling Report (Due 2nd January)

Can anyone please help on this? Sorry I haven't tracked the community for months. Thanks Saisai Justin Mclean 于2019年1月2日周三 下午2:14写道： > Hi, > > Just a reminder that the report is due today. [1] If you can't report this > month you will asked to report next month. > > Thanks, > Justin > > 1. http

Re: [VOTE] Move source repo to gitbox

+1 Luciano Resende 于2019年1月4日周五 上午8:26写道： > +1 > > On Thu, Jan 3, 2019 at 15:57 Marcelo Vanzin > wrote: > > > Creating a formal vote for this. I don't think we have a choice but > > they seem to request a vote anyway. This will be lazy consensus, I > > plan to create an infra ticket for the mig

Re: Making travis logs less verbose

Problem is that there's no better way to get detailed log on travis without printing in out on screen. I was struggling on it when debugging on travis. Thanks Saisai Meisam Fathi 于2019年2月9日周六 下午12:19写道： > This may do the trick for maven > > mvn -Dorg.slf4j.simpleLogger.defaultLogLevel=warn ...

Re: Making travis logs less verbose

ason why two mvn builds are >needed? > > install: - mvn $MVN_FLAG install -Dskip -DskipTests -DskipITs > -Dmaven.javadoc.skip=true -B -V > script: - mvn $MVN_FLAG verify -e > > > On Mon, Feb 11, 2019 at 5:52 PM Saisai Shao > wrote: > > > Problem is that th

Re: Podling Report Reminder - August 2019

Oh, sorry, let me check it. Also it would grateful if any mentor could sign-off the report. Thanks Saisai Justin Mclean 于2019年8月7日周三 下午3:39写道： > Hi, > > Thanks for submitting your report but I notice you didn't answer the "Have > your mentors been helpful and responsive?" question. It would be

Re: Possible missing mentor(s)

It's unfair to say there's underlying bias. Livy project is a small project, the contributor diversity may not be as rich as popular project like Spark, it is not fair to say that the contributions only limits to someones, so project is biased. There're many small Apache project which has only few

Re: Possible missing mentor(s)

ks become inactive and busy -- life > > happens, I get it. May I ask what are you folks doing to scale PR review > > and merging? Are you adding new committers? Do you feel that 2-year old > > open PRs is where you wish to be and is the right way to grow a > community? &g

Plan to cut new branch and prepare to release 0.7

Hi all, I'm planning to cut a new branch and prepare for the 0.7 release, which did lots of improvements to thrift module, I think we could make thrift module GA as for this release. Currently I'm waiting for this JIRAs to be merged before cutting the new branch. [LIVY-356][SERVER]Add LDAP authe

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

is? > > Thanks, > Marco > > Il giorno gio 10 ott 2019 alle ore 06:08 Jeff Zhang ha > scritto: > > > Make sense to me > > > > Saisai Shao 于2019年10月10日周四 下午12:04写道： > > > > > Hi all, > > > > > > I'm planning to cut a n

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

ihengw ha scritto: > Regarding the thrift server GA, > should we consider supporting recovery in > thrift server? I open a JIRA > for it > https://issues.apache.org/jira/browse/LIVY-696 > > > welcome for > discussion. > > > 原始邮件 > 发件人: Saisai Shao >

Re: Support multi-active high availability in Livy

I think it is feasible to move to next step. Let's create subtasks to track all the works. Thanks Saisai Yiheng Wang 于2019年12月10日周二 下午3:18写道： > Hi Community > > We have received some feedback for this design. Here're the open questions > for discussion > 1. Session allocation algorithm > We agr

Re: Support multi-active high availability in Livy

t; > Il giorno mer 11 dic 2019 alle ore 14:50 Saisai Shao < > sai.sai.s...@gmail.com> > ha scritto: > > > I think it is feasible to move to next step. Let's create subtasks to > track > > all the works. > > > > Thanks > > Saisai > > > &

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

+1 rei sivan 于2019年12月12日周四 下午2:09写道： > +1 > > On Thu, Dec 12, 2019, 05:30 Yiheng Wang wrote: > > > Dear Community > > > > I'd like to call a vote on LIVY-718 > > "Support > > multi-active high availability in Livy". > > > > Current

[VOTE] Release Livy 0.7.0 based on RC2

This vote is for releasing Livy 0.7.0 based on RC2 (RC1 has one unnecessary commit due to my bad). The vote will be open until Friday Dec 20, 23:59 UTC and will pass with a minimum of 3 +1 binding votes and a majority of positive votes. [+1] This release is ready to send to the Incubator PMC for

Re: [VOTE] Release Livy 0.7.0 based on RC2

api_2.10/ > livy-thriftserver/ > livy-thriftserver-session/ > minicluster-dependencies-parent/ > minicluster-dependencies_2.10/ > minicluster-dependencies_2.11/ > > ** release files* > I verify the sha512 and asc file. Both look good. > > Thanks > Yiheng > >

[VOTE] Release Livy 0.7.0 based on RC3

This vote is for releasing Livy 0.7.0 based on RC3. The vote will be open until Friday Dec 23, 23:59 UTC and will pass with a minimum of 3 +1 binding votes and a majority of positive votes. [+1] This release is ready to send to the Incubator PMC for approval [-1] This release is not ready becau

Re: [VOTE] Release Livy 0.7.0 based on RC3

I check all the jiras in the commits. > >   > > > > Thanks > > RunzhiWang > > > > > > > > -- 原始邮件 -- > > 发件人: "Saisai Shao" > 发送时间: 2019年12月18日(星期三) 中午1:58 > > 收件人: "dev" > &

Re: [VOTE] Release Livy 0.7.0 based on RC3

The date is overdue, but we still didn't receive enough votes, let me extend the due date to Dec 29, 23:59 UTC. Please help to vote. Best regards, Saisai Saisai Shao 于2019年12月20日周五 下午4:02写道： > +1 myself. > > Yiheng Wang 于2019年12月19日周四 上午11:41写道： > >> Check the re

Re: [VOTE] Release Livy 0.7.0 based on RC3

3, 2019 11:58 PM > To: dev@livy.incubator.apache.org > Subject: Re: [VOTE] Release Livy 0.7.0 based on RC3 > > +1 > > вт, 24 дек. 2019 г. в 8:11, Saisai Shao : > > > The date is overdue, but we still didn't receive enough votes, let me > > extend the due date to Dec 29,

Re: Podling Livy Report Reminder - January 2020

I will work on this. Thanks Saisai Justin Mclean 于2020年1月1日周三 下午4:06写道： > Hi, > Just a friendly reminder the report is due today is anyone working on it? > Thanks, > Justin >

Fwd: [VOTE] Release Apache Livy 0.7.0 (incubating) based on RC3

Does anyone knows how to handle license issue for fonts like below? Thanks Saisai -- Forwarded message - 发件人： Justin Mclean Date: 2020年1月3日周五 上午9:59 Subject: Re: [VOTE] Release Apache Livy 0.7.0 (incubating) based on RC3 To: Hi, +1 (binding). There’s a license issue that need

Re: Fwd: [VOTE] Release Apache Livy 0.7.0 (incubating) based on RC3

a & AI Technologies > -- > *E-mail:* *ajboz...@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 Sa

[VOTE] Release Livy 0.7.0 based on RC4

This vote is for releasing Livy 0.7.0 based on RC4. This RC mainly fixes the license issue. The vote will be open until Sunday Jan 12, 23:59 UTC and will pass with a minimum of 3 +1 binding votes and a majority of positive votes. [+1] This release is ready to send to the Incubator PMC for appro

Re: [VOTE] Release Livy 0.7.0 based on RC4

My +1 of course. Saisai Shao 于2020年1月7日周二 下午9:25写道： > This vote is for releasing Livy 0.7.0 based on RC4. > > This RC mainly fixes the license issue. > > The vote will be open until Sunday Jan 12, 23:59 UTC and > will pass with a minimum of 3 +1 binding votes and a majority o

Re: Livy metrics

Currently we don't have concrete plan on this, it would be great if you could contribute on this. Thanks Saisai Shanyu Zhao 于2020年1月10日周五 上午8:44写道： > Hi, > > Are there ongoing effort to add Livy metrics? I saw that dropwizard is > added as dependency in pom.xml but didn't see it get used anywhe

Re: .NET for Apache Spark interactive interpreter support

Is this just a wrapper of Livy REST API, or it could support Livy Job API? >From my opinion, if it is just a wrapper of REST API, then it would be better to maintain out of Livy, since REST API is language independent, if we're going to have all the languages support in Livy, then it is hard to ma

  1   2   >