+1. Thank you for picking it up. Yes, this will be the final bug fix for
Flink 1.16.
Am Mo., 6. Nov. 2023 um 03:47 Uhr schrieb Rui Fan <1996fan...@gmail.com>:
> Hi all,
>
> I would like to discuss creating a new 1.16 patch release (1.16.3). The
> last 1.16 release is over five months old, and
Thank you for picking it up! +1
Cheers,
Konstantin
Am Mo., 6. Nov. 2023 um 03:48 Uhr schrieb Yun Tang :
> Hi all,
>
> I would like to discuss creating a new 1.17 patch release (1.17.2). The
> last 1.17 release is near half a year old, and since then, 79 tickets have
> been closed [1], of which
Hi Rui,
Thank you for this proposal and working on this. I also agree that
exponential back off makes sense as a new default in general. I think
restarting indefinitely (no max attempts) makes sense by default, though,
but of course allowing users to change is valuable.
So, overall +1.
Cheers,
Thanks a lot for working on this!
Am Do., 19. Okt. 2023 um 10:24 Uhr schrieb Zakelly Lan <
zakelly@gmail.com>:
> Hi everyone,
>
> Flink benchmarks [1] generate daily performance reports in the Apache
> Flink slack channel (#flink-dev-benchmarks) to detect performance
> regression [2]. Those
Hi everyone,
I've just opened a PR for the release announcement [1] and I am looking
forward to reviews and feedback.
Cheers,
Konstantin
[1] https://github.com/apache/flink-web/pull/680
Am Fr., 6. Okt. 2023 um 11:03 Uhr schrieb Sergey Nuyanzin <
snuyan...@gmail.com>:
> sorry for not
Hi Bonnie,
this makes sense to me, in particular, given that we already have this
toggle for a different type of hints.
Best,
Konstantin
Am Mi., 16. Aug. 2023 um 19:38 Uhr schrieb Bonnie Arogyam Varghese
:
> Hi Liu,
> Options hints could be a security concern since users can override
>
Congrats, Matthias!
Am Fr., 4. Aug. 2023 um 09:15 Uhr schrieb Paul Lam :
> Congratulation, Matthias!
>
> Best,
> Paul Lam
>
> > 2023年8月4日 15:09，yuxia 写道：
> >
> > Congratulation, Matthias!
> >
> > Best regards,
> > Yuxia
> >
> > - 原始邮件 -
> > 发件人: "Yun Tang"
> > 收件人: "dev"
> > 发送时间:
w long is enough?) because
> LTS has been offered. How could we help users and avoid this happening?
>
> Best regards,
> Jing
>
> On Tue, Jul 25, 2023 at 6:57 PM Konstantin Knauf
> wrote:
>
> > Hi Jing,
> >
> > let's not overindex on the Source-/SinkFunction discussio
Hi everyone,
I'd just like to add that we also said, that we would continue the
discussion to come up and agree on a list of concrete blockers for the
removal of SourceFunction, so that don't need to have the same discussion
again in half a year. And while we are add it, we should do the same
k
> [2] https://lists.apache.org/thread/j5d5022ky8k5t088ffm03727o5g9x9jr
>
> On Tue, Jul 25, 2023 at 8:49 PM Konstantin Knauf
> wrote:
>
> > I assume this vote includes a decision to not removing
> > SourceFunction/SinkFunction in Flink 2.0 (as it has be
I assume this vote includes a decision to not removing
SourceFunction/SinkFunction in Flink 2.0 (as it has been removed from the
table). If this is the case, I don't think, this discussion has concluded.
There are multiple contributors like myself, Martijn, Alex Fedulov and
Maximilian Michels, who
Konstantin Knauf created FLINK-32671:
Summary: Document Externalized Declarative Resource Management
Key: FLINK-32671
URL: https://issues.apache.org/jira/browse/FLINK-32671
Project: Flink
Hi Timo,
this makes sense to me. Option 3 seems reasonable, too.
Cheers,
Konstantin
Am Di., 25. Juli 2023 um 12:53 Uhr schrieb Timo Walther :
> Hi everyone,
>
> I would like to start a discussion about introducing the concept of
> "System Columns" in SQL and Table API.
>
> The subject sounds
o bugfixes. I would suggest supporting it for double the
> usual
> > amount of time (4 minor releases).
> >
> > On Tue, Jul 25, 2023 at 9:25 AM Konstantin Knauf
> > wrote:
> >
> > > Hi Alex,
> > >
> > > yes, I think, it makes sense to s
Hi Alex,
yes, I think, it makes sense to support the last 1.x release longer than
usual. This should be limited to bugfixes in my opinion.
Best,
Konstantin
Am Di., 25. Juli 2023 um 07:07 Uhr schrieb Xintong Song <
tonysong...@gmail.com>:
> Hi Alex,
>
> Providing a longer supporting period for
+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:10 PM Chesnay Schepler
> wrote:
>
> > Hello,
> >
> > I'd like to start a vote on FLIP-340.
> >
> > Discussion thread:
> >
+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'd like to start a vote on FLIP-336.
> >
> > Discussion thread:
> >
Konstantin Knauf created FLINK-32468:
Summary: Replace Akka by Pekko
Key: FLINK-32468
URL: https://issues.apache.org/jira/browse/FLINK-32468
Project: Flink
Issue Type: Improvement
+1. Thanks, Gordon!
Am Mo., 3. Apr. 2023 um 06:37 Uhr schrieb Tzu-Li (Gordon) Tai <
tzuli...@apache.org>:
> Hi Martijn,
>
> Since this RC vote was opened, we had three critical bug fixes that was
> merged for the Kafka connector:
>
>- https://issues.apache.org/jira/browse/FLINK-31363
>-
Congrats!
Am Mo., 27. März 2023 um 14:32 Uhr schrieb Leonard Xu :
> Congratulations!
>
>
> Best,
> Leonard
>
> On Mar 27, 2023, at 5:23 PM, Yu Li wrote:
>
> Dear Flinkers,
>
>
>
> As you may have noticed, we are pleased to announce that Flink Table Store
> has joined the Apache Incubator as a
Hi everyone,
"Nach dem Spiel ist vor dem Spiel" [1] aka "There is always a next
release". With the announcement of Flink 1.17, we have entered the next
release cycle and with it comes the usual routine:
- Release Managers
I'd like to volunteer as one of the release managers this time. It has
Hi Daniel,
I think, it would be great to have a PubSub Lite Connector in Flink. Before
you put this proposal up for a vote, though, we need feedback from a
Committer who would review and help maintain it going forward. Ideally,
this Committer would guide one or more contributors from Google to
+1 (binding)
Am Di., 28. Feb. 2023 um 15:02 Uhr schrieb John Roesler :
> Thanks for the FLIP, David!
>
> I’m +1 (non-binding)
>
> -John
>
> On Tue, Feb 28, 2023, at 07:46, David Morávek wrote:
> > Hi Everyone,
> >
> > I want to start the vote on FLIP-291: Externalized Declarative Resource
> >
Thanks, Martijn. That was a lot of work.
Am Do., 23. Feb. 2023 um 16:33 Uhr schrieb Maximilian Michels <
m...@apache.org>:
> Congrats! Great work. This was a long time in the making!
>
> -Max
>
> On Thu, Feb 23, 2023 at 3:28 PM Martijn Visser
> wrote:
> >
> > Hi everyone,
> >
> > The project
Hi Danny,
yes, this makes a lot of sense. We should probably by default just do one
more patch release shortly after the official support window has ended to
flush out all bug fixes.
Cheers,
Konstantin
Am Fr., 17. Feb. 2023 um 17:52 Uhr schrieb Danny Cranmer <
dannycran...@apache.org>:
>
+1
Am Mi., 15. Feb. 2023 um 15:21 Uhr schrieb Maximilian Michels <
m...@apache.org>:
> +1
>
> On Wed, Feb 15, 2023 at 12:32 PM Danny Cranmer
> wrote:
> >
> > Hi all,
> >
> > I would like to discuss creating a new 1.15 patch release (1.15.4). The
> > last 1.15 release is over three months old,
rote:
> >
> > > Hi Konstantin,
> > >
> > > Thanks for the comment! Please see my comment inline.
> > >
> > > Cheers,
> > > Dong
> > >
> > > On Sat, Feb 4, 2023 at 2:06 AM Konstantin Knauf
> > wrote:
> > >
Hi everyone,
sorry for joining the discussion late.
1) Is there an option to deprecate SinkFunction in Flink 1.17 while leaving
SinkV2 @PublicEvolving in Flink 1.17. We then aim to make SinkV2 @Public in
and remove SinkFunction in Flink 1.18. @PublicEvolving are intended for
public use. So, I
Hi everyone,
if I am not mistaken of the sinks mentioned by Joao Kafka, Kinesis &
Kinesis already use the Sink2 API. How were those implemented without
exposing the ExecutionConfig?
Best,
Konstantin
Am Mi., 1. Feb. 2023 um 12:28 Uhr schrieb Lijie Wang <
wangdachui9...@gmail.com>:
> +1 for
Great. Thanks, Martijn for managing the release.
Am Mi., 1. Feb. 2023 um 20:26 Uhr schrieb Martijn Visser <
martijnvis...@apache.org>:
> The Apache Flink community is very happy to announce the release of Apache
> Flink 1.16.1, which is the first bugfix release for the Apache Flink 1.16
>
es which is much harder than simply using active resource management.
>
> Cheers,
> Gyula
>
> On Thu, Jan 26, 2023 at 2:57 PM Konstantin Knauf
> wrote:
>
>> Hi Max,
>>
>> it seems to me we are now running in some of the potential duplication of
>> e
+1 (binding)
* checked Maven and source artifact signatures and checksums - OK
* no binaries or packaged dependencies - OK
* checked website changes - Approved.
Am Fr., 20. Jan. 2023 um 15:39 Uhr schrieb Martijn Visser <
martijnvis...@apache.org>:
> Hi everyone,
> Please review and vote on the
Hi Max,
it seems to me we are now running in some of the potential duplication of
efforts across the standard and adaptive scheduler that Chesnay had
mentioned on the original ticket. The issue of having to do a full restart
of the Job for rescaling as well as waiting for resources to be
Thanks, Martijn.
+1 (binding)
- Verified checksums and signatures for binaries & sources - OK
- checked pom changes for newly introduced dependencies - OK
- went over flink-web PR - Looks good except for Matthias' remarks
Am Do., 26. Jan. 2023 um 12:34 Uhr schrieb Sergey Nuyanzin <
Hi Becket,
> It is a basic rule of public API that anything exposed by a public
interface should also be public.
I agree with this in general. Did you get an overview of where we currently
violate this? Is this something that the Arc42 architecture tests could
test for so that as a first measure
Hi Martijn,
thanks for bringing it up and +1 to do a release rather soon.
Best,
Konstantin
Am Fr., 16. Dez. 2022 um 06:17 Uhr schrieb ConradJam :
> Hi Martijn,
>
> Thank you for bringing this up. I'm in favor of this proposal, by the way,
> FLINK-30116 has been fixed
>
>
>
> Martijn Visser
+1 (binding)
Am Fr., 16. Dez. 2022 um 15:31 Uhr schrieb Dong Lin :
> +1 (binding)
>
> Thanks for driving this!
>
> On Fri, Dec 16, 2022 at 6:17 PM Samrat Deb wrote:
>
> > Hi All, Thanks for all the feedback so far. Based on the discussion[1] we
> > seem to have a consensus, so I would like to
Hi Mason,
great, thanks a lot for working on this. Will greatly speed up CI of the
core repository once this is finalized.
Cheers
Konstantin
Am Mi., 7. Dez. 2022 um 07:23 Uhr schrieb Mason Chen :
> Hi all,
>
> I've finished the first pass on externalizing the Kafka connector under the
>
Hi Samrat,
+1 to the effort and +1 to adding it to flink-connector-aws.
Can you explain how users are expected to authenticate with AWS Glue? I
don't see any catalog options regardng authx. So I assume the credentials
are taken from the environment?
Best,
Konstantin
Am Fr., 9. Dez. 2022 um
Congrats to both.
Am Mi., 23. Nov. 2022 um 10:45 Uhr schrieb yu zelin :
> Congratulations，Godfrey and Xingbo!
>
> Best,
> Yu Zelin
> > 2022年11月23日 12:18，Dian Fu 写道：
> >
> > Hi everyone,
> >
> > On behalf of the Apache Flink PMC, I'm very happy to announce that
> Godfrey
> > He and Xingbo Huang
Congrats!
Am Di., 22. Nov. 2022 um 11:46 Uhr schrieb Péter Váry <
peter.vary.apa...@gmail.com>:
> Congratulations Mátyás!
>
> On Tue, Nov 22, 2022, 06:40 Matthias Pohl
> wrote:
>
> > Congratulations, Matyas :)
> >
> > On Tue, Nov 22, 2022 at 11:44 AM Xingbo Huang
> wrote:
> >
> > > Congrats
Konstantin Knauf created FLINK-30116:
Summary: Don't Show Env Vars in Web UI
Key: FLINK-30116
URL: https://issues.apache.org/jira/browse/FLINK-30116
Project: Flink
Issue Type
c), where my immediate gut instinct was that no ones
> > gonna bother to do that.
> >
> > as for e*) (opt-in flag that Gyula proposed); I think it's to easy to
> > shoot yourself in the foot somewhere down the line. It may be fine at
> > one point but setups evolve after
not printing them at all, i.e. option (d). We have the
> > configuration page which lists the effective config and already removes
> any
> > known secrets.
> >
> > -Max
> >
> > On Tue, Nov 15, 2022 at 11:26 AM Konstantin Knauf
> > wrote:
> >
Hi all,
since Flink 1.17 [1] the Flink Web UI prints *all* environment variables of
the Taskmanager or Jobmanagers hosts (Jobmanager -> Configuration ->
Environment). Given that environment variables are often used to store
sensitive information, I think, it is wrong and dangerous to print those
Hi everyone,
I agree with Xintong in the sense that I don't see what has changed since
the original decision on this topic. In my opinion, there is a high cost in
moving to ASF now, namely I fear we will loose many of the >1200 members
and the momentum that I see in the workspace. To me there
+1 (binding)
Am Fr., 28. Okt. 2022 um 16:58 Uhr schrieb Piotr Nowojski <
pnowoj...@apache.org>:
> Hi,
>
> As discussed on the dev mailing list [0] I would like to start a vote to
> drop support of older savepoint formats (for Flink versions older than
> 1.8). You can find the original
+1, thanks Fabian.
Am Mi., 26. Okt. 2022 um 08:26 Uhr schrieb Danny Cranmer <
dannycran...@apache.org>:
> +1, thanks for driving this Fabian.
>
> Danny,
>
> On Wed, Oct 26, 2022 at 2:22 AM yuxia wrote:
>
> > Thanks for driving this.
> > +1 for release 1.15.3
> >
> > Best regards,
> > Yuxia
> >
Hi everyone,
while I see some benefits in moving to Github Issues completely, we need to
be aware that Github Issues lacks many features that Jira has. From the top
of my head:
* there are no issue types
* no priorities
* issues can only be assigned to one milestone
So, you need to work a lot
+1
Am Do., 13. Okt. 2022 um 10:56 Uhr schrieb Niels Basjes :
> +1
>
> On Wed, Oct 12, 2022 at 11:00 PM Martijn Visser
> wrote:
>
> > Hi everyone,
> >
> > I would like to open a vote for dropping Gelly, which was discussed a
> long
> > time ago but never put to a vote [1].
> >
> > Voting will be
Make sense to me. It is moving us in the right direction and makes it
possible to drop these keys with Flink 2.0 if that ever happens :)
Am Mi., 21. Sept. 2022 um 16:06 Uhr schrieb Chesnay Schepler <
ches...@apache.org>:
> Hi,
>
> we have a small number of options in Flink whose key is a prefix
Hi everyone,
thanks for starting this discussion. I think, the flink-kubernetes and
flink repository are too different (age, size) to draw conclusions from
another. On a first thought, I am not a fan of having different processes
for different repositories inside the project.
The discussion
Sounds good. +1.
Am Di., 6. Sept. 2022 um 10:45 Uhr schrieb Jingsong Li <
jingsongl...@gmail.com>:
> +1 for 1.14.6
>
> Thanks Xingbo for driving.
>
> Best,
> Jingsong
>
> On Tue, Sep 6, 2022 at 4:42 PM Xingbo Huang wrote:
> >
> > Hi all,
> >
> > I would like to start discussing releasing Flink
+1. Thanks, Chesnay.
Am Di., 6. Sept. 2022 um 11:51 Uhr schrieb Chesnay Schepler <
ches...@apache.org>:
> Since no one objected in the discuss thread, let's vote!
>
> FLIP:
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=225152857
>
> The vote will be open for at least 72h.
>
Hi Martijn, Hi Mohammad,
thanks for creating this FLIP.
I am wondering, do you know how much Redis Streams are used compared to
other Redis data structures? At least as a sink and LookupTableSource
supporting regular Redis data structures seems quite useful.
I suppose such connectors would live
Hi Chesnay,
thanks for bringing this up and for your research and fixes to japicmd.
+1 for the proposal. For Immerok as an Apache Flink cloud service provider
it is very valuable to know that our users don't need to upgrade their Jobs
when the Flink patch version changes. I am sure the same is
Hi Ron,
thanks you for sharing your use case and your initiative to save Queryable
State. Queryable State was deprecated due to a lack of maintainers and thus
the community did not have resources to improve and develop it further. The
deprecation notice was added to signal this lack of attention
+1 (binding)
* checked checksum of binaries
* checked signatures of binaries & Maven artifacts
* checked dependency & NOTICE changes
* ran TopSpeedWindowing locally
Thanks for driving the release, Danny! Good job.
Am Di., 23. Aug. 2022 um 04:16 Uhr schrieb Peng Kang
:
> +1
>
> --
Hi Guillaume,
as long as those vulnerabilities have not been introduced since Flink
1.15.1, which they haven't, we can proceed with should not block the
release.
Best,
Konstantin
Am Di., 23. Aug. 2022 um 10:12 Uhr schrieb Guillaume Vauvert <
guillaume.vauvert@gmail.com>:
> Hello all,
>
>
+1. Thanks!
Am Mi., 20. Juli 2022 um 16:48 Uhr schrieb Tzu-Li (Gordon) Tai <
tzuli...@apache.org>:
> +1
>
> On Wed, Jul 20, 2022 at 6:13 AM Danny Cranmer
> wrote:
>
> > Hi there,
> >
> > After the discussion in [1], I’d like to open a voting thread for
> FLIP-252
> > [2], which proposes the
+1 (binding)
Am Mi., 20. Juli 2022 um 15:48 Uhr schrieb David Anderson <
dander...@apache.org>:
> +1
>
> Thank you Chesnay.
>
> On Tue, Jul 19, 2022 at 3:09 PM Alexander Fedulov >
> wrote:
>
> > +1
> > Looking forward to using the API to simplify tests setups.
> >
> > Best,
> > Alexander
Hi Blake,
thank you for reaching out. @PublicEvolving interface can only be changed
with a minor release of Apache Flink (e.g. 1.6). While the JavaDoc is
indeed ambiguous there was a FLIP recently that discussed this topic:
Makes sense to me. Thank you, Chesnay. +1
David Anderson schrieb am Fr., 8. Juli 2022, 13:56:
> I've found that with our current tooling it's frustrating to try to write
> good end-to-end tests for real-world jobs with multiple sinks.
> DataStream#executeAndCollect() is okay for simple
bugs or
> compatibility issues, they are blockers, not just the regressions
> brought about in the new fixes for 1.15.1.
>
> Best,
> Jingsong
>
> On Sat, Jul 2, 2022 at 2:09 AM Konstantin Knauf wrote:
> >
> > Hi everyone,
> >
> > I would like to raise th
Hi everyone,
I would like to raise the question if we should abort this release
candidate at the current stage because of newly found bugs?
* The minimal voting period had already passed and with one addition
binding vote (e.g. mine), we could release this immediately and ship all
the other
Sounds like a good plan. Thank you!
Am Fr., 17. Juni 2022 um 12:33 Uhr schrieb David Anderson <
dander...@apache.org>:
> After hitting pause on the 1.15.1 release a couple of days ago because of
> FLINK-28060 [1], I want to hit resume now. You should go read that ticket
> if you want the
+1 (binding)
* checked signatures and checksums of binaries -> OK
* skimmed over changes since 1.14.4 -> no dependency updates without NOTICE
updates
* reviewed release blog post and -> requested changes
Thanks for preparing this rc!
Konstantin
Am Fr., 10. Juni 2022 um 11:58 Uhr schrieb
+1 (binding)
Am Fr., 10. Juni 2022 um 18:20 Uhr schrieb Ran Tao :
> +1 non-binding
>
> for that we can't always block at 2.12.7. but we should let users know
> about this binary incompatibility if execute this update.
> btw, the configuration
> of scala-maven-plugin may need to update to match
gt;>>> impact of deprecating all SourceFunction subclasses is rather
> > >>> big,
> > >>>>> and
> > >>>>>> we
> > >>>>>>>> can expect it to
> > >>>>>>>> take a while. The h
eetings from the various
> SIGs:
> - Overview:
>
> https://github.com/kubernetes/community/blob/master/events/community-meeting.md
> - Calendar:
> https://calendar.google.com/calendar/u/0/embed?src=calen...@kubernetes.io
>
> Best,
> Robert
>
>
> On Tue, May
Hi everyone,
very interesting thread. The proposal for deprecation seems to have sparked
a very important discussion. Do we what users struggle with specifically?
Speaking for myself, when I upgrade flink-faker to the new Source API an
unbounded version of the NumberSequenceSource would have
Hi everyone,
can you be more specific what you mean by "current topics in the Flink
Community"? Shouldn't asynchronous communication be the default, and if
that doesn't work, we consider a synchronous channel?
Cheers,
Konstantin
Am Di., 31. Mai 2022 um 13:54 Uhr schrieb Jing Ge :
> +1
>
+1 for the user community, not the contributor/dev community
Am Do., 19. Mai 2022 um 12:44 Uhr schrieb Yuan Mei :
> +1 (binding)
>
> This facilitates people collaborating on the same project from different
> organizations. I really like this idea.
>
> On Thu, May 19, 2022 at 12:43 PM Peter Huang
t; Should we use PUT in this case? WDYT?
>
> Best,
> Lijie
>
> Konstantin Knauf 于2022年5月13日周五 17:20写道：
>
> > Hi Lijie,
> >
> > wouldn't the REST API-idiomatic way for an update/replace be a PUT on the
> > resource?
> >
> > PUT: htt
Thanks a lot for taking care of this, Martijn!
Am Fr., 13. Mai 2022 um 12:59 Uhr schrieb Martijn Visser <
martijnvis...@apache.org>:
> Hi everyone,
>
> I noticed that multiple e2e tests had debugging logged enabled. Quite a few
> of them have done that for a long time; however, since we are
>> > > > > >> > >> > > If it's possible I'd like to participate in
> >> development.
> >> > > > > >> > >> > >
> >> > > > > >> > >> > > I agree with 3rd point of Konstantin's reply - we
> >> should
> >> > > &g
Hi Martijn,
+1 to do a release which is compatible with Flink 1.5.x. With the release,
we should add something like a compatibility matrix to the documentation,
but I am sure that's already on your list.
Cheers,
Konstantin
Am Mi., 11. Mai 2022 um 20:10 Uhr schrieb Martijn Visser <
'm a bit concerned about the maintenance overhead. I'm not
> very familiar with Discourse or Reddit. My impression is that they are not
> as easy to set up and maintain as Slack.
>
> Thank you~
>
> Xintong Song
>
>
> [1] https://asktug.com/
>
> On Tue, May 10,
Hi there,
are you using any of Flink S3 Filesystems? If so, where do you load it from
a) lib/
b) plugins/
c) bundled with your Job in a fat JAR
b) would be the right way to do it in Flink 1.13. I don't know if this
fixes the issue, but IIRC because we introduced the plugin mechansim we
don't
Hi Matyas,
yes, that's expected. The feature should have never been called "high
availability", but something like "Flink Jobmanager failover", because
that's what it is.
With standby Jobmanagers what you gain is a faster failover, because a new
Jobmanager does not need to be started before
Thanks for starting this discussion again. I am pretty much with Timo here.
Slack or Discourse as an alternative for the user community, and mailing
list for the contributing, design discussion, etc. I definitely see the
friction of joining a mailing list and understand if users are intimidated.
Hi Xintong,
it is a pity that we can only have 5 maintainers. Every (patch) release of
flink, flink-statefun, the flink-kubernetes-operator requires a maintainer
to publish the image then, if I am not mistaken. As its mostly different
groups managing the sub-projects, this is quite the
; > > > extend this deadline for that reason :)
> > > > >
> > > > > Best regards,
> > > > >
> > > > > Martijn Visser
> > > > > https://twitter.com/MartijnVisser82
> > > > > https://github.c
Congratulations to everyone!
Thanks to Yun Gao, Joe Moser & Till Rohrmann for managing this release.
It's done :)
Am Do., 5. Mai 2022 um 09:57 Uhr schrieb Xintong Song :
> Congratulations~!
>
> Thank the release managers, and thank all who contributed to this release.
>
> Thank you~
>
> Xintong
+1 (binding)
* mvn clean package - PASSED
* checked signatures & checksums of source artifacts - OK
* went through quick start - WORKS
* skimmed over NOTICE file - LOOKS GOOD
I also read over the announcement blog post. In my opinion, we could try to
motivate the project a bit better. What is
ards,
> > >
> > > Martijn Visser
> > > https://twitter.com/MartijnVisser82
> > > https://github.com/MartijnVisser
> > >
> > >
> > > On Tue, 26 Apr 2022 at 13:19, godfrey he wrote:
> > >
> > > > Hi Konstantin & Ch
Hi Lijie,
I think, this makes sense and +1 to only support manually blocking
taskmanagers and nodes. Maybe the different strategies can also be
maintained outside of Apache Flink.
A few remarks:
1) Can we use another term than "bla.cklist" due to the controversy around
the term? [1] There was
Hi everyone,
With Flink 1.15 about to be released, the community has started planning &
developing features for the next release, Flink 1.16. As such, I would like
to start a discussion around managing this release.
Specifically, Chesnay & myself would like to volunteer as release managers.
Our
; >
> > cons.
> > 1. Need to maintain an additional Calcite repository
> > 2. The Upgrades are a little more complicated than before
> >
> > Any feedback is very welcome!
> >
> >
> > [1]
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-204%3A+Introduce+Hash+Lookup+Join
> > [2]
> https://github.com/apache/flink/tree/master/flink-table/flink-table-planner/src/main/java/org/apache/calcite
> > [3] https://github.com/apache/drill/blob/master/pom.xml#L64
> >
> > Best,
> > Godfrey
>
>
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
.
> >
> > Best,
> > Sebastian
> >
> > [1]
> >
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-217+Support+watermark+alignment+of+source+splits
> > [2] https://github.com/dawidwys/flink/tree/aligned-splits
> >
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
; implementation around it.
>
> 2. In Flink 1.15, there are Async Sinks (
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-171%3A+Async+Sink)
> but not much documentation around. Also don't know if it would be
> achievable to write the continuous firing logic in alertmanager
>
> Any
plication 写成了 yarn-appliation的话
> 就会报错
> [image: image.png]
> 这里我看了代码是CliFrontend 封装的 213行的配置集合 effectiveConfiguration
> 有问题，导致DefaultClusterClientServiceLoader.java:83 判断进入报错
> [image: image.png]
> 我觉得这里的报错信息的描述有问题 会造成误导，是使用者误认为是自己的HADOOP_CLASSPATH 环境有问题，希望可以得到大家的回复
>
--
> we move more and more in a Scala-free direction.
> >
> > The Scala-free direction means users can pick arbitrary Scala versions,
> not
> > drop the Scala API.
> > So the "Language Tabs" is still necessary and helpful for switching
> > languages
cala-free direction means users can pick arbitrary Scala versions, not
> drop the Scala API.
> So the "Language Tabs" is still necessary and helpful for switching
> languages.
>
> Best,
> Jark
>
> [1]:
>
> https://nightlies.apache.org/flink/flink-docs-master/docs
h both have not been implemented, are partially
contradicting each other and are generally out-of-date. I specifically
don't intend to add another FLIP to this graveyard, but still reach a
consensus on the high-level direction.
What do you think?
Cheers,
Konstantin
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
eel packages?
>
> Best,
> Xingbo
>
> Leonard Xu 于2022年3月16日周三 01:02写道：
>
>> Thanks a lot for being our release manager Konstantin and everyone who
>> involved!
>>
>> Best,
>> Leonard
>>
>> 2022年3月15日 下午9:34，Martijn Visser 写道：
>>
&
in Jira:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351231
We would like to thank all contributors of the Apache Flink community who
made this release possible!
Regards,
Konstantin
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
gt;> Best,
> > > > > >>>>> Leonard
> > > > > >>>>>
> > > > > >>>>>> 2022年3月14日 下午4:09，Yangze Guo 写道：
> > > > > >>>>>>
> > > > > >>>>>> Congratulations!
> > &
still a couple missing features that we need to iron out and we
> > need to make sure we have proper documentation but after that I think it
> > would be a good time for the preview release.
> >
> > I propose to aim for the first release candidate around the 25-27th of
&g
:
> Hi Developers,
>
> I wish to add a new library to existing flink docker image since it’s a
> dependency requirement in my processor.
> Is it possible to add?
>
> apt-get install libatomic1
>
> Thanks,
> Julius
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
1 - 100 of 470 matches
Mail list logo
