Congratulations, Qingsheng! :)
On Mon, Apr 24, 2023, 05:17 Yangze Guo wrote:
> Congratulations, Qingsheng!
>
> Best,
> Yangze Guo
>
> On Mon, Apr 24, 2023 at 10:05 AM Shuo Cheng wrote:
> >
> > Congratulations, Qingsheng!
> >
> > Best,
> > Shuo
> >
> > On Sun, Apr 23, 2023 at 7:43 PM Sergey Nuya
Congrats, Leonard :)
On Mon, Apr 24, 2023, 05:17 Yangze Guo wrote:
> Congratulations, Leonard!
>
> Best,
> Yangze Guo
>
> On Mon, Apr 24, 2023 at 10:05 AM Shuo Cheng wrote:
> >
> > Congratulations, Leonard.
> >
> > Best,
> > Shuo
> >
> > On Sun, Apr 23, 2023 at 7:43 PM Sergey Nuyanzin
> wrote:
Hi everyone,
I'm jumping in a bit late due to holidays. Generally, I agree with all the
things that were shared in this thread. It would be great to see Flink 2.0
happening (especially in terms of the Java 17 support and the removal of
code).
I would prefer having a major release that focuses enti
Hi Gyula,
Could you share the logs in the ML? Or is there a Jira issue I missed?
Matthias
On Wed, May 17, 2023 at 9:33 PM Gyula Fóra wrote:
> Hey Devs!
>
> I am bumping this thread to see if someone has any ideas how to go about
> solving this.
>
> Yang Wang earlier had this comment but I am no
Thanks for starting this discussion, Becket. A few good points were raised.
Here's what I want to add:
Stefan raised the point of behavioral stability (in contrast to API
stability). That might be a reason for users to not be able to go ahead
with a major version bump. Working around behavioral ch
Kafka releases which is
> extremely rewarding.
>
> Thanks,
>
> Jiangjie (Becket) Qin
>
> On Wed, Jun 14, 2023 at 5:06 PM Matthias Pohl
> wrote:
>
> > Thanks for starting this discussion, Becket. A few good points were
> raised.
> > Here's what I want
Thanks, Becket
+1 (binding)
On Mon, Jul 3, 2023 at 10:44 AM Jing Ge wrote:
> +1(binding)
>
> On Mon, Jul 3, 2023 at 10:19 AM Stefan Richter
> wrote:
>
> > +1 (binding)
> >
> >
> > > On 3. Jul 2023, at 10:08, Martijn Visser
> > wrote:
> > >
> > > +1 (binding)
> > >
> > >
> > >
> > > On Mon, Ju
Now that the vote is started on the must-have items: There are still
to-be-discussed items in the list of features. What's the plan with those?
Some of them don't have anyone assigned. Were these items discussed among
the release managers? So far, it looks like they are handled as
nice-to-have if s
@Xintong did you come across FLINK-3957 [1] when looking for deprecated
issues? There are a few subtasks that would require deprecations as well as
far as I can see. For some I'm wondering whether we should add them to the
release 2.0 feature list [2] in some way and (as a consequence) missed them
> > > Some of them don't have anyone assigned.
> > > > My concern is that they will be overlooked because nobody feels to
> be in
> > > >> charge.
> > > > This is a tricky one. For must-have items without assignees, we as
> the
> > &
gt;
> [1] https://lists.apache.org/thread/r0y9syc6k5nmcxvnd0hj33htdpdj9k6m
> [2] https://issues.apache.org/jira/browse/FLINK-3957
>
> On Mon, Jul 10, 2023 at 10:53 PM Matthias Pohl
> wrote:
>
> > I brought it up in the deprecating APIs in 1.18 thread [1] already but it
> >
I also like the proposed designs. Considering that you want to touch
individual subpages, there are also some subpages of Flink's website not
being mentioned in the FLIP (e.g. roadmap [1]). What is the plan with
those? Are they covered by the "We recommend modifications only to the
design of the fo
The 2.0 feature list includes the removal of Flink's Time classes in favor
of the JDKs java.time.Duration class. There was already a discussion about
it in [1] and FLINK-14068 [2] was created as a consequence of this
discussion.
I started working on marking the APIs as deprecated in FLINK-32570 [3
Jing brought up a question in the FLIP-335 discussion thread [1] which I
want to move into a dedicated discussion thread as it's a bit more general:
How do we handle the deprecation process of Public APIs for Flink 2.0?
>
> I just have a related question: Do we need to create a FLIP each time
> whe
should be no doubt to
> deprecate Time classes. +1
>
> I just have a related question: Do we need to create a FLIP each time when
> we want to deprecate any classes? (BTW, FLIP-335 contains useful
> information. It makes sense to write it)
>
> Best regards,
> Jing
>
must be
> > > deprecated for at least 2 minor releases before they can be removed
> > > (which is now unsurprisingly backfiring on us).
> > >
> > > So if something isn't deprecated in 1.18 then either:
> > > - we delay 2.0 by at 1 release cycle
method which needs to be implemented in the Scala Pattern class as
> well to comply with PatternScalaAPICompletenessTest."
>
> /FLIP-265//states that /all/ Scala APIs will be removed, which should
> also cover CEP.
> //
> On 13/07/2023 12:08, Matthias Pohl wrote:
> > The
>
> We don't have a well-defined process for breaking behavioral changes. We
> could consider adding a new method with a different name.
Introducing a new API to make the behavioral change visible was also the
suggestion in the deprecation ML thread [1]. getEnvironmentVariables (or
even getEnviron
I think Martijn and Markos brought up a few good points:
- We shouldn't degrade the accessibility but ideally improve it as part of
the redesign. The current proposal doesn't look like we're doing changes in
a way that it lowers the accessibility (considering that the menu structure
stays the same
+1 nothing to add
@Austin It sounds reasonable. But this topic might deserve a dedicated
discussion thread, I think.
On Thu, Jul 20, 2023 at 12:52 AM Austin Cawley-Edwards <
austin.caw...@gmail.com> wrote:
> It doesn't need to be part of the Flink 2.0 release perse, but starting to
> wonder if w
Sorry for the late reply in that matter. I was off the last few days. I
should have made this clear in the ML. Anyway, I went over the issues as
well. Xintong's summary matches more or less my findings aside from the
following items:
- FLINK-4503 (remove deprecated methods from CoGroupedStreams an
There's a kind-of-related issue FLINK-4758 [1] that proposes removing the
IOReadableWritable interface from more classes. It was briefly mentioned in
the must-have work items discussion [2].
I'm not too sure about the usage of IOReadableWritable: ...whether it would
go away with the removal of the
The feature freeze was postponed to July 24 (end of this week in
Europe/early morning Monday in East Asia) in [1]. What's the 1.18 release
managers' take on all the FLIPs that were recently started and require some
deprecation work (which ideally should go into 1.18)? How does that work
with the fe
I should have mentioned it in the discussion thread but I missed going over
that ML thread earlier: We might want to update the FLIP to refer to the
actual endpoint /jobs/:jobid/rescaling (AFAIU) with the corresponding cause
being FLINK-12312 [1].
But that's just a minor thing.
+1 (binding)
[1]
+1 (binding)
On Mon, Jul 24, 2023 at 2:24 PM Konstantin Knauf wrote:
> +1 (binding)
>
> Am Mo., 24. Juli 2023 um 14:15 Uhr schrieb Martijn Visser <
> martijnvis...@apache.org>:
>
> > +1 (binding)
> >
> > On Mon, Jul 24, 2023 at 1:08 PM Chesnay Schepler
> > wrote:
> >
> > > Hello,
> > >
> > > I'
Do we have conventions on how the REST API should be formatted written down
somewhere?
Checking our coding conventions [1] didn't reveal anything.
We could refer to a style guide like [2] to cover this topic. That would
also include the camel-cased JSON fields.
[1]
https://flink.apache.org/how-to
What was the reason you decided to go for 0 as the fallback value instead
of null? Wouldn't that be a more reasonable value for error cases?
On Mon, Jul 24, 2023 at 12:51 PM Chesnay Schepler
wrote:
> There are a number of cases where the REST API can return infinity or
> NaN for certain double f
Hi liuwb9,
thanks for reporting this issue. Please keep a few things in mind, though:
- The community only supports the two most-recently released versions of
Flink. Your version 1.14 is too old (issues might have been fixed already
in newer releases). Trying to reproduce the behavior in a supporte
Congratulations :)
On Tue, Jul 25, 2023 at 5:13 PM Jing Ge wrote:
> Congrats, Yong Fang!
>
> Best regards,
> Jing
>
> On Tue, Jul 25, 2023 at 7:35 PM Yu Li wrote:
>
> > Congrats, Yong!
> >
> > Best Regards,
> > Yu
> >
> >
> > On Tue, 25 Jul 2023 at 18:03, Sergey Nuyanzin
> wrote:
> >
> > > Con
>>> - Considering FLIPs that purely mark an API as deprecated and do not
> > >>> introduce anything new as "not a new feature", because that can
> hardly
> > >>> cause any trouble.
> > >>> - Considering FLIPs that introduce new /
ssing multiple modules issue, I've explained it in the
> > reply
> > > >> to Matthias.
> > > >>
> > > >>
> > > >> Best regards,
> > > >>
> > > >>
> > > >> Wencong Liu
&g
-0 (binding)
I'm not going to block this effort because it's still possible to cover
other occurrences in a subsequent FLIP if it's considered useful (I'm not
in the position to judge how important the IOReadableWritable interface is
in the context of removing the DataSet API).
The recent discuss
+1 (binding)
On Wed, Jul 26, 2023 at 10:11 AM Yuxin Tan wrote:
> +1 (non-binding)
>
> Best,
> Yuxin
>
>
> Xintong Song 于2023年7月26日周三 16:08写道：
>
> > +1 (binding)
> >
> > Best,
> >
> > Xintong
> >
> >
> >
> > On Wed, Jul 26, 2023 at 3:35 PM Yuepeng Pan wrote:
> >
> > > +1 (non-binding)
> > >
> >
Matthias's intention to put more workload on Wencong.
> It's just sometimes such requests are not easy to say no.
>
> Best,
>
> Xintong
>
>
>
> On Wed, Jul 26, 2023 at 4:14 PM Matthias Pohl
> wrote:
>
> > Is the time constraint driven by the fact th
isn't even used.
> >>> Arguably the same could be said for null, but I'd think that 0 is less
> >>> of a surprise.
> >>>
> >>> On 24/07/2023 17:21, Gyula Fóra wrote:
> >>>> I agree that it's a bit strange to have 0 as a fal
I think making the last minor release before a major release an LTS release
with extended support makes sense. I cannot think of a reason against the
four minor release cycles suggested by Marton. Only providing bug fixes and
not allowing features to be backported sounds reasonable to keep the
main
@Mathias, I am not quite sure about the 3 versions description. Are you
> concerned that 1.x and 2.x LTS releases could overlap, if 3.0 comes early?
>
> Best,
> Alex
>
> On Wed, 26 Jul 2023 at 14:47, Matthias Pohl .invalid>
> wrote:
>
> > I think making the last
I'm requesting to merge in FLINK-32098 [1]. It's a minor change that
reduces the amount of exists calls to S3 while submitting a job (which can
be an expensive operation if the object actually doesn't exist but the
corresponding bucket itself contains a lot of objects). The PR is reviewed
and ready
Congratulations, Hong! :)
On Thu, Aug 3, 2023 at 3:39 PM Leonard Xu wrote:
> Congratulations, Hong!
>
>
> Best,
> Leonard
>
> > On Aug 3, 2023, at 8:45 PM, Jiabao Sun
> wrote:
> >
> > Congratulations, Hong Teoh!
> >
> > Best,
> > Jiabao Sun
> >
> >> 2023年8月3日 下午7:32，Danny Cranmer 写道：
> >>
> >>
tions, Matthias!
> >> > >
> >> > > Best,
> >> > > Wencong Liu
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> &
Congratulations, Weihua.
On Mon, Aug 7, 2023 at 3:50 AM Yuepeng Pan wrote:
>
>
>
> Congratulations, Weihua!
>
> Best,
> Yuepeng Pan
>
>
>
>
>
> 在 2023-08-07 09:17:41，"yh z" 写道：
> >Congratulations, Weihua!
> >
> >Best,
> >Yunhong Zheng (Swuferhong)
> >
> >Runkang He 于2023年8月5日周六 21:34写道：
> >
>
Congratulations, Yanfei! :)
On Mon, Aug 7, 2023 at 10:00 AM Junrui Lee wrote:
> Congratulations Yanfei!
>
> Best,
> Junrui
>
> Yun Tang 于2023年8月7日周一 15:19写道：
>
> > Congratulations, Yanfei!
> >
> > Best
> > Yun Tang
> >
> > From: Danny Cranmer
> > Sent: Monday,
Congratulations, Hangxiang! :)
On Mon, Aug 7, 2023 at 10:01 AM Junrui Lee wrote:
> Congratulations, Hangxiang!
>
> Best,
> Junrui
>
> Yun Tang 于2023年8月7日周一 15:19写道：
>
> > Congratulations, Hangxiang!
> >
> > Best
> > Yun Tang
> >
> > From: Danny Cranmer
> > Sent
Thanks Shammon FY for starting this discussion.
I'm not sure whether we have to expand the focus of Apache Flink in a way
you're describing it with OLAP being a topic next to Batch and Stream
Processing. You've rightfully pointed out that there are already solutions
to cover OLAP. In this sense, I
Your request was approved. Sorry for the delay and welcome to the
community. :)
On Tue, Aug 15, 2023 at 3:58 AM lambda ch wrote:
> Sorry I may have misunderstood. I need a jira account. And I have already
> submitted a jira account request. How long will it take to get approved? My
> Jira Id is
org/apache/flink/table/planner/sinks/CollectTableSink.scala#L70
[11] https://cwiki.apache.org/confluence/display/FLINK/2.0+Release
--
[image: Aiven] <https://www.aiven.io>
*Matthias Pohl*
Opensource Software Engineer, *Aiven*
matthias.p...@aiven.io| +49 170 9869525
aiven.io <https://www.aiven.i
> > rather than CollectSink and whether their requirements can be fully
> covered
> > by CollectSink. For 2), we probably also need to involve the user@ ML.
> >
> > Best,
> >
> > Xintong
> >
> >
> >
> > On Wed, Aug 23, 2023 at 11:00 PM Mat
Thanks Gabor for looking into it. It sounds reasonable to me as well.
+1
On Sun, Sep 3, 2023 at 5:44 PM Márton Balassi
wrote:
> Hi Gabor,
>
> Thanks for bringing this up. Similarly to when we dropped Python 3.6 due to
> its end of life (and added 3.10) in Flink 1.17 [1,2], it makes sense to
> p
luence/display/FLINK/FLIP-360%3A+Merging+the+ExecutionGraphInfoStore+and+the+JobResultStore+into+a+single+component+CompletedJobStore
--
[image: Aiven] <https://www.aiven.io>
*Matthias Pohl*
Opensource Software Engineer, *Aiven*
matthias.p...@aiven.io| +49 170 9869525
aive
You should be able to adapt tools/azure-pipelines/build-apache-repo.yml [1]
in your branch as a "debug" commit to add the steps/stages that you're
planning to include in a test CI run of your PR (this debug commit should
be removed before merging the PR). The ci stage will be executed as part of
yo
I don't know about the specifics of the kryo 2.x vs 5.x issues. The
discussion around FLIP-317 [1] seems to have stalled here. But Java 17 is
still considered an experimental feature as expressed in Flink's roadmap
[2]. So, it should be fine to have it in 1.18. I updated the release notes
of FLINK
sterClient as an access point.
The last option is my least favorite one: Moving the ExecutionGraphInfo out
of the JobManager seems to be the right thing to do when thinking about
Flink's vision to become cloud-native.
Just my 2cts on that topic.
Matthias
On Mon, Sep 4, 2023 at 1:11 PM Matthias
Thanks for creating RC1. I did the following checks:
* Downloaded artifacts
* Built Flink from sources
* Verified SHA512 checksums GPG signatures
* Compared checkout with provided sources
* Verified pom file versions
* Went over NOTICE file/pom files changes without finding anything
suspicious
* D
the proposal more carefully next week and
> > provide some detailed feedback.
> >
> > +1
> >
> > Thanks
> > Gyula
> >
> > On Fri, Sep 8, 2023 at 8:36 AM Matthias Pohl > .invalid>
> > wrote:
> >
> > > Just a bit more elabo
+1 Sounds like a good idea.
On Wed, Oct 4, 2023 at 5:04 PM Gyula Fóra wrote:
> I will share my initial implementation soon, it seems to be pretty
> straightforward.
>
> Biggest challenge so far is setting tests so we can still compile against
> older versions but have tests for records . But I h
I would agree with David's proposal as well.
Would it make sense to come up with some performance comparisons for the
different S3 implementations in the end? ...just to ensure that we're
improving things or (at least) don't make things worse. Or is there
something like that already somewhere?
A
implemented wrongly. I would imagine that this could be a valid concern
because the concept of directories is not really present in an object store
like S3, if I'm not mistaken?!
On Mon, Oct 9, 2023 at 6:49 PM Matthias Pohl wrote:
> I would agree with David's proposal as well.
>
> Wou
Great catch, Yun Tang. I created FLINK-33291 [1] to cover the issue of
enforcing the JDK (and Maven) version in the release profile.
[1] https://issues.apache.org/jira/browse/FLINK-33291
On Tue, Oct 17, 2023 at 1:28 PM Jing Ge wrote:
> Hi Folks,
>
> I have rebuilt Flink with Java 8 and replaced
rg/content/repositories/orgapacheflink-1658/org/apache/flink/flink-runtime/1.18.0/flink-runtime-1.18.0.jar
>
> Best,
> Yun Tang
>
>
> --
> *From:* Matthias Pohl
> *Sent:* Tuesday, October 17, 2023 20:38
> *To:* dev@flink.apache.org
> *C
Congratulations :)
On Mon, Oct 16, 2023 at 1:04 PM Jing Ge wrote:
> Congrats!
>
> Best regards,
> Jing
>
> On Mon, Oct 16, 2023 at 10:33 AM Yuepeng Pan
> wrote:
>
> > Congratulations, Jane !
> >
> >
> >
> > Best,
> > Yuepeng Pan
> >
> > At 2023-10-16 09:58:02, "Jark Wu" wrote:
> > >Hi, everyon
Congratulations :)
On Mon, Oct 16, 2023 at 11:55 PM Venkatakrishnan Sowrirajan <
vsowr...@asu.edu> wrote:
> Congrats Ron!
>
> On Mon, Oct 16, 2023, 9:34 AM David Radley
> wrote:
>
> > Congratulations Ron!
> >
> > From: Jark Wu
> > Date: Sunday, 15 October 2023 at 18:57
> > To: dev
> > Cc: ron9
IHi Yuxin,
That would be the way to go for flink-shaded and Flink 1.17.
Generally, netty upgrades are a source of instability based on past
experiences. But considering that we have newer versions (4.1.91.Final)
tested with flink-shaded 17.0 in Flink 1.18, it should be alright bumping
netty in fl
+1 (binding)
* Downloaded artifacts
* Built Flink from sources
* Verified SHA512 checksums GPG signatures
* Compared checkout with provided sources
* Verified pom file versions
* Verified that there are no pom/NOTICE file changes since RC1
* Deployed standalone session cluster and ran WordC
Good question. I couldn't find anything about it except for 9ef6796e [1]
where it was excluded from the Maven deployment. Unfortunately, no Jira
issue is attached with additional documentation.
@Martijn Visser How is the docs generation
intended to be used? It looks like it's done by integrating
Hi Amir,
Usually, the plan is to release minor version support for Flink connectors
after the Flink minor version is released. See Martijn's post on that issue
in the 1.18.0 RC0 ML thread [1] for further context.
Best,
Matthias
[1] https://lists.apache.org/thread/687qrtq3894ycw69dvvr4sdjdqxngsj6
Hi David,
The change that caused the conflict in your PR is caused by FLINK-33291
[1]. I was thinking about adding links to the comments to make the
navigation to the corresponding resources easier as you rightfully
mentioned. I didn't do it in the end because I was afraid that
documentation might
simple place?
> - Ideally the JobDetailsStore / JobDetailsProvider could be a very thin
> interface exposed by the CompletedJobStore
>
> Gyula
>
> On Sat, Sep 30, 2023 at 2:18 AM Matthias Pohl
> wrote:
>
> > Thanks for sharing your thoughts, Shammon FY. I kind of see
1.17.3 would cover roughly 78 issues [1]. Flink 1.16.3 would cover 50
issues fixed [2]. There would be a discussion on whether we should do a
1.16.3 flush-out-all-the-leftover-issues minor release in the context of
the currently happening 1.18.0 release, anyway.
+1 I think it makes sense to prepar
+1 from my side for Lincoln, Yun Tang, Jing and Martijn as release managers.
Thanks everyone for volunteering.
I tried to collect the different tasks that are part of release management
in [1]. It might help to identify responsibilities. Feel free to have a
look and/or update it. Ideally, it will
Thanks to everyone who was involved and especially to the 1.18 release
managers. :)
On Fri, Oct 27, 2023 at 9:13 AM Yuepeng Pan wrote:
> Thanks for the great work! Congratulations to everyone involved!
>
>
> Best,
> Yuepeng Pan
>
> At 2023-10-27 15:06:40, "ConradJam" wrote:
> >Congratulations!
Thanks for your proposal, Zhanghao Chen. I think it adds more transparency
to the configuration documentation.
+1 from my side on the proposal
On Wed, Oct 11, 2023 at 2:09 PM Zhanghao Chen
wrote:
> Hi Flink users and developers,
>
> Currently, Flink won't generate doc for the deprecated options
+1 (binding)
* Downloaded artifacts
* Built Flink from sources
* Verified SHA512 checksums & GPG signatures
* Compared checkout with provided sources
* Verified pom file versions
* Went over NOTICE/pom file changes without finding anything suspicious
* Deployed standalone session cluster and ran W
+1 (binding)
* Downloaded artifacts
* Built Flink from sources
* Verified SHA512 checksums & GPG signatures
* Compared checkout with provided sources
* Verified pom file versions
* Went over NOTICE/pom file changes without finding anything suspicious
* Deployed standalone session cluster and ran W
/actions/runs/6927443941
[5]
https://cwiki.apache.org/confluence/display/FLINK/FLIP-395%3A+Migration+to+GitHub+Actions
--
[image: Aiven] <https://www.aiven.io>
*Matthias Pohl*
Opensource Software Engineer, *Aiven*
matthias.p...@aiven.io| +49 170 9869525
aiven.io <https://www
Tue, Nov 21, 2023 at 2:58 PM Matthias Pohl
wrote:
> Hi everyone,
>
> The Flink community discussed migrating from Azure CI to GitHub Actions
> quite some time ago [1]. The efforts around that stalled due to limitations
> around self-hosted runner support from Apache Infra’s side.
eed to provide the secret to
> ASF Infra and then we would be able to refer to them in a pipeline?
>
> Best regards,
>
> Martijn
>
> On Tue, Nov 21, 2023 at 3:05 PM Matthias Pohl
> wrote:
> >
> > I realized that I mixed up FLIP IDs. FLIP-395 is already reserved
that there are
some features provided through plugins which are missing in GitHub Actions.
[1] https://lists.apache.org/thread/vs81xdhn3q777r7x9k7wd4dyl9kvoqn4
On Tue, Nov 21, 2023 at 4:19 PM Matthias Pohl
wrote:
> That's a valid point. I updated the FLIP accordingly:
>
>> Curre
+1
Thanks for driving this, Sergey. We could also think of removing the
ZooKeeper versions 3.5 and 3.6, I guess. 3.6 reached EOL in 2022. Flink
1.17 already switched to 3.7 as the default version.
On Thu, Nov 23, 2023 at 9:31 AM Jing Ge wrote:
> +1
>
> Does it make sense to use 32.1.3-jre Guava
mailing list I should
> ask for assistance?
>
> [1]
>
> https://cwiki.apache.org/confluence/display/FLINK/Creating+a+flink-shaded+release#Creatingaflinkshadedrelease-Preparefortherelease
>
>
>
>
> On Thu, Nov 23, 2023 at 11:25 AM Matthias Pohl
> wrote:
>
>
t; > for Apache Beam, Google donated a bunch of servers to get additional
> > build capacity.
> >
> > -Max
> >
> >
> > On Thu, Nov 23, 2023 at 10:30 AM Matthias Pohl
> > wrote:
> >> Btw. even though we've been focusing on GitHub Actions
. Will it be a blocker before migrating the new
> tests? If not, If not, when can we expect arm environment
> support to be implemented? Thanks.
>
> Best,
> Yuxin
>
>
> Márton Balassi 于2023年11月29日周三 03:09写道：
>
> > Thanks, Matthias. Big +1 from me.
> >
>
Thanks for the update, Lincoln.
A small remark: The appreciation for fixing FLINK-18356 [1] should be sent
to Yunhong Zheng. :)
Now, let's see and hope that the problem doesn't appear again.
Best,
Matthias
[1] https://issues.apache.org/jira/browse/FLINK-18356
On Wed, Nov 29, 2023 at 2:41 AM Lin
The key is the last key in the KEYS file. It's just having a different
format with spaces being added (due to different gpg versions?): F752 9FAE
2481 1A5C 0DF3 CA74 1596 BBF0 7268 35D8
On Wed, Nov 29, 2023 at 9:41 AM Rui Fan <1996fan...@gmail.com> wrote:
> Hey Sergey,
>
> Thank you for driving
hash
> > - Verified signature
> > - Verified that no binaries exist in the source archive
> > - Build the source with Maven and jdk8
> > - Verified licenses
> > - Verified web PRs, and left a comment
> >
> > Best,
> > Rui
> >
> > On Wed, Nov 29
maintain the CI in two places (i.e. PRs on Github Actions and cron builds
> > on Azure).
> >
> > - What exactly are the changes that would affect contributors during the
> > trial period? Is it only an additional CI report that you can potentially
> > just ignore? Or w
o rely on (see the
workflows I shared in my previous response to Xintong's message).
[1] https://issues.apache.org/jira/browse/FLINK-18370
On Wed, Nov 29, 2023 at 3:17 PM Matthias Pohl
wrote:
> Thanks for your comments, Xintong. See my answers below.
>
>
>> I think it would b
Welcome to the community. :)
Some good starting points aside from reading the mailing lists [1] are the
documentation about contributing [2] and setting up your IDE [3]. You can
look for Jira issues labeled as starter [4].
Matthias
[1] https://flink.apache.org/what-is-flink/community/#mailing-li
comparison to 14GB), though.
[1]
https://cwiki.apache.org/confluence/display/FLINK/FLIP-396%3A+Trial+during+Flink+1.19+Cycle+to+test+migrating+to+GitHub+Actions#FLIP396:TrialduringFlink1.19CycletotestmigratingtoGitHubActions-HardwareSpecifications
On Wed, Nov 29, 2023 at 4:01 PM Matthias P
+1 (binding)
On Fri, Dec 1, 2023 at 3:40 AM Zhu Zhu wrote:
> +1 (binding)
>
> Thanks,
> Zhu
>
> Zhanghao Chen 于2023年11月30日周四 23:31写道：
>
> > +1 (non-binding)
> >
> > Best,
> > Zhanghao Chen
> >
> > From: Rui Fan <1996fan...@gmail.com>
> > Sent: Monday, November 1
, we
> > can encourage contributors to report unstable cases under a specific
> > ticket umbrella when they encounter them.
> >
> > Best,
> > Yangze Guo
> >
> > On Thu, Nov 30, 2023 at 12:10 AM Matthias Pohl
> > wrote:
> >> With regards to Ale
ding votes.
Matthias
[1]
https://cwiki.apache.org/confluence/display/FLINK/FLIP-396%3A+Trial+to+test+GitHub+Actions+as+an+alternative+for+Flink%27s+current+Azure+CI+infrastructure
[2] https://lists.apache.org/thread/h4cmv7l3y8mxx2t435dmq4ltco4sbrgb
--
[image: Aiven] <https://www.aiven.io>
ly concluded if there
are no objections and enough (i.e. at least 3) binding votes.
Matthias
[1]
https://cwiki.apache.org/confluence/display/FLINK/FLIP-335%3A+Removing+Flink%27s+Time+classes
[2] https://lists.apache.org/thread/48ysrg1rrtl8s1twg9wmx35l201hnc2w
--
[image: Aiven] <https://www.ai
Sure, I will help you.
On Wed, Dec 13, 2023 at 7:55 PM Alex Nitavsky
wrote:
> Hello,
>
> I would love to initiate FLIP in order to extend Apache Curator
> configuration: https://issues.apache.org/jira/browse/FLINK-33376.
>
> Would it be please possible to get edit permissions for Apache Flink
>
I updated the Slack invite link [1]. Feel free to use that one. I created a
PR [2] to reflect the change on the website as well.
Matthias
[1]
https://join.slack.com/t/apache-flink/shared_invite/zt-294plfx41-23lOoovZOdegKwjW9_0q_g
[2] https://github.com/apache/flink-web/pull/704
On Wed, Dec 13, 2
;
> > Thanks.
> >
> > Best regards,
> > Jing
> >
> > On Tue, Dec 12, 2023 at 1:12 PM Zhu Zhu wrote:
> >
> > > +1 (binding)
> > >
> > > Thanks,
> > > Zhu
> > >
> > > Matthias Pohl 于2023年12月12日周二 01:32写
hnc2w
[3] https://lists.apache.org/thread/notp8cc942jknpqcoq1cnsmgh5wz80h5
--
[image: Aiven] <https://www.aiven.io>
*Matthias Pohl*
Opensource Software Engineer, *Aiven*
matthias.p...@aiven.io| +49 170 9869525
aiven.io <https://www.aiven.io> | <https://www.facebook.com/aivenclou
t; Best,
> > > >>>>> Yangze Guo
> > > >>>>>
> > > >>>>> On Tue, Dec 12, 2023 at 3:51 PM Yuxin Tan >
> > > wrote:
> > > >>>>>> +1 (non binding)
> > > >>>>>> Thanks for the effort.
> > > >>>
org/thread/qx91dkm7mornvqqbr5n5sg1z9hj06t55
--
[image: Aiven] <https://www.aiven.io>
*Matthias Pohl*
Opensource Software Engineer, *Aiven*
matthias.p...@aiven.io| +49 170 9869525
aiven.io <https://www.aiven.io> | <https://www.facebook.com/aivencloud>
<https://www.linked
+1 (binding)
On Wed, Jan 10, 2024 at 3:35 PM ConradJam wrote:
> +1 non-binding
>
> Dawid Wysakowicz 于2024年1月10日周三 21:06写道：
>
> > +1 (binding)
> > Best,
> > Dawid
> >
> > On Wed, 10 Jan 2024 at 11:54, Piotr Nowojski
> wrote:
> >
> > > +1 (binding)
> > >
> > > śr., 10 sty 2024 o 11:25 Martijn Vi
Thanks for joining the discussion, everyone and sorry for picking it up
that late. Here are a few points, I want to add to this discussion:
- FLINK-24038 [1] led to a reduction of the curator/k8s client leader
election requests by having a single leader election per JM rather than
individual once
1 - 100 of 971 matches
Mail list logo
