Re: [VOTE] Release Livy 0.7.0 based on RC3

19 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, 23:59 UTC.

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 release

Re: [VOTE] Release Livy 0.7.0 based on RC3

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

[jira] [Updated] (LIVY-727) Session state always be idle though the yarn application has been killed after restart livy.

[ https://issues.apache.org/jira/browse/LIVY-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao updated LIVY-727: - Affects Version/s: 0.7.0 0.6.0 > Session state always be idle though the y

[jira] [Resolved] (LIVY-727) Session state always be idle though the yarn application has been killed after restart livy.

[ https://issues.apache.org/jira/browse/LIVY-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-727. -- Fix Version/s: 0.8.0 Assignee: runzhiwang Resolution: Fixed Issue resolved by pull

[jira] [Resolved] (LIVY-729) Livy should not recover the killed session

[ https://issues.apache.org/jira/browse/LIVY-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-729. -- Fix Version/s: 0.8.0 Assignee: runzhiwang Resolution: Fixed Issue resolved by pull

Re: [VOTE] Release Livy 0.7.0 based on RC2

> 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 > > On

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". > > > >

Re: Support multi-active high availability in Livy

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 > > > > Yiheng Wang

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

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

w 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: Enabling fully disaggregated shuffle on Spark

Hi Ben and Felix, I'm also interested in this. Would you please add me to the invite, thanks a lot. Best regards, Saisai Greg Lee 于2019年12月2日周一 下午11:34写道： > Hi Felix & Ben, > > This is Li Hao from Baidu, same team with Linhong. > > As mentioned in Linhong’s email, independent disaggregated

[jira] [Resolved] (LIVY-717) Specify explicit ZooKeeper version in maven

[ https://issues.apache.org/jira/browse/LIVY-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-717. -- Fix Version/s: 0.7.0 Assignee: Mate Szalay-Beko Resolution: Fixed Issue resolved by pull

[jira] [Resolved] (LIVY-714) Cannot remove the app in leakedAppTags when timeout

[ https://issues.apache.org/jira/browse/LIVY-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-714. -- Fix Version/s: 0.7.0 Assignee: runzhiwang Resolution: Fixed Issue resolved by pull

Re: Iceberg in Spark 3.0.0

t; >> +1 for Iceberg branch >> >> Thanks for the contribution from you and your team! >> >> On Fri, Nov 22, 2019 at 8:29 AM Anton Okolnychyi >> wrote: >> >>> +1 on having a branch in Iceberg as we have for vectorized reads. >>> >

Re: Query about the semantics of "overwrite" in Iceberg

se Spark will choose its behavior and correctly > configure the source with a dynamic overwrite or an overwrite using an > expression. > > On Thu, Nov 21, 2019 at 11:33 PM Saisai Shao > wrote: > >> Hi Team, >> >> I found that Iceberg's "overwrite" is dif

Query about the semantics of "overwrite" in Iceberg

Hi Team, I found that Iceberg's "overwrite" is different from Spark's built-in sources like Parquet. The "overwrite" semantics in Iceberg seems more like "upsert", but not deleting the partitions where new data doesn't contain. I would like to know what is the purpose of such design choice? Also

[jira] [Resolved] (LIVY-715) The configuration in the livy.conf.template is inconsistent with LivyConf.scala

[ https://issues.apache.org/jira/browse/LIVY-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-715. -- Fix Version/s: 0.7.0 Resolution: Fixed Issue resolved by pull request 261 https://github.com

Re: Iceberg in Spark 3.0.0

that they community could review and contribute on it. I would like to hear your suggestions. Best regards, Saisai Ryan Blue 于2019年11月20日周三 上午1:27写道： > Sounds great, thanks Saisai! > > On Mon, Nov 18, 2019 at 3:29 AM Saisai Shao > wrote: > >> Thanks Anton, I will

Re: Iceberg in Spark 3.0.0

t; > - Anton > > > On 18 Nov 2019, at 02:08, Saisai Shao wrote: > > Hi Anton, > > Thanks to bring this out. We already have a branch building against Spark > 3.0 (Master branch actually) internally, and we're actively working on it. > I think it is a good idea to create an u

Re: Iceberg in Spark 3.0.0

Hi Anton, Thanks to bring this out. We already have a branch building against Spark 3.0 (Master branch actually) internally, and we're actively working on it. I think it is a good idea to create an upstream Spark 3.0 branch, we could share it if the community would like to do so. Best regards,

[jira] [Resolved] (LIVY-707) Add audit log for SqlJobs from ThriftServer

[ https://issues.apache.org/jira/browse/LIVY-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-707. -- Fix Version/s: 0.7.0 Assignee: Hui An Resolution: Fixed Issue resolved by pull request

[jira] [Updated] (LIVY-711) Travis fails to build on Ubuntu16.04

[ https://issues.apache.org/jira/browse/LIVY-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao updated LIVY-711: - Component/s: Build > Travis fails to build on Ubuntu16

Re: livy and security concerns

Livy is just a gateway service, I think it is not Livy's responsibility to provide a sandbox. Also it is super hard to analyze the code from Livy side. Typically some companies will provide a sand-boxing runtime, like JVM or others, or put Spark into container for security and isolation. Thanks

Re: [VOTE] Accept TubeMQ into the Apache Incubator

+1 (non-binding). Thanks Saisai Sheng Wu 于2019年10月30日周三 上午10:03写道： > +1 binding > Good luck. > > Dave Fisher 于2019年10月30日 周三上午7:30写道： > > > +1 (binding) > > > > Go TubeMQ. > > > > Regards, > > Dave > > > > Sent from my iPhone > > > > > On Oct 29, 2019, at 6:48 PM, David Nalley wrote: > > > >

[jira] [Resolved] (LIVY-697) Rsc client cannot resolve the hostname of driver in yarn-cluster mode

[ https://issues.apache.org/jira/browse/LIVY-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-697. -- Fix Version/s: 0.7.0 Assignee: runzhiwang Resolution: Fixed Issue resolved by pull

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

, > 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 new branch and prepare for

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

[jira] [Assigned] (LIVY-690) Exclude curator in thrift server pom to avoid conflict jars

[ https://issues.apache.org/jira/browse/LIVY-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao reassigned LIVY-690: Assignee: Yiheng Wang > Exclude curator in thrift server pom to avoid conflict j

[jira] [Resolved] (LIVY-690) Exclude curator in thrift server pom to avoid conflict jars

[ https://issues.apache.org/jira/browse/LIVY-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-690. -- Resolution: Fixed Issue resolved by pull request 239 [https://github.com/apache/incubator-livy/pull/239

[jira] [Assigned] (LIVY-688) Error message of LivyClient only keep outer stackTrace but discard cause's stackTrace

[ https://issues.apache.org/jira/browse/LIVY-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao reassigned LIVY-688: Assignee: weiwenda > Error message of LivyClient only keep outer stackTrace but discard caus

[jira] [Resolved] (LIVY-658) RSCDriver should catch exception if cancel job failed during shutdown

[ https://issues.apache.org/jira/browse/LIVY-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-658. -- Fix Version/s: 0.7.0 Assignee: Jeffrey(Xilang) Yan Resolution: Fixed Issue resolved

[jira] [Resolved] (LIVY-644) Flaky test: Failed to execute goal org.jacoco:jacoco-maven-plugin:0.8.2:report-aggregate (jacoco-report) on project livy-coverage-report

[ https://issues.apache.org/jira/browse/LIVY-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-644. -- Fix Version/s: 0.7.0 Assignee: Yiheng Wang Resolution: Fixed Issue resolved by pull

[jira] [Resolved] (SPARK-29112) Expose more details when ApplicationMaster reporter faces a fatal exception

[ https://issues.apache.org/jira/browse/SPARK-29112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved SPARK-29112. - Fix Version/s: 3.0.0 Assignee: Lantao Jin Resolution: Fixed Issue resolved

[jira] [Resolved] (LIVY-657) Travis failed on should not create sessions with duplicate names

[ https://issues.apache.org/jira/browse/LIVY-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-657. -- Fix Version/s: 0.7.0 Assignee: runzhiwang Resolution: Fixed Issue resolved by pull

[jira] [Commented] (LIVY-666) Support named interpreter groups

[ https://issues.apache.org/jira/browse/LIVY-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931976#comment-16931976 ] Saisai Shao commented on LIVY-666: -- I think it looks good to me. With the above, I think the REST APIs

[jira] [Resolved] (LIVY-633) session should not be gc-ed for long running queries

[ https://issues.apache.org/jira/browse/LIVY-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-633. -- Fix Version/s: 0.7.0 Assignee: Yiheng Wang Resolution: Fixed Issue resolved by pull

[jira] [Updated] (SPARK-29114) Dataset.coalesce(10) throw ChunkFetchFailureException when original Dataset size is big

[ https://issues.apache.org/jira/browse/SPARK-29114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao updated SPARK-29114: Priority: Major (was: Blocker) > Dataset.coalesce(10) throw ChunkFetchFailureException w

[jira] [Resolved] (LIVY-647) Travis failed on "batch session should not be gc-ed until application is finished"

[ https://issues.apache.org/jira/browse/LIVY-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-647. -- Fix Version/s: 0.7.0 Assignee: runzhiwang Resolution: Fixed Issue resolved by pull

[jira] [Commented] (SPARK-29038) SPIP: Support Spark Materialized View

[ https://issues.apache.org/jira/browse/SPARK-29038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927265#comment-16927265 ] Saisai Shao commented on SPARK-29038: - [~cltlfcjin] I think we need a SPIP review and vote

[jira] [Commented] (SPARK-29038) SPIP: Support Spark Materialized View

[ https://issues.apache.org/jira/browse/SPARK-29038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927263#comment-16927263 ] Saisai Shao commented on SPARK-29038: - IIUC, I think the key difference between MV and Spark's built

Re: Welcoming some new committers and PMC members

Congratulations! Jungtaek Lim 于2019年9月9日周一 下午6:11写道： > Congratulations! Well deserved! > > On Tue, Sep 10, 2019 at 9:51 AM John Zhuge wrote: > >> Congratulations! >> >> On Mon, Sep 9, 2019 at 5:45 PM Shane Knapp wrote: >> >>> congrats everyone! :) >>> >>> On Mon, Sep 9, 2019 at 5:32 PM Matei

[jira] [Resolved] (LIVY-659) Travis failed on "can kill spark-submit while it's running"

[ https://issues.apache.org/jira/browse/LIVY-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-659. -- Fix Version/s: 0.7.0 Assignee: runzhiwang Resolution: Fixed Issue resolved by pull

Question about schema evolution and partition spec evolution

Hi team, I have some newbie questions about schema evolution and partition evolution. From the design spec, Iceberg supports schema evolution and partition spec evolution, my questions are: 1. If a new column is added, are we going to rewrite the whole data, if not how do we support it? 2. Do we

[jira] [Resolved] (LIVY-645) Add Name, Owner, Proxy User to web UI

[ https://issues.apache.org/jira/browse/LIVY-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-645. -- Fix Version/s: 0.7.0 Assignee: Jeffrey(Xilang) Yan Resolution: Fixed Issue resolved

[jira] [Reopened] (SPARK-19147) netty throw NPE

[ https://issues.apache.org/jira/browse/SPARK-19147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao reopened SPARK-19147: - > netty throw NPE > --- > > Key: SPARK-19147 >

[jira] [Commented] (SPARK-19147) netty throw NPE

[ https://issues.apache.org/jira/browse/SPARK-19147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16923014#comment-16923014 ] Saisai Shao commented on SPARK-19147: - Yes, we also met the similar issue when executor is stopping

[jira] [Resolved] (LIVY-519) Flaky test: SparkYarnApp "should kill yarn app "

[ https://issues.apache.org/jira/browse/LIVY-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-519. -- Fix Version/s: 0.7.0 Assignee: runzhiwang Resolution: Fixed Issue resolved by pull

Re: New committer and PPMC member, Anton Okolnychyi

Congrats Anton! Best regards, Saisai Daniel Weeks 于2019年9月3日周二 上午7:48写道： > Congrats Anton! > > On Fri, Aug 30, 2019 at 1:54 PM Edgar Rodriguez > wrote: > >> Nice! Congratulations, Anton! >> >> Cheers, >> >> On Fri, Aug 30, 2019 at 1:42 PM Dongjoon Hyun >> wrote: >> >>> Congratulations,

Re: Possible missing mentor(s)

nd 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? > > > > -s

[jira] [Resolved] (LIVY-586) When a batch fails on startup, Livy continues to report the batch as "starting", even though it has failed

[ https://issues.apache.org/jira/browse/LIVY-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-586. -- Fix Version/s: 0.7.0 Assignee: runzhiwang Resolution: Fixed Issue resolved by pull

[jira] [Resolved] (LIVY-642) A rare status happened in yarn cause SparkApp change into error state

[ https://issues.apache.org/jira/browse/LIVY-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-642. -- Fix Version/s: 0.7.0 Assignee: Zhefeng Wang Resolution: Fixed Issue resolved by pull

[jira] [Commented] (SPARK-28340) Noisy exceptions when tasks are killed: "DiskBlockObjectWriter: Uncaught exception while reverting partial writes to file: java.nio.channels.ClosedByInterruptException

[ https://issues.apache.org/jira/browse/SPARK-28340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918386#comment-16918386 ] Saisai Shao commented on SPARK-28340: - My simple concern is that there may be other places which

[jira] [Commented] (SPARK-28340) Noisy exceptions when tasks are killed: "DiskBlockObjectWriter: Uncaught exception while reverting partial writes to file: java.nio.channels.ClosedByInterruptException

[ https://issues.apache.org/jira/browse/SPARK-28340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918306#comment-16918306 ] Saisai Shao commented on SPARK-28340: - We also saw a bunch of exceptions in our production

[jira] [Assigned] (LIVY-616) Livy Server discovery

[ https://issues.apache.org/jira/browse/LIVY-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao reassigned LIVY-616: Assignee: Saisai Shao > Livy Server discovery > - > >

[jira] [Commented] (LIVY-616) Livy Server discovery

[ https://issues.apache.org/jira/browse/LIVY-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917755#comment-16917755 ] Saisai Shao commented on LIVY-616: -- [~oshevchenko] we don't typically assign the jira ourselves

[jira] [Assigned] (LIVY-616) Livy Server discovery

[ https://issues.apache.org/jira/browse/LIVY-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao reassigned LIVY-616: Assignee: (was: Oleksandr Shevchenko) > Livy Server discov

[jira] [Resolved] (LIVY-617) Livy session leak on Yarn when creating session duplicated names

[ https://issues.apache.org/jira/browse/LIVY-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-617. -- Fix Version/s: 0.7.0 Assignee: shanyu zhao Resolution: Fixed Issue resolved by pull

[jira] [Comment Edited] (LIVY-641) Travis failed on "should end with status dead when batch session exits with no 0 return code"

[ https://issues.apache.org/jira/browse/LIVY-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916318#comment-16916318 ] Saisai Shao edited comment on LIVY-641 at 8/27/19 3:58 AM: --- Issue resolved

[jira] [Resolved] (LIVY-641) Travis failed on "should end with status dead when batch session exits with no 0 return code"

[ https://issues.apache.org/jira/browse/LIVY-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-641. -- Fix Version/s: 0.7.0 Assignee: jiewang Resolution: Fixed Issue resolved by pull request

[jira] [Commented] (LIVY-639) Is it possible to add start time and completion time and duration to the statements web ui interface?

[ https://issues.apache.org/jira/browse/LIVY-639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916306#comment-16916306 ] Saisai Shao commented on LIVY-639: -- Issue resolved by pull request 201 https://github.com/apache/incubator

[jira] [Resolved] (LIVY-639) Is it possible to add start time and completion time and duration to the statements web ui interface?

[ https://issues.apache.org/jira/browse/LIVY-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-639. -- Fix Version/s: 0.7.0 Resolution: Fixed > Is it possible to add start time and completion t

[jira] [Assigned] (LIVY-648) Wrong return message in cancel statement documentation

[ https://issues.apache.org/jira/browse/LIVY-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao reassigned LIVY-648: Assignee: Oleksandr Shevchenko > Wrong return message in cancel statement documentat

[jira] [Resolved] (LIVY-648) Wrong return message in cancel statement documentation

[ https://issues.apache.org/jira/browse/LIVY-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-648. -- Fix Version/s: 0.7.0 Resolution: Fixed Issue resolved by pull request 210 [https://github.com

[jira] [Updated] (SPARK-28849) Spark's UnsafeShuffleWriter may run into infinite loop in transferTo occasionally

[ https://issues.apache.org/jira/browse/SPARK-28849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao updated SPARK-28849: Description: Spark's {{UnsafeShuffleWriter}} may run into infinite loop when calling

[jira] [Updated] (SPARK-28849) Spark's UnsafeShuffleWriter may run into infinite loop in transferTo occasionally

[ https://issues.apache.org/jira/browse/SPARK-28849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao updated SPARK-28849: Description: Spark's {{UnsafeShuffleWriter}} may run into infinite loop when calling

[jira] [Updated] (SPARK-28849) Spark's UnsafeShuffleWriter may run into infinite loop in transferTo occasionally

[ https://issues.apache.org/jira/browse/SPARK-28849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao updated SPARK-28849: Description: Spark's {{UnsafeShuffleWriter}} may run into infinite loop when calling

[jira] [Updated] (SPARK-28849) Spark's UnsafeShuffleWriter may run into infinite loop in transferTo occasionally

[ https://issues.apache.org/jira/browse/SPARK-28849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao updated SPARK-28849: Description: Spark's {{UnsafeShuffleWriter}} may run into infinite loop when calling

[jira] [Updated] (SPARK-28849) Spark's UnsafeShuffleWriter may run into infinite loop in transferTo occasionally

[ https://issues.apache.org/jira/browse/SPARK-28849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao updated SPARK-28849: Description: Spark's {{UnsafeShuffleWriter}} may run into infinite loop when calling

[jira] [Updated] (SPARK-28849) Spark's UnsafeShuffleWriter may run into infinite loop in transferTo occasionally

[ https://issues.apache.org/jira/browse/SPARK-28849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao updated SPARK-28849: Description: Spark's {{UnsafeShuffleWriter}} may run into infinite loop when calling

[jira] [Updated] (SPARK-28849) Spark's UnsafeShuffleWriter may run into infinite loop in transferTo occasionally

[ https://issues.apache.org/jira/browse/SPARK-28849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao updated SPARK-28849: Attachment: D18F4.png 95330.png 91ADA.png > Spar

[jira] [Updated] (SPARK-28849) Spark's UnsafeShuffleWriter may run into infinite loop in transferTo occasionally

[ https://issues.apache.org/jira/browse/SPARK-28849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao updated SPARK-28849: Description: Spark's {{UnsafeShuffleWriter}} may run into infinite loop when calling

[jira] [Created] (SPARK-28849) Spark's UnsafeShuffleWriter may run into infinite loop in transferTo occasionally

Saisai Shao created SPARK-28849: --- Summary: Spark's UnsafeShuffleWriter may run into infinite loop in transferTo occasionally Key: SPARK-28849 URL: https://issues.apache.org/jira/browse/SPARK-28849

[jira] [Resolved] (LIVY-637) get NullPointerException when create database using thriftserver

[ https://issues.apache.org/jira/browse/LIVY-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-637. -- Fix Version/s: 0.7.0 Resolution: Fixed > get NullPointerException when create database us

[jira] [Commented] (LIVY-637) get NullPointerException when create database using thriftserver

[ https://issues.apache.org/jira/browse/LIVY-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16913001#comment-16913001 ] Saisai Shao commented on LIVY-637: -- Issue resolved by pull request 200 https://github.com/apache/incubator

[jira] [Closed] (LIVY-591) ACLs enforcement should occur on both session owner and proxy user

[ https://issues.apache.org/jira/browse/LIVY-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao closed LIVY-591. Resolution: Duplicate > ACLs enforcement should occur on both session owner and proxy u

[jira] [Resolved] (LIVY-592) Proxy user cannot view its session log

[ https://issues.apache.org/jira/browse/LIVY-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-592. -- Fix Version/s: 0.7.0 Assignee: Yiheng Wang Resolution: Fixed > Proxy user cannot v

[jira] [Commented] (LIVY-592) Proxy user cannot view its session log

[ https://issues.apache.org/jira/browse/LIVY-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16912875#comment-16912875 ] Saisai Shao commented on LIVY-592: -- Issue resolved by pull request 202 https://github.com/apache/incubator

Re: Are we going to use Apache JIRA instead of Github issues

n). I'm just one vote, though, so if most people >> prefer to move to JIRA I'm open to it. >> >> What do you think is missing compared to JIRA? >> >> On Fri, Aug 16, 2019 at 3:09 AM Saisai Shao >> wrote: >> >>> Hi Team, >>> >>> Seems

Re: Release Spark 2.3.4

+1 Wenchen Fan 于2019年8月19日周一 上午10:28写道： > +1 > > On Sat, Aug 17, 2019 at 3:37 PM Hyukjin Kwon wrote: > >> +1 too >> >> 2019년 8월 17일 (토) 오후 3:06, Dilip Biswal 님이 작성: >> >>> +1 >>> >>> Regards, >>> Dilip Biswal >>> Tel: 408-463-4980 >>> dbis...@us.ibm.com >>> >>> >>> >>> - Original message

Are we going to use Apache JIRA instead of Github issues

Hi Team, Seems Iceberg project uses Github issues instead of JIRA. IMHO JIRA is more powerful and easy to manage, most of the Apache projects use JIRA to track everything, any plan to move to JIRA or we stick on using Github issues? Thanks Saisai

[jira] [Assigned] (LIVY-625) Implement GetFunctions metadata operation

[ https://issues.apache.org/jira/browse/LIVY-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao reassigned LIVY-625: Assignee: Yiheng Wang > Implement GetFunctions metadata operat

[jira] [Updated] (LIVY-575) Implement missing metadata operations

[ https://issues.apache.org/jira/browse/LIVY-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao updated LIVY-575: - Priority: Major (was: Minor) > Implement missing metadata operati

[jira] [Assigned] (LIVY-622) Implement GetSchemas metadata operation

[ https://issues.apache.org/jira/browse/LIVY-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao reassigned LIVY-622: Assignee: Yiheng Wang > Implement GetSchemas metadata operat

[jira] [Resolved] (LIVY-625) Implement GetFunctions metadata operation

[ https://issues.apache.org/jira/browse/LIVY-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-625. -- Resolution: Fixed Fix Version/s: 0.7.0 Issue resolved by pull request 194 [https://github.com

[jira] [Resolved] (LIVY-624) Implement GetColumns metadata operation

[ https://issues.apache.org/jira/browse/LIVY-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-624. -- Resolution: Fixed Fix Version/s: 0.7.0 Issue resolved by pull request 194 [https://github.com

[jira] [Resolved] (LIVY-623) Implement GetTables metadata operation

[ https://issues.apache.org/jira/browse/LIVY-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-623. -- Resolution: Fixed Fix Version/s: 0.7.0 Issue resolved by pull request 194 [https://github.com

[jira] [Updated] (LIVY-635) Travis failed to build

[ https://issues.apache.org/jira/browse/LIVY-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao updated LIVY-635: - Component/s: Build > Travis failed to build > -- > > K

[jira] [Assigned] (LIVY-635) Travis failed to build

[ https://issues.apache.org/jira/browse/LIVY-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao reassigned LIVY-635: Assignee: jiewang > Travis failed to build > -- > >

[jira] [Resolved] (LIVY-635) Travis failed to build

[ https://issues.apache.org/jira/browse/LIVY-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-635. -- Resolution: Fixed Fix Version/s: 0.7.0 Issue resolved by pull request 198 [https://github.com

[jira] [Assigned] (LIVY-620) Spark batch session always ends with success when configuration is master yarn and deploy-mode client

[ https://issues.apache.org/jira/browse/LIVY-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao reassigned LIVY-620: Assignee: Gustavo Martin > Spark batch session always ends with success when configurat

[jira] [Resolved] (LIVY-620) Spark batch session always ends with success when configuration is master yarn and deploy-mode client

[ https://issues.apache.org/jira/browse/LIVY-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-620. -- Resolution: Fixed Fix Version/s: 0.7.0 Issue resolved by pull request 192 [https://github.com

[jira] [Commented] (LIVY-616) Livy Server discovery

[ https://issues.apache.org/jira/browse/LIVY-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16906098#comment-16906098 ] Saisai Shao commented on LIVY-616: -- I will spend time on the PR itself, but I'm a little busy these days

[jira] [Commented] (LIVY-616) Livy Server discovery

[ https://issues.apache.org/jira/browse/LIVY-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905734#comment-16905734 ] Saisai Shao commented on LIVY-616: -- I don't have the objections about it, just thinking about how to use

[jira] [Commented] (LIVY-616) Livy Server discovery

[ https://issues.apache.org/jira/browse/LIVY-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16904922#comment-16904922 ] Saisai Shao commented on LIVY-616: -- Yes, I was asking how to use HTTP request directly, do you have

[jira] [Commented] (LIVY-616) Livy Server discovery

[ https://issues.apache.org/jira/browse/LIVY-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16904908#comment-16904908 ] Saisai Shao commented on LIVY-616: -- I think I was asking if user directly using REST API, not Livy JobAPI

Re: Creating session in livy with jars parameter

r example) - session is > in *IDLE* status > >> {"kind":"spark", "jars":["local:/path_to_guava_jar/guava.jar"]} > > > I don't understand what can be the difference between my jar and some > other jars... > > On Sun, Aug 11, 2019 at

Re: Creating session in livy with jars parameter

Would you mind listing the steps to reproduce your issue, and how do you use REST APIs? Thanks Saisai Pavel Sivak 于2019年8月10日周六 上午11:01写道： > Hi, > My idea is to create livy session with my library in class path using > "jars" parameter. > I'm using REST API to create a session. After sending

Re: Pre-registering UDTs / UDFs in Livy session

Unfortunately there's no such mechanism to inject custom code when session is started in Livy side. I think you can add some code in Spark side, Spark has a listener hook "SparkListener", in which there has a hook ` onApplicationStart`, this hook will be called immediately after application is

[jira] [Assigned] (LIVY-547) Livy kills session after livy.server.session.timeout even if the session is active

[ https://issues.apache.org/jira/browse/LIVY-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao reassigned LIVY-547: Assignee: shanyu zhao > Livy kills session after livy.server.session.timeout even if the sess

<    1   2   3   4   5   6   7   8   9   10   >