ailing-list-archive.1008284.n3.nabble.com/SURVEY-Remove-Mesos-support-td45974.html
> [2] https://flink.apache.org/roadmap.html#feature-radar
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
Nico
have provided feedback that this is too aggressive).
* exclude Sub-Tasks from all rules except the "stale-assigned" rule (I
think, this was just an oversight in the original discussion.)
Keep it coming.
Cheers,
Konstantin
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
a/browse/FLINK-10911
> > >
> > >
> > > Martijn Visser | Product Manager
> > >
> > > mart...@ververica.com
> > >
> > > <https://www.ververica.com/>
> > >
> > >
> > > Follow us @VervericaData
> > >
> > > --
> > >
> > > Join Flink Forward <https://flink-forward.org/> - The Apache Flink
> > > Conference
> > >
> > > Stream Processing | Event Driven | Real Time
> > >
> >
> >
> > --
> > Best Regards
> >
> > Jeff Zhang
> >
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
nt pieces of the code base, principles, assumptions,
... and hand over open threads.
If you would like to take on this responsibility or can join this effort in
a supporting role, please reach out!
Cheers,
Konstantin
for the Deployment & Coordination Team at Ververica
--
Konstantin K
anks,
>
> Martijn
>
> [1]
>
> https://issues.apache.org/jira/secure/ShowConstantsHelp.jspa?decorator=popup#PriorityLevels
>
> On Wed, 28 Jul 2021 at 16:06, Konstantin Knauf wrote:
>
> > Hi everyone,
> >
> > well that escalated quickly :) Let me shar
se issues?
> 3. If not, how can we help contribute to a solution?
> 4. Are there officially supported non-Debian based Flink images?
>
> We appreciate the insights and look forward to working with the community
> on a solution.
>
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
his.
> >
> > Thank you~
> >
> > Xintong Song
> >
> >
> >
> > On Thu, Jul 29, 2021 at 5:04 PM Márton Balassi >
> > wrote:
> >
> > > Hi Konstantin,
> > >
> > > Thank you for raising this topic, our develop
>
> We would like to thank all contributors of the Apache Flink community
> who made this release possible!
>
> Regards,
> Chesnay
>
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
en using the DataStream
> > APIs, for example to convert an input stream of JSON from Kafka to a Row
> > instance.
> >
> > Do you have any opinions about deprecating these classes in 1.15 and then
> > drop them in 1.16? Or are you using them? If yes, can you describe your
> use
> > case?
> >
> > Thank you,
> >
> > FG
> >
>
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
lematic because
> > you'd still work against the latest snapshots, and they not be
> > compatible with each other.
> >
> >
> > On 18/10/2021 15:22, Arvid Heise wrote:
> > > I was actually betting on snapshots versions. What are the limits?
> > > Obviously, we can only do a release of a 1.15 connector after 1.15 is
> > > release.
> >
> >
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
s everything ASF. More often it is
> > >> "Apache Foo". It would be fatal to end up with a patchwork of projects
> > >> with potentially different licenses and governance to arrive at a
> > >> working Flink setup. This may mean we prioritize usabili
rica.com
>
> <https://www.ververica.com/>
>
>
> Follow us @VervericaData
>
> --
>
> Join Flink Forward <https://flink-forward.org/> - The Apache Flink
> Conference
>
> Stream Processing | Event Driven | Real Time
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
like updating some e2e tests to actually run on
> Java 11, performance benchmarking etc. .
>
> There is no set date for the removal of Java 8 support.
>
> We'll use the usual minimum 72h vote duration, with committers having
> binding votes.
>
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
side a
> > > CepOperator and does not support changing the pattern dynamically. In
> order
> > > to reduce resource consumption and to experience shorter downtime
> during
> > > pattern updates, there is a growing need in the production environment
> that
> > > expects CEP to support having multiple patterns in one operator and to
> > > support dynamically changing them. Therefore I propose to add certain
> > > infrastructure as described in FLIP-200 to support these
> functionalities.
> > >
> > > Please feel free to reply to this email thread. Looking forward to your
> > > feedback!
> > >
> > > [1]
> > >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=195730308
> > >
> > > Best regards,
> > >
> > > Yunfeng
> > >
> >
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
und in case we need to
> > revert
> > >> - Timeframe: 1-2 weeks
> > >>
> > >> *Phase 5: *Removal of Azure CI leftovers
> > >> - Only after we are satisfied that GHA is stable (at least 1 month
> after
> > >> the switch, can be longer)
> > >> - Green GHA build is required from now on
> > >> - Stale PRs that don't have a GHA run will have to trigger a new one
> > (but
> > >> they would most likely have to rebase anyway...)
> > >> - (old) FlinkCIBot is disabled
> > >> - Azure yamls are deleted
> > >> - Azure runners are removed from machines
> > >>
> > >>
> > >> Timing-wise, the full switch to GHA should happen during a quiet time,
> > far
> > >> away from a release. The remaining phases shouldn't have much impact,
> > but
> > >> right before a release is not a good moment, of course.
> > >> Please give us your thoughts and point out anything we missed or that
> > >> doesn't seem to make sense!
> > >>
> > >> Best,
> > >> Nico
> >
> >
> >
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
for 1.14.1
> > > > > >> >> > >>>> > [3]. I'm including the ones that are currently
> marked
> > as
> > > > > >> >> critical or a
> > > > > >> >> > >>>> > blocker to verify if these should be included in
> > Flink 1.14.1.
> > > > > >> >> It would be
> > > > > >> >> > >>>> > great if those that are assigned or working on one
> or
> > more of
> > > > > >> >> these tickets
> > > > > >> >> > >>>> > can give an update on its status.
> > > > > >> >> > >>>> >
> > > > > >> >> > >>>> > * https://issues.apache.org/jira/browse/FLINK-24543
> -
> > > > > >> Zookeeper
> > > > > >> >> connection
> > > > > >> >> > >>>> > issue causes inconsistent state in Flink -> I think
> > this
> > > > > >> depends
> > > > > >> >> on the
> > > > > >> >> > >>>> > outcome of dropping Zookeeper 3.4 as was proposed on
> > the Dev
> > > > > >> >> mailing list
> > > > > >> >> > >>>> > * https://issues.apache.org/jira/browse/FLINK-25027
> > - Allow
> > > > > >> GC
> > > > > >> >> of a
> > > > > >> >> > >>>> > finished job's JobMaster before the slot timeout is
> > reached
> > > > > >> >> > >>>> > * https://issues.apache.org/jira/browse/FLINK-25022
> -
> > > > > >> >> ClassLoader leak with
> > > > > >> >> > >>>> > ThreadLocals on the JM when submitting a job through
> > the REST
> > > > > >> API
> > > > > >> >> > >>>> > * https://issues.apache.org/jira/browse/FLINK-24789
> -
> > > > > >> >> IllegalStateException
> > > > > >> >> > >>>> > with CheckpointCleaner being closed already
> > > > > >> >> > >>>> > * https://issues.apache.org/jira/browse/FLINK-24328
> > - Long
> > > > > >> term
> > > > > >> >> fix for
> > > > > >> >> > >>>> > receiving new buffer size before network reader
> > configured ->
> > > > > >> >> I'm not sure
> > > > > >> >> > >>>> > if this would end up in Flink 1.14.1, I think it's
> > more likely
> > > > > >> >> that it
> > > > > >> >> > >>>> > would be Flink 1.15. Anton/Dawid, could you confirm
> > this?
> > > > > >> >> > >>>> > * https://issues.apache.org/jira/browse/FLINK-23946
> -
> > > > > >> >> Application mode
> > > > > >> >> > >>>> > fails fatally when being shut down -> This depends
> on
> > > > > >> >> > >>>> > https://issues.apache.org/jira/browse/FLINK-24038
> > and I don't
> > > > > >> >> see much
> > > > > >> >> > >>>> > happening there, so I also expect that this would
> > move to
> > > > > >> Flink
> > > > > >> >> 1.15.
> > > > > >> >> > >>>> > David, could you confirm?
> > > > > >> >> > >>>> > * https://issues.apache.org/jira/browse/FLINK-22113
> -
> > > > > >> UniqueKey
> > > > > >> >> constraint
> > > > > >> >> > >>>> > is lost with multiple sources join in SQL
> > > > > >> >> > >>>> > * https://issues.apache.org/jira/browse/FLINK-21788
> > - Throw
> > > > > >> >> > >>>> > PartitionNotFoundException if the partition file has
> > been lost
> > > > > >> >> for blocking
> > > > > >> >> > >>>> > shuffle -> I'm also expecting that this would move
> to
> > Flink
> > > > > >> >> 1.15, can you
> > > > > >> >> > >>>> > confirm Yingjie ?
> > > > > >> >> > >>>> >
> > > > > >> >> > >>>> > There are quite some other tickets that I've
> excluded
> > from
> > > > > >> this
> > > > > >> >> list,
> > > > > >> >> > >>>> > because they are either test instabilities or are
> not
> > > > > >> depending
> > > > > >> >> on a Flink
> > > > > >> >> > >>>> > release to be resolved.
> > > > > >> >> > >>>> >
> > > > > >> >> > >>>> > Note: there are quite a few test instabilities in
> the
> > list and
> > > > > >> >> help on
> > > > > >> >> > >>>> > those is always appreciated. You can check all
> > unassigned
> > > > > >> tickets
> > > > > >> >> > >>>> > instabilities in Jira [4].
> > > > > >> >> > >>>> >
> > > > > >> >> > >>>> > Are there any other open tickets that we should wait
> > for? Is
> > > > > >> >> there a PMC
> > > > > >> >> > >>>> > member who would like to manage the release? I'm
> more
> > than
> > > > > >> happy
> > > > > >> >> to help
> > > > > >> >> > >>>> > with monitoring the status of the tickets.
> > > > > >> >> > >>>> >
> > > > > >> >> > >>>> > Best regards,
> > > > > >> >> > >>>> >
> > > > > >> >> > >>>> > Martijn
> > > > > >> >> > >>>> >
> > > > > >> >> > >>>> > [1]
> > > > > >> https://flink.apache.org/news/2021/09/29/release-1.14.0.html
> > > > > >> >> > >>>> > [2]
> > > > > >> >> > >>>> >
> > > > > >> >>
> > > > > >>
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%201.14.1%20ORDER%20BY%20priority%20DESC%2C%20created%20DESC
> > > > > >> >> > >>>> > [3]
> > > > > >> >> > >>>> >
> > > > > >> >>
> > > > > >>
> >
> https://issues.apache.org/jira/issues?jql=project%20%3D%20FLINK%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20fixVersion%20%3D%201.14.1%20ORDER%20BY%20priority%20DESC%2C%20created%20DESC
> > > > > >> >> > >>>> >
> > > > > >> >> > >>>> > [4]
> > > > > >> >> > >>>> >
> > > > > >> >>
> > > > > >>
> >
> https://issues.apache.org/jira/issues?jql=project%20%3D%20FLINK%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20fixVersion%20%3D%201.14.1%20AND%20labels%20%3D%20test-stability%20AND%20assignee%20in%20(EMPTY)%20ORDER%20BY%20priority%20DESC%2C%20created%20DESC
> > > > > >> >> > >>>> >
> > > > > >> >> > >>>> > Martijn Visser | Product Manager
> > > > > >> >> > >>>> >
> > > > > >> >> > >>>> > mart...@ververica.com
> > > > > >> >> > >>>> >
> > > > > >> >> > >>>> > <https://www.ververica.com/>
> > > > > >> >> > >>>> >
> > > > > >> >> > >>>> >
> > > > > >> >> > >>>> > Follow us @VervericaData
> > > > > >> >> > >>>> >
> > > > > >> >> > >>>> > --
> > > > > >> >> > >>>> >
> > > > > >> >> > >>>> > Join Flink Forward <https://flink-forward.org/> -
> > The Apache
> > > > > >> >> Flink
> > > > > >> >> > >>>> > Conference
> > > > > >> >> > >>>> >
> > > > > >> >> > >>>> > Stream Processing | Event Driven | Real Time
> > > > > >> >> > >>>> >
> > > > > >> >> > >>>>
> > > > > >> >> > >>
> > > > > >> >> > >>
> > > > > >> >> > >> --
> > > > > >> >> > >> Marios
> > > > > >> >>
> > > > > >> >>
> > > > > >> >>
> > > > > >> >> --
> > > > > >> >> Best, Jingsong Lee
> > > > > >> >>
> > > > > >> >
> > > > > >>
> > > > > >
> >
> >
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
>> > was released on the 29th of September [1] and so
> far
> > >> 107
> > >> > > >> issues
> > >> > > >> >> have been
> > >> > > >> >> > >>>> > resolved, including multiple blockers and critical
> > >> priorities
> > >> > > >> >> [2].
>
each TaskManager are consistent.
> > We
> > > > will describe how to deal with the Failover scenario in more detail
> on
> > > FLIP.
> > > >
> > > > Thanks for that. I think having the JobManager tell the TaskManagers
> > the
> > > >
> Piotrek
>
> [1]
>
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-193%3A+Snapshots+ownership
> [2]
>
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-203%3A+Incremental+savepoints#FLIP203:Incrementalsavepoints-Semantic
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
gt; [1] https://cwiki.apache.org/confluence/x/bIyqCw
>
>
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
gging/metrics without losing
> > >>>>>> useful
> > >>>>>>>>>>>> information.
> > >>>>>>>>>>>>>>> 2. introduce a tree-mode vertex description which
> > >> can
> > >>&g
hat support "fast" copy (ideally with latency numbers).
>
> Regards,
> Roman
>
> On Mon, Nov 22, 2021 at 9:24 AM Yun Gao
>
> wrote:
>
> Hi,
>
> Very thanks Dawid for proposing the FLIP to clarify the ownership for the
> states. +1 for the overall changes since it makes the behavior clear and
> provide users a determined method to finally cleanup savepoints / retained
> checkpoints.
>
> Regarding the changes to the public interface, it seems currently the changes
> are all bound
> to the savepoint, but from the FLIP it seems perhaps we might also need to
> support the claim declaration
> for retained checkpoints like in the cli side[1] ? If so, then might it be
> better to change the option name
> from `execution.savepoint.restore-mode` to something like
> `execution.restore-mode`?
>
> Best,
> Yun
>
>
> [1]
> https://nightlies.apache.org/flink/flink-docs-master/docs/ops/state/checkpoints/#resuming-from-a-retained-checkpoint
>
>
> --
> From:Konstantin Knauf
>
> Send Time:2021 Nov. 19 (Fri.) 16:00
> To:dev
>
> Subject:Re: [DISCUSS] FLIP-193: Snapshots ownership
>
> Hi Dawid,
>
> Thanks for working on this FLIP. Clarifying the differences and
> guarantees around savepoints and checkpoints will make it easier and safer
> for users and downstream projects and platforms to work with them.
>
> +1 to the changing the current (undefined) behavior when recovering from
> retained checkpoints. Users can now choose between claiming and not
> claiming, which I think will make the current mixed behavior obsolete.
>
> Cheers,
>
> Konstantin
>
> On Fri, Nov 19, 2021 at 8:19 AM Dawid Wysakowicz
>
> wrote:
>
> Hi devs,
>
> I'd like to bring up for a discussion a proposal to clean up ownership
> of snapshots, both checkpoints and savepoints.
>
> The goal here is to make it clear who is responsible for deleting
> checkpoints/savepoints files and when can that be done in a safe manner.
>
> Looking forward for your feedback!
>
> Best,
>
> Dawid
>
> [1] https://cwiki.apache.org/confluence/x/bIyqCw
>
>
>
> --
>
> Konstantin Knaufhttps://twitter.com/snntrablehttps://github.com/knaufk
>
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
gt;>
> > >> The vote will be open for at least 72 hours unless there is an
> objection
> > >> or not enough votes.
> > >>
> > >> [1]
> > >>
> >
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-189%3A+SQL+Client+Usability+Improvements
> > >> [2] https://lists.apache.org/thread/8d580jcqzpcbmfwqvhjso82hdd2x0461
> > >>
> > >> --
> > >> Best,
> > >> Sergey
> > >>
> > >
> > >
> >
> >
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
PMC, I'm very happy to announce Ingo Bürk as a
> >> new
> >>>>>>> Flink
> >>>>>>>>> committer.
> >>>>>>>>>
> >>>>>>>>> Ingo has started contributing to Flink since the
>>>>>>> Matthias has worked on Flink since August last year. He helped
> >> review
> >>>>>> a ton
> >>>>>>>> of PRs. He worked on a variety of things but most notably the
> >> tracking
> >>>>>> and
> >>>>>>>> reporting of concurrent exceptions, fixing HA bugs and deprecating
> >> and
> >>>>>>>> removing our Mesos support. He actively reports issues helping
> >> Flink
> >>>> to
> >>>>>>>> improve and he is actively engaged in Flink's MLs.
> >>>>>>>>
> >>>>>>>> Please join me in congratulating Matthias for becoming a Flink
> >>>>>> committer!
> >>>>>>>> Cheers,
> >>>>>>>> Till
> >>>>>>>>
> >>>>
> >>>>
> >>
> > --
> >
> > Martijn Visser | Product Manager
> >
> > mart...@ververica.com
> >
> > <https://www.ververica.com/>
> >
> >
> > Follow us @VervericaData
> >
> > --
> >
> > Join Flink Forward <https://flink-forward.org/> - The Apache Flink
> > Conference
> >
> > Stream Processing | Event Driven | Real Time
>
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
; not enough votes.
>
> Best,
>
> Dawid
>
> [1] https://cwiki.apache.org/confluence/x/bIyqCw
>
> [2] https://lists.apache.org/thread/zw2crf0c7t7t4cb5cwcwjpvsb3r1ovz2
>
>
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
e problem of how to make sure
> that APIs become stable over time.
>
> Looking forward to your feedback.
>
> [1] https://cwiki.apache.org/confluence/x/IJeqCw
> [2] https://lists.apache.org/thread/5jm25783oq5svyk7rr8g1gly2ooxqhjr
> [3] https://lists.apache.org/thread/kzhfc3t6omzo2
k.
>
> Hopefully, we can provide our users a better experience when working with
> Flink because we offer more stable APIs and make them available faster.
>
> [1] https://cwiki.apache.org/confluence/x/J5eqCw
> [2] https://cwiki.apache.org/confluence/x/IJeqCw
>
> Che
moving this from Flink will slightly shrink the
>> codebase and CI runtime.
>>
>> I'm also cross posting this to the User mailing list, in case there's
>> still anyone who's using MapR.
>>
>> Best regards,
>>
>> Martijn
>>
>> [1]
>>
ncy. Meaning not waiting for the next bug fix
> > > releases
> > > > > > >>> coming in a few weeks, but releasing asap.
> > > > > > >>> The mood I perceive in the industry is pretty much panicky
> over
> > > this,
> > >
ynamic rule changing mechanism.
>
> Best,
> Nicholas Jiang
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
euse the Pattern concept for the
> DynamicPattern renaming?
>
> Best,
> Nicholas Jiang
>
> On 2021/12/13 07:45:04 Konstantin Knauf wrote:
> > Thanks, Yufeng, for starting this discussion. I think this will be a very
> > popular feature. I've seen a lot of users asking for this in th
> PatternProcessFunction, but the Pattern or DynamicPattern doesn't contain
> the function.
>
> Best
> Nicholas Jiang
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
lt;https://flink-forward.org/> - The Apache Flink
> Conference
>
> Stream Processing | Event Driven | Real Time
>
> --
>
> Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany
>
> --
>
> Ververica GmbH
>
> Registered at Amtsgericht Charlottenburg: HRB 158
onable
> > > change. But I think it would be better to handle different types of
> > tickets
> > > respectively. For example, for bugs a default major seems to be better,
> > > while for others the default shall be minor.
> > >
> > > Kons
ntin
[1] https://lists.apache.org/x/list.html?dev@flink.apache.org:lte=1M:
[2] https://github.com/apache/flink-jira-bot
[3]
https://cwiki.apache.org/confluence/display/FLINK/Flink+Jira+Process#FlinkJiraProcess-TicketsPriorities
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
1 at 12:40, Yun Tang wrote:
>
> > Hi Konstantin,
> >
> > How about rename "Major" to "Normal"? We already have higher critical and
> > blocker priorities, and I personally usually treat current "major" as
> > "normal" priority
o be a subproject of flink, just -1
> > >
> > > The vote will be open for at least 72 hours unless there is an
> > > objection or not enough votes.
> > >
> > > [1]
> >
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-188%3A+Introduce+Built-in+Dynamic+Table+Storage
> > >
> > > Best,
> > > Jingsong
> > >
> >
> >
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
need to be fixed
> before release. So that would be the case where fixVersion is set
> upfront.
>
> Thanks,
> Thomas
>
> [1]
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20Flink%20and%20fixVersion%20%3D%201.14.4%20and%20resolution%20%3D%20Unresolved%20
> [2]
> h
reen deployment.
>>>> >
>>>> >
>>>> > To sum this up, I'd really love if Flink could provide great out-of
>>>> the box experience with standalone mode on k8s, that makes the experience
>>>> as close to running / operating any other
gt; Wenhao
> >
> > On Tue, Jan 11, 2022 at 8:24 PM Martijn Visser
> wrote:
> > >
> > > Hi all,
> > >
> > > I agree with Konstantin, this feels like a problem that shouldn't be
> solved
> > > via Apache Flink but via the logging ecosystem
t; [5]
>
> Best regards,
>
> Martijn
> https://twitter.com/MartijnVisser82
>
> [1] https://privacy.apache.org/faq/committers.html
> [2] https://matomo.org/
> [3]
>
> https://drive.google.com/file/d/1yomYhLoyrzBW620bpn_dROiwyvSCzuvt/view?usp=sharing
> [4] https://github.com/MartijnVisser/matomo-analytics
> [5] https://infra.apache.org/vm-for-project.html
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
heers and thank you,
Konstantin
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
allocate a new one timely.
>
> Thanks for sharing this, we should evaluate it as part of a proposal.
> If we can optimize recovery or scaling with active resource management
> then perhaps it is worth to support it through the operator.
> Previously mentioned operators all rely
d could be as simple as adding test coverage but that's an
> active
> > > decision we'd need to make.
> > >
> > > On Tue, Dec 21, 2021 at 7:43 AM Piotr Nowojski
> > > wrote:
> > >
> > > > Hi Konstantin,
> > > >
> > > > >
t; Personally I still think that the the current capabilities are
> sufficient, and I do not want us to rely on internals of the logging
> backends in production code.
>
> On 10/01/2022 17:26, Konstantin Knauf wrote:
> > Thank you for starting the discussion. Being able to change t
f96c249cbc17ce062491bfbb39d484e241ab168/storm-client/src/jvm/org/apache/storm/daemon/worker/LogConfigManager.java#L144
> [8]:
> https://github.com/spring-projects/spring-boot/blob/main/spring-boot-project/spring-boot/src/main/java/org/springframework/boot/logging/LoggingSystem.java#L164
> [9]:
:
> 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
v
> > Subject: Re: [VOTE] Release 1.14.4, release candidate #1
> >
> > +1 non-binding
> >
> > - built from source
> > - checked hashes and signatures
> > - started locally and deployed wordcount / stopped with savepoint /
> > restarted
> > -
Hi everyone,
I am pleased to announce that we have unanimously approved this release
candidate:
There are 5 approving votes, 3 of which are binding:
- Seth Wiesman (non-binding)
- Yun Tang (non-binding)
- Yun Gao (binding)
- Timo Walther (binding)
- Konstantin Knauf (binding
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
gt;> Best,
> > > > > >>>>> Leonard
> > > > > >>>>>
> > > > > >>>>>> 2022年3月14日 下午4:09，Yangze Guo 写道：
> > > > > >>>>>>
> > > > > >>>>>> Congratulations!
> > &
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
cations and don't have the main()
> > > method.
> > > For example, SQL CLI submits SQL jobs by invoking
> > > `StreamExecutionEnvironment#executeAsync(StreamGraph)`.
> > > How SQL Client and SQL platforms (e.g. Zeppelin) support application
> > mode?
&
gt; wrote:
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Hi team,
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Thank you for the great feedback,
> > Thomas
> > > has
> > > > > > > > updated
> > > > > > >
Best,
>
> Qingsheng Ren
>
> [1] https://issues.apache.org/jira/browse/FLINK-26018
>
> > On Feb 11, 2022, at 5:29 PM, Konstantin Knauf wrote:
> >
> > Hi everyone,
> >
> > what do you think about a timely Flink 1.14.4 in order to release the fix
2022 09:30, Dawid Wysakowicz пишет:
> > +1 (binding)
> >
> >
> > - signatures OK
> > - checksums OK
> > - tag OK
> > - PR looks good
> >
> > - built from sources
> >
> > - run example
> >
> > - checked dependency version chang
Hi everyone,
I am pleased to announce that we have unanimously approved this release
candidate:
There are 4 approving votes, 3 of which are binding:
- Chesnay Schepler (binding)
- Dawid Wysakowicz (binding)
- Anton Kalashnikov (non-binding)
- Konstantin Knauf (binding)
There are no disapproving
Therefore, I propose to disable this bot. Please let me know if you
> disagree, otherwise, I'll soon disable it.
>
>
> Best,
> Robert
>
>
> [1]https://github.com/apache/flink/pull/18818#issuecomment-1042865516
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
in Jira:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351074
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
orward to your thoughts on this!
>
> Best regards,
>
> Martijn Visser
> https://twitter.com/MartijnVisser82
>
> [1] https://lists.apache.org/thread/bywh947r2f5hfocxq598zhyh06zhksrm
> [2] https://lists.apache.org/thread/bk9f91o6wk66zdh353j1n7sfshh262tr
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
llows:
> >>>
> >>> 1. We wait until the Flink 1.15 release branch is cut
> >>> 2. When that's done, the Elasticsearch code (including commit history)
> >> from
> >>> Flink's 1.15 release branch will be moved to the
> >>> flink-connector-elasticsearch main branch.
> >>> 3. When Flink 1.15 is released, we will also release an Elasticsearch
> >>> connector for the external connector repository with version 3.0.0.
> >>> 4. Bugfixes or improvements will be made first pointing to the external
> >>> connector repository and will be cherry-picked back to the release-1.15
> >>> branch in the Flink core repository.
> >>> 5. The Elasticsearch code, test etc will be removed from the master
> >> branch
> >>> in the Flink core repository and dropped with Flink 1.16
> >>>
> >>> Looking forward to your thoughts on this!
> >>>
> >>> Best regards,
> >>>
> >>> Martijn Visser
> >>> https://twitter.com/MartijnVisser82
> >>>
> >>> [1]https://lists.apache.org/thread/bywh947r2f5hfocxq598zhyh06zhksrm
> >>> [2]https://lists.apache.org/thread/bk9f91o6wk66zdh353j1n7sfshh262tr
> >>>
> >>
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
ed
> warrant
> > > a speedy Flink 1.14.4 release. I would indeed also like to include
> > > FLINK-26018.
> > >
> > > Best regards,
> > >
> > > Martijn
> > >
> > > Op vr 11 feb. 2022 om 10:29 schreef Konstantin Knauf <
>
; Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany
>
> --
>
> Ververica GmbH
>
> Registered at Amtsgericht Charlottenburg: HRB 158244 B
>
> Managing Directors: Karl Anton Wehner, Holger Temme, Yip Park Tung Jason,
> Jinwei (Kevin) Zhang
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
ons and well deserved Martjin !
> > > > > > > > > > > > >
> > > > > > > > > > > > > Best,
> > > > > > > > > > > > > Leonard
> > > > > > > > > > > > >
> > > > > > > > > > > > >> 2022年3月4日 上午7:55，Austin Cawley-Edwards <
> > > > > > austin.caw...@gmail.com
> > > > > > > > >
> > > > > > > > > > 写道：
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> Congrats Martijn!
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> On Thu, Mar 3, 2022 at 10:50 AM Robert Metzger <
> > > > > > > > rmetz...@apache.org
> > > > > > > > > > >
> > > > > > > > > > > > wrote:
> > > > > > > > > > > > >>
> > > > > > > > > > > > >>> Hi everyone,
> > > > > > > > > > > > >>>
> > > > > > > > > > > > >>> On behalf of the PMC, I'm very happy to announce
> > > > Martijn
> > > > > > > > Visser as
> > > > > > > > > > a
> > > > > > > > > > > > new
> > > > > > > > > > > > >>> Flink committer.
> > > > > > > > > > > > >>>
> > > > > > > > > > > > >>> Martijn is a very active Flink community member,
> > > > driving
> > > > > a
> > > > > > lot
> > > > > > > > of
> > > > > > > > > > > > efforts
> > > > > > > > > > > > >>> on the dev@flink mailing list. He also pushes
> > > projects
> > > > > > such as
> > > > > > > > > > > > replacing
> > > > > > > > > > > > >>> Google Analytics with Matomo, so that we can
> generate
> > > > our
> > > > > > web
> > > > > > > > > > > analytics
> > > > > > > > > > > > >>> within the Apache Software Foundation.
> > > > > > > > > > > > >>>
> > > > > > > > > > > > >>> Please join me in congratulating Martijn for
> > > becoming a
> > > > > > Flink
> > > > > > > > > > > > committer!
> > > > > > > > > > > > >>>
> > > > > > > > > > > > >>> Cheers,
> > > > > > > > > > > > >>> Robert
> > > > > > > > > > > > >>>
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > best,
> > > > > > > > > > > Zhipeng
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> > --
> > Best regards,
> > Sergey
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
e Beam project to Flink.
> >
> >
> > Please join me in congratulating David for becoming a Flink committer!
> >
> > Cheers,
> > Robert
> >
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
com/apache/flink-web/pull/510
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
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
> 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
plication 写成了 yarn-appliation的话
> 就会报错
> [image: image.png]
> 这里我看了代码是CliFrontend 封装的 213行的配置集合 effectiveConfiguration
> 有问题，导致DefaultClusterClientServiceLoader.java:83 判断进入报错
> [image: image.png]
> 我觉得这里的报错信息的描述有问题 会造成误导，是使用者误认为是自己的HADOOP_CLASSPATH 环境有问题，希望可以得到大家的回复
>
--
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
sus of active committers.
>
> Best regards,
>
> Martijn Visser
> https://twitter.com/MartijnVisser82
>
> [1] https://lists.apache.org/thread/1vs3wmk66vsq6l4npjsfzltft4tz5tkq
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
> > D.
> > >
> > > On Mon, Jan 24, 2022 at 3:24 PM Till Rohrmann
> > > wrote:
> > >
> > > > +1 for the 1.13.6 release and thanks for volunteering Konstantin.
> > > >
> > > > Cheers,
> > > > Till
> >
bled by some config) distribute these, or are there some technical
> > > limitations?
> > >
> > > For us it would be crucial to achieve the functionality we have at the
> > > moment over YARN. We started to track
> > > https://issues.apache.org/ji
[1] https://lists.apache.org/thread/b8g76cqgtr2c515rd1bs41vy285f317n
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
> > > > > On Fri 28. 1. 2022 at 17:53, Till Rohrmann >
> > > > wrote:
> > > > > >
> > > > > > > +1 (binding)
> > > > > > >
> > > > > > > Cheers,
> > > > > > > Till
> >
com/apache/flink-web/pull/505
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
Non-Binding +1
Chenya Zhang
David Moravek
Gabor Somogyi
Cheers,
Konstantin
[1] https://lists.apache.org/thread/v6oz92dfp95qcox45l0f8393089oyjv4
[2] https://issues.apache.org/jira/browse/FLINK-25999
[3] https://issues.apache.org/jira/browse/FLINK-26000
--
Konstantin Knauf
https://twitter.com
ntin.
> >
> > +1 for deprecating per-job mode in Flink 1.15, and reevaluating when to
> > drop it after Flink 1.16.
> >
> > Thank you~
> >
> > Xintong Song
> >
> >
> >
> > On Tue, Feb 1, 2022 at 5:27 PM Konstantin Knauf
> wrote:
>
nd whether we couldn't invest this time elsewhere.
>
> Let me know what you think.
>
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
tijn
> > > > > >
> > > > > > On Wed, 9 Feb 2022 at 10:55, Martijn Visser <
> mart...@ververica.com
> > >
> > > > > wrote:
> > > > > >
> > > > > >> Hi everyone,
> > > > > >>
> >
://issues.apache.org/jira/browse/FLINK-26018 to be resolved.
I can volunteer as release manager.
Cheers,
Konstantin
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
of the cluster resources prior to taking down the previous
> job during upgrade when the goal is optimization for availability.
>
> Thanks,
> Thomas
>
> [1] https://github.com/lyft/flinkk8soperator
>
> On Thu, Jan 13, 2022 at 12:32 AM Konstantin Knauf
> wrote:
> >
ormat checkpoints, and could be done
> > > completely independently of providing the native format support in
> > > savepoints.
> > >
> > > Best,
> > > Piotrek
> > >
> > > [1]
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-203%3A+Incremental+savepoints
> > >
> >
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
ttps://twitter.com/MartijnVisser82
>
> [1] https://flink.apache.org/news/2021/12/16/log4j-patch-releases.html
> [2] https://flink.apache.org/news/2021/10/19/release-1.13.3.html
> [3] JQL filter: project = FLINK AND resolution = Fixed AND fixVersion =
> 1.13.6 AND labels != test-stability
ot
> > (incremental checkpoint)?
> > b) State Processor API - both pre-existing and what do we want to provide
> > in the future
> > c) Schema Evolution - both pre-existing and what do we want to provide in
> > the future
> >
> > Best,
> > Piotrek
, 2021 at 2:22 PM 柳尘 wrote:
> Thanks to Konstantin for raising this question, and to Marton and Gabor
> To strengthen!
>
> If i can help
> In order to better participate in the work, please let me know.
>
> the best,
> cheng xingyuan
>
>
> > 2021年7月29日 下午4:1
On Wed, Jan 26, 2022 at 10:17 AM Konstantin Knauf
wrote:
> Hi everyone,
>
> We are seeing an increasing number of test instabilities related to YARN
> [1]. Does someone in this group have the time to pick these up? The Flink
> Confluence contains a guide on how to triage test inst
+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
>
; >
> > 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
; 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
.
> >
> > 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
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
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
201 - 300 of 470 matches
Mail list logo
