+1 (binding)
[x] incubating in name
[x] signature and hash fine
[x] DISCLAIMER is fine
[x] LICENSE and NOTICE are fine
[x] No unexpected binary files
[x] All source files have ASF headers
[x] Can be built from source
Best,
Jerry
Felix Cheung 于2022年12月8日周四 09:05写道：
> +1 (binding)
>
> -
[
https://issues.apache.org/jira/browse/HUDI-4193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saisai Shao updated HUDI-4193:
--
Affects Version/s: 0.12.0
> Fail to compile in osx aarch_64 environm
Saisai Shao created HUDI-4193:
-
Summary: Fail to compile in osx aarch_64 environment
Key: HUDI-4193
URL: https://issues.apache.org/jira/browse/HUDI-4193
Project: Apache Hudi
Issue Type: Bug
Thanks Justin for the explanation.
We discussed internally and think that a new name would be better to avoid
potential issue.
Will figure out a new name.
Best regards,
Jerry
Justin Mclean 于2022年5月23日周一 20:29写道：
> Hi,
>
> > There’s a typo in this paragraph that makes it impossible to
> >
I see, thanks Justin and Daniel for your inputs.
Best regards,
Jerry
Daniel Widdis 于2022年5月23日周一 11:32写道：
> Adding onto this, even if there may be no legal trademark issue, there is
> other software by this name which makes it less than desirable. Quoted
> from [1]
>
> > Avoiding
Thanks Willem for organizing, thanks Yu to join and have this open
discussion.
We have made a consensus that both projects developing separately, and seek
the opportunity to collaborate in future. So +1 from my side.
Back to the merging or separation discussion, I think both ways have pros
and
Thanks Weiwei, let me add you to the mentor list.
Best regards,
Jerry
Weiwei Yang 于2022年5月17日周二 12:18写道：
> +1
> This is an interesting project, I'd be happy to help the project's
> incubation process.
> Let me know if you need my help, Thanks
>
> On Mon, May 16, 2022 at 8
Got it, thanks a lot Justin.
Best regards,
Jerry
Justin Mclean 于2022年5月17日周二 10:59写道：
> Hi,
>
> The new project name doesn’t need to be a registered trademark, but you
> would still need to pick a name that is now likely to have any trademark
> issues.
>
> The project may want to get the ASF
SF before graduation), or just a new suitable name
(without registration) is enough for incubation?
Best regards,
Jerry
Saisai Shao 于2022年5月17日周二 10:01写道：
> Thanks Daniel and Justin, let me resolve the naming issue first.
>
> Best regards,
> Jerry
>
> Justin Mclean 于2022年5月
Thanks Daniel and Justin, let me resolve the naming issue first.
Best regards,
Jerry
Justin Mclean 于2022年5月17日周二 09:52写道：
> Hi,
>
> > Thanks for your reply. The trademark "firestorm" as a software has
> already
> > been submitted the registration by Tencent in China, I'm not sure is that
> >
Hi Daniel and Justin,
Thanks for your reply. The trademark "firestorm" as a software has already
been submitted the registration by Tencent in China, I'm not sure is that
enough or not.
Is there any guidance in ASF about naming or trademark things? I will
consult this to our company lawyer.
>From Dev's point, it has less burden to always support the latest version
of Spark (for example). But from user's point, especially for us who
maintain Spark internally, it is not easy to upgrade the Spark version for
the first time (since we have many customizations internally), and we're
still
+1 (binding)
Best,
Saisai
Willem Jiang 于2021年7月29日周四 上午7:59写道：
> +1 (binding)
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, Jul 26, 2021 at 11:12 PM 俊平堵 wrote:
> >
> > Dear all,
> >
> >
> > Following up the [DISCUSS] thread on Linkis[1], I would like to call a
> >
+1 (binding)
Checked: signatures，LICENSE and NOTICE files，DISCLAIMER，ASF header. LGTM.
Thanks!
Saisai
Jean-Baptiste Onofre 于2021年7月21日周三 下午1:22写道：
> +1 (binding)
>
> Checked:
> - incubating in the name
> - signatures OK
> - LICENSE and NOTICE files look good
> - DISCLAIMER file is there
> -
Yes, Livy supports Spark 3.0 + Scala 2.12 in the master branch. But it
doesn't have a lot of tests, I expect there're some issues in it.
Ashish Agarwal 于2021年4月19日周一 下午2:01写道：
> Thanks Renat I saw that "https://issues.apache.org/jira/browse/LIVY-756;
> is fixed for version 0.8.0.
>
> Any idea
+1 binding.
Checked license file, ASC and SHA512, LGTM.
Best regards,
Sasisai
Goson zhang 于2021年2月26日周五 上午9:40写道：
> Hi all:
>
> We need your help, can anyone help us to review this release?
>
> The release of this version has lasted for more than a month, and many
> changes have been delayed
[
https://issues.apache.org/jira/browse/LIVY-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saisai Shao closed LIVY-833.
Resolution: Won't Fix
> Livy allows users to see password in config files
> (spark.ssl.keyPa
[
https://issues.apache.org/jira/browse/LIVY-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289457#comment-17289457
]
Saisai Shao commented on LIVY-833:
--
This is the problem of Spark, not Livy. Spark uses the configuration
t;
> Regards
> JB
>
> > Le 7 févr. 2021 à 02:50, Saisai Shao a écrit :
> >
> > The Livy PPMC has voted to release Livy 0.7.1 RC1 as the next Livy
> release.
> >
> > Livy enables programmatic, fault-tolerant, multi-tenant submission of
> > Spark jobs
My +1 as well. Please help to vote.
Thanks
Saisai
Justin Mclean 于2021年2月8日周一 上午9:36写道：
> Hi,
>
> +1 (binding)
>
> I checked in the source release:
> - incubating in name
> - signatures and hashes correct
> - NOTICE file is incorrect, please don’t say "Copyright 2018 and onwards”
> but include
The Livy PPMC has voted to release Livy 0.7.1 RC1 as the next Livy release.
Livy enables programmatic, fault-tolerant, multi-tenant submission of
Spark jobs from web/mobile apps (no Spark client needed). So, multiple
users can interact with your Spark cluster concurrently and reliably.
Vote
t;
> >
> > 505 Howard Street
> > San Francisco, CA 94105
> > United States
> >
> >
> >
> > [image: Inactive hide details for Saisai Shao ---02/03/2021 09:44:31
> > PM---This vote is for releasing Livy 0.7.1 based on RC1. The vote]Saisai
> > S
This vote is for releasing Livy 0.7.1 based on RC1.
The vote will be open until Feb 10 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 because...
zhangli...@apache.org 于2020年11月23日周一 下午8:09写道：
> Hi Jerry,
>
> It is better to discuss it in TubeMQ dev mail list first.
>
> --
>
> Sincerely,
> Liang Zhang (John)
> Apache ShardingSphere
>
>
> Saisai Shao 于2020年11月23日周一 上午10:38写道：
>
&
The podling project is Apache TubeMQ. Currently the project is planning to
change the name, but haven't yet figured out a new name, neither did a
podling name search. Just want to understand what is the process.
CC @general@incubator.apache.org
Thanks
Jerry
Dave Fisher 于2020年11月23日周一
t; FileSystem works great and is probably the easiest way to maintain an
> implementation for the object store.
>
> On Thu, Nov 12, 2020 at 7:31 PM Saisai Shao
> wrote:
>
>> Hi all,
>>
>> Sorry to chime in, I also have a same concern about using Iceberg with
>> Objec
Hi all,
Sorry to chime in, I also have a same concern about using Iceberg with
Object storage.
One of my concerns with S3FileIO is getting tied too much to a single
> cloud provider. I'm wondering if an ObjectStoreFileIO would be helpful
> so that S3FileIO and (a future) GCSFileIO could share
[
https://issues.apache.org/jira/browse/SPARK-13704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saisai Shao updated SPARK-13704:
Description:
In some cases, TaskSchedulerImpl.createTaskSetManager can be expensive. For
example
Would like to get structured streaming reader in in the next release :).
Will spend time on addressing new feedbacks.
Thanks
Saisai
Mass Dosage 于2020年8月27日周四 下午10:36写道：
> I'm all for a release. The only thing still required for basic Hive read
> support (other than documentation of course!) is
+1 for the changes.
Mass Dosage 于2020年8月20日周四 下午5:46写道：
> +1 for `iceberg-hive-metastore` as I found this confusing when I first
> started working with the code.
>
> On Thu, 20 Aug 2020 at 03:27, Jungtaek Lim
> wrote:
>
>> +1 for `iceberg-hive-metastore` and also +1 for RD's proposal.
>>
>>
Congrats!
Thanks
Saisai
OpenInx 于2020年7月23日周四 上午10:06写道：
> Congratulations !
>
> On Thu, Jul 23, 2020 at 9:31 AM Jingsong Li
> wrote:
>
>> Congratulations Shardul! Well deserved!
>>
>> Best,
>> Jingsong
>>
>> On Thu, Jul 23, 2020 at 7:27 AM Anton Okolnychyi
>> wrote:
>>
>>> Congrats and
Hi,
I just merged the Spark 3 support yesterday, I would wait for most tests to
stabilize this feature. In the meanwhile, you can build the master branch
yourself to try this latest feature.
Thanks
Saisai
Aliaksandr Sasnouskikh 于2020年7月2日周四 下午10:50写道：
> Hi, thanks for notifying about the
[
https://issues.apache.org/jira/browse/LIVY-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saisai Shao closed LIVY-593.
Fix Version/s: 0.8.0
Resolution: Duplicate
> Adding Scala 2.12 supp
[
https://issues.apache.org/jira/browse/LIVY-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saisai Shao closed LIVY-562.
Fix Version/s: 0.8.0
Resolution: Duplicate
> Add support of scala 2
[
https://issues.apache.org/jira/browse/LIVY-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saisai Shao resolved LIVY-423.
--
Fix Version/s: 0.8.0
Assignee: Thomas Prelle
Resolution: Fixed
Issue resolved by pull
[
https://issues.apache.org/jira/browse/LIVY-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saisai Shao resolved LIVY-756.
--
Fix Version/s: 0.8.0
Assignee: Thomas Prelle
Resolution: Fixed
> Add spark 3 supp
[
https://issues.apache.org/jira/browse/LIVY-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17150037#comment-17150037
]
Saisai Shao commented on LIVY-756:
--
Issue resolved by pull request 300
https://github.com/apache/incubator
Hi team,
Any plan to get this Structured Streaming Read support (
https://github.com/apache/iceberg/pull/796) in 0.9.0 release? Would be
appreciated anyone can take a review. Thanks!
Best regards,
Saisai
Ryan Blue 于2020年6月23日周二 上午6:42写道：
> Hi everyone,
>
> I just posted my notes from the
+1 for graduation.
Junjie Chen 于2020年5月13日周三 上午9:33写道：
> +1
>
> On Wed, May 13, 2020 at 8:07 AM RD wrote:
>
>> +1 for graduation!
>>
>> On Tue, May 12, 2020 at 3:50 PM John Zhuge wrote:
>>
>>> +1
>>>
>>> On Tue, May 12, 2020 at 3:33 PM parth brahmbhatt <
>>> brahmbhatt.pa...@gmail.com> wrote:
> On 2020/03/27 01:53:09, Saisai Shao wrote:
> > Thanks Ryan, let me take a try.>
> >
> > Best regards,>
> > Saisai>
> >
> > Ryan Blue 于2020年3月27日周五 上午12:15写道：>
> >
> > > Here’s how it was done before:>
> > >
> https:
rg-hive and iceberg-mr modules so that they aren't locked to the
>> same versions as the rest of the projects.
>>
>> On Thu, 26 Mar 2020 at 01:53, Saisai Shao wrote:
>>
>>> Hi Ryan,
>>>
>>> As mentioned in the meeting, would you please point me out the wa
[
https://issues.apache.org/jira/browse/LIVY-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saisai Shao reassigned LIVY-751:
Assignee: Shingo Furuyama
> Livy server should allow to customize LIVY_CLASSP
[
https://issues.apache.org/jira/browse/LIVY-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17067383#comment-17067383
]
Saisai Shao commented on LIVY-751:
--
Issue resolved by pull request 282
https://github.com/apache/incubator
[
https://issues.apache.org/jira/browse/LIVY-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saisai Shao resolved LIVY-751.
--
Resolution: Fixed
> Livy server should allow to customize LIVY_CLASSP
ke a lot of time. I know in our
> company we have no near term plans to move to Spark 3.
>
> -Best,
> R.
>
> On Thu, Mar 5, 2020 at 6:33 PM Saisai Shao wrote:
>
>> I was thinking that if it is possible to limit version lock plugin to
>> only iceberg core related subpr
Sorry for the delay, I will take a review.
Thanks
Saisai
Shingo Furuyama 于2020年3月24日周二 下午12:45写道：
> Hello,
>
> I am Shingo Furuyama, working at Yahoo! JAPAN.
>
> We are trying to use livy 0.7.0-incubating and spark 2.4.5 with YARN
> HDP2.6.4 and have sent a few tiny patches related to the
5pm PST in any day works for me.
Looking forward to it.
Thanks
Saisai
Let's cut and stabilize the branch-0.3 for now. And do the 0.3.0 release
when it is ready.
Thanks
Saisai
俊平堵 于2020年3月9日周一 下午5:16写道：
> Thanks Goson for proposing this. It sounds like a reasonable plan. +1.
>
> PS: In most Apache projects, there is no need to vote for release plan.
> Just make
Though we haven't tried such use case before, from my understanding I think
Livy cannot support it, and such usage scenario seems not a typical usage
pattern.
adley 于2020年3月8日周日 下午9:40写道：
> Hi：
> I followed the official example-PiApp.java, and tried to submit and
> run successfully.
>
suggestions on this?
Best regards,
Saisai
Saisai Shao 于2020年3月5日周四 下午3:12写道：
> I think the requirement of supporting different version should be quite
> common. As Iceberg is a table format which should be adapted to different
> engines like Hive, Flink, Spark. To support different
hecks that
> baseline provides in general since this is a short-term problem. It would
> just be nice if we could have versions that are confined to a single
> module. The Nebula plugin that baseline uses claims to support that, but I
> couldn't get it to work.
>
> On Wed, Ma
be differentiated by names when generating jars, also they will
not be relied by other modules in Iceberg.
So this dependency issue should not be the case here. And in Maven it could
be achieved easily. Please correct me if wrong.
Best regards,
Saisai
Saisai Shao 于2020年3月4日周三 上午10:01写道：
> Thanks M
>
> I would think that branching would be the best way to build and publish
> against multiple versions of a dependency.
>
>
>
> -Matt Cheah
>
>
>
> *From: *Saisai Shao
> *Reply-To: *"dev@iceberg.apache.org"
> *Date: *Tuesday, March 3, 2020 at 5:45
ng, I think it's a
>> great idea to get this into master.
>>
>> Otherwise, I was thinking about proposing an 0.8.0 release in the next
>> month or so based on Spark 2.4. Then we could merge the branch into master
>> and do another release for Spark 3.0 when it's ready
Hi team,
I was thinking of merging spark-3 branch into master, also per the
discussion before we could make spark-2 and spark-3 coexisted into 2
different sub-modules. With this, one build could generate both spark-2 and
spark-3 runtime jars, user could pick either at preference.
One concern is
[
https://issues.apache.org/jira/browse/LIVY-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saisai Shao resolved LIVY-748.
--
Fix Version/s: 0.8.0
Assignee: Roger Liu
Resolution: Fixed
Issue resolved by pull
[
https://issues.apache.org/jira/browse/LIVY-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17045049#comment-17045049
]
Saisai Shao commented on LIVY-423:
--
We don't typically assign JIRA to someone before it merges. I think
[
https://issues.apache.org/jira/browse/LIVY-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17044012#comment-17044012
]
Saisai Shao commented on LIVY-423:
--
No update on it. There's no one working on this feature, you can take
[
https://issues.apache.org/jira/browse/SPARK-30586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17036734#comment-17036734
]
Saisai Shao commented on SPARK-30586:
-
We also met the same issue. Seems like the code doesn't check
[
https://issues.apache.org/jira/browse/SPARK-30586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17036734#comment-17036734
]
Saisai Shao edited comment on SPARK-30586 at 2/14/20 7:13 AM:
--
We also met
Just figured out there's a doc about it. Thanks!
Best regards,
Saisai
Saisai Shao 于2020年2月2日周日 下午7:15写道：
> Hi Team,
>
> Do you know how to build and release java/scala doc for new Livy (0.7.0)
> release. I think document thing is the only remaining thing for 0.7.0
> relea
The Apache Livy team is proud to announce the release of Apache Livy
0.7.0-incubating.
Livy is web service that exposes a REST interface for managing long
running Apache Spark contexts in your cluster. Livy enables
programmatic, fault-tolerant, multi-tenant submission of Spark jobs
from
The Apache Livy team is proud to announce the release of Apache Livy
0.7.0-incubating.
Livy is web service that exposes a REST interface for managing long
running Apache Spark contexts in your cluster. Livy enables
programmatic, fault-tolerant, multi-tenant submission of Spark jobs
from
Hi Team,
Do you know how to build and release java/scala doc for new Livy (0.7.0)
release. I think document thing is the only remaining thing for 0.7.0
release. Please help to guide, would be appreciated if there's doc about it.
Thanks
Saisai
://lists.apache.org/thread.html/r02710b9b34f5dfbdadeaeb73305a2da345b74f3623b597420ff45ae7%40%3Cgeneral.incubator.apache.org%3E
We will continue the release process and soon follow with the announcement
email for the release to general@incubator.
Thanks,
Saisai
Saisai Shao 于2020年2月2日周日 上午10:02写道：
> Hi
Hi all,
The voting for releasing Apache Hudi (incubating) 0.7.0 RC4 has passed with
3 +1 binding votes and no -1 votes.
+1 Vote from:
- Junping Du (binding)
- Justin Mclean (binding)
- Bikas Saha (binding)
Voting Thread:
I don't think current Livy support such behavior, the cluster manager
specified in the conf file is a global configuration which affects all the
created sessions.
Thanks
Saisai
Ravi Shankar 于2020年1月28日周二 上午4:02写道：
> Hey guys,
> Is there a way to start different kind of spark sessions using the
Thanks for the fix. Would you please create a separate PR about this issue?
It should be enough to create a "minor" GH PR directly without JIRA issue.
Best regards,
Saisai
Wing Yew Poon 于2020年1月31日周五 上午6:33写道：
> I updated python-api/setup.py to include
>
> 'mock~=3.0.5',
>
> in
Anyone please help to vote on this thread, greatly appreciated!
Thanks
Saisai
Justin Mclean 于2020年1月22日 周三09:59写道：
> Hi
>
> > About the missing license for the font, we've already investigated a bit
> on
> > this, below is the conclusion. In this release I would like to leave as
> it
> > is.
Thanks Justin for the reply.
About the missing license for the font, we've already investigated a bit on
this, below is the conclusion. In this release I would like to leave as it
is.
Based on https://www.glyphicons.com/license/ we do not need to directly
> mention the licensing for those fonts.
Can any IPMC/mentor help to vote on this? Thanks a ton.
Best regards,
Saisai
Saisai Shao 于2020年1月15日周三 下午5:48写道：
> The Livy PPMC has voted to release Livy 0.7.0 RC4 as the next Livy release.
>
> Livy enables programmatic, fault-tolerant, multi-tenant submission of
> Spark jobs fro
The Livy PPMC has voted to release Livy 0.7.0 RC4 as the next Livy release.
Livy enables programmatic, fault-tolerant, multi-tenant submission of
Spark jobs from web/mobile apps (no Spark client needed). So, multiple
users can interact with your Spark cluster concurrently and reliably.
Vote
IIUC, the current block issue is SGA thing. And I think from code/doc
level, we also have several other things:
1. Change to use Apache License V2 and enable RAT check
2. Refactor README to remove any proprietary word
3. Fix the version number and add versioning track in JIRA.
4. Bootstrap
> and
> > looks good.
> >
> > +1
> >
> > On Wed, Jan 8, 2020 at 8:07 PM Yiheng Wang wrote:
> >
> > > Check the release files. Looks good.
> > >
> > > +1
> > >
> > > On Tue, Jan 7, 2020 at 9:25 PM Saisai Shao
&
[
https://issues.apache.org/jira/browse/LIVY-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17014846#comment-17014846
]
Saisai Shao commented on LIVY-718:
--
Active-active HA doesn't only address scalability issue, but also high
nInterpreter, SparkRInterpreter, and
> SQLInterpreter classes get instantiated and used.
>
>
> Regards,
> -Steve
>
> On Sun, Jan 12, 2020 at 5:45 PM Saisai Shao
> wrote:
>
> > Is this just a wrapper of Livy REST API, or it could support Livy Job
> API?
> >
[
https://issues.apache.org/jira/browse/LIVY-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17013965#comment-17013965
]
Saisai Shao commented on LIVY-718:
--
[~bikassaha] The merged two sub-tasks, they're actually required
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
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
I see there're three open issues about about TubeMQ version number:
1. The version number is x.y-SNASHOT, typically it would be x.y.z-SNAPHOST
2. For incubating project, it should have "incubating" suffix,
x.y.z-incubating-SNAPSHOT.
3. There's no version number tracking for each JIRA.
So I think
[
https://issues.apache.org/jira/browse/LIVY-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17011485#comment-17011485
]
Saisai Shao commented on LIVY-718:
--
Hi [~shanyu] what is the main reason that we should have "a
Hi Goson, why don't you create a JIRA to track this issue?
俊平堵 于2020年1月8日周三 下午5:17写道：
> +1. I think we *must* use standard Apache license given this is an apache
> project.
> Would like to hear other mentors' opinion here as well.
>
> Thanks,
>
> Junping
>
> Goson zhang 于2020年1月8日周三 下午5:14写道：
[
https://issues.apache.org/jira/browse/LIVY-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saisai Shao resolved LIVY-735.
--
Fix Version/s: 0.8.0
Assignee: runzhiwang
Resolution: Fixed
Issue resolved by pull
I agreed, I think there should a wiki about "how to contribute".
Also about the commit log, I think we should use the script to formalize
the commit log and use this to merge, not directly using GH button, one
consideration is to formalize the commit log, another is to avoid
additional merge
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
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
[
https://issues.apache.org/jira/browse/LIVY-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saisai Shao resolved LIVY-732.
--
Fix Version/s: 0.8.0
Assignee: runzhiwang
Resolution: Fixed
Issue resolved by pull
[
https://issues.apache.org/jira/browse/LIVY-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saisai Shao resolved LIVY-738.
--
Fix Version/s: 0.8.0
0.7.0
Assignee: Saisai Shao
Resolution: Fixed
nologies
> --
> *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 ---01
, they do existed in binary distro
as a part of Livy Server.
Thanks
Saisai
Luciano Resende 于2020年1月3日周五 上午6:11写道：
> On Mon, Dec 30, 2019 at 3:43 AM Saisai Shao
> wrote:
> >
> > The Livy PPMC has voted to release Livy 0.7.0 RC3 as the next Livy
> release.
> >
> >
Saisai Shao created LIVY-738:
Summary: Fix Livy third-party library license generating issue
Key: LIVY-738
URL: https://issues.apache.org/jira/browse/LIVY-738
Project: Livy
Issue Type: Bug
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
I've updated some parts of the report, please help to review, thanks!
Besides, we will follow the Apache way to bring out all the discussions on
the mail list, thanks for your guidance.
Thanks
Saisai
Saisai Shao 于2020年1月3日周五 上午11:27写道：
> Thanks Justin for your reply, I will amend the rep
Thanks Justin for your reply, I will amend the report soon.
Best regards,
Saisai
Justin Mclean 于2020年1月3日周五 上午7:03写道：
> Hi,
>
> Thanks for submitting the report but it will not be accepted in it's
> currently form as it doesn't accurately reflect the current podlings state
> and what it needs
Thanks Justin and Luciano for your check.
I use some maven plugins to extract license files from third party
libraries, the missing of license files are mainly due to the issue of this
jars. I will amend them manually and make another RC release.
Thanks
Saisai
Justin Mclean 于2020年1月3日周五
There's no any vote yet, I guess it might be due to the holiday season. I
will extend the due date to weekend.
Thanks
Saisai
Saisai Shao 于2019年12月30日周一 上午10:43写道：
> The Livy PPMC has voted to release Livy 0.7.0 RC3 as the next Livy
> release.
>
> Livy enables programmatic, fa
Hi Justin,
Sorry about the late reply, we will work on this today. Thanks a lot for
your reminder.
Best regards,
Saisai
Justin Mclean 于2020年1月2日周四 上午10:05写道：
> Hi,
>
> This is the second report in a row the project has missed, one missed
> report is OK, two are cause for concern, three and
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
>
[
https://issues.apache.org/jira/browse/LIVY-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17005895#comment-17005895
]
Saisai Shao commented on LIVY-718:
--
IIUC, current JDBC part maintains lots of results/metadata/information
The Livy PPMC has voted to release Livy 0.7.0 RC3 as the next Livy release.
Livy enables programmatic, fault-tolerant, multi-tenant submission of
Spark jobs from web/mobile apps (no Spark client needed). So, multiple
users can interact with your Spark cluster concurrently and reliably.
Vote
1 - 100 of 1996 matches
Mail list logo
