pendency. 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,
> >
and dynamic rule changing mechanism.
>
> Best,
> Nicholas Jiang
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
e 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
le contains the
> PatternProcessFunction, but the Pattern or DynamicPattern doesn't contain
> the function.
>
> Best
> Nicholas Jiang
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
ng a single pattern inside 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
> 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
t around 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
ck whether the latest rules on 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
&g
gt; Flink 1.14
> > >> > > >> >> > >>>> > was released on the 29th of September [1] and so
> far
> > >> 107
> > >> > > >> issues
> > >> > > >> >> have been
> > >> > > >> >> > >>>> > resolved, including multiple blockers and critical
> > &g
; >> fixVersion
> > > > > >> >> 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
o not want it to 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
lob/3f96c249cbc17ce062491bfbb39d484e241ab168/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
>
; > supported 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,
> > > >
enient.
>
> 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 a
cardinality and 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
rom the latest checkpoint, it may be fairly simple to implement.
>>>> What I'm struggling with are the more complex upgrade scenarios such as
>>>> dual, blue / green deployment.
>>>> >
>>>> >
>>>> > To sum this up, I'd re
gt; TM heartbeat lost and 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 ment
ode midterm?
Cheers and thank you,
Konstantin
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
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 ecosyste
equesting a VM from Apache Infra
> [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
native format snapshot
> > (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
ocation 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:
&g
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
gt; https://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-stab
, 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
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] https://lists.apache.org/thread/b8g76cqgtr2c515rd1bs41vy285f317n
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
; enabled 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.o
; > D.
> > > > > >
> > > > > > On Fri 28. 1. 2022 at 17:53, Till Rohrmann >
> > > > wrote:
> > > > > >
> > > > > > > +1 (binding)
> > > > > > >
> > > > > > > Cheers,
>
gt; consensus 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
> > Best,
> > > 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,
> > > >
s://github.com/apache/flink-web/pull/505
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
rmann
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://twitte
onstantin.
> >
> > +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
n makes sense to do
> so, and whether we couldn't invest this time elsewhere.
>
> Let me know what you think.
>
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
>
> > > > > >> Hi everyone,
> > > > > >>
> > > > > >> Please keep in mind that Azure Pipelines currently is dealing
> with
> > > an
> > > > > >> incident [1] which causes all CI pipeline runs on Azure to fail.
> > > When
> > > > > the
> > > > > >> incident has been resolved, it will be required to retrigger
> your
> > > > > pipeline
> > > > > >> to see if the pipeline then passes.
> > > > > >>
> > > > > >> Best regards,
> > > > > >>
> > > > > >> Martijn Visser
> > > > > >> https://twitter.com/MartijnVisser82
> > > > > >>
> > > > > >> [1] https://status.dev.azure.com/_event/287959626
> > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
://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
gt; > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Hi team,
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Thank you for the great feedback,
> > Thomas
> > > has
> &g
e not jar applications 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
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
Jira:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=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
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
indeed
> 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 <
> kn
o execute this plan for the Elasticsearch
> >>> connector as follows:
> >>>
> >>> 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
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
>
s://github.com/apache/flink-web/pull/510
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
-
>
> 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
Apache 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
che.org/confluence/display/FLINK/FLIP-158%3A+Generalized+incremental+checkpoints
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
org/thread.html/rd34fb695d371c2bf0cbd1696ce190bac35dd78f29edd8c60d0c7ee71%40%3Cdev.flink.apache.org%3E
[2]
https://cwiki.apache.org/confluence/display/FLINK/FLINK+Jira+field+definitions
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
> Thanks for starting this discussion Konstantin. I like your proposal and
> > also the idea of automating the tedious parts of it via a bot.
> >
> > Cheers,
> > Till
> >
> > On Fri, Feb 26, 2021 at 4:17 PM Konstantin Knauf
> > wrote:
> >
> > >
ide, this would lessen the exposure to the various Flink areas
> for lists maintainers.
>
> What do you think?
>
> Regards,
> Roman
>
--
Konstantin Knauf | Head of Product
+49 160 91394525
Follow us @VervericaData Ververica <https://www.ververica.com/>
--
Join Fli
res therefore it
> will automatically priortise the tasks according to failure frequencies.
>
> Best,
>
> Dawid
>
> On 01/03/2021 09:38, Konstantin Knauf wrote:
> > Hi Xintong,
> >
> > yes, such labels would make a lot of sense. I added a sentence to the
>
work on it in the near future?
> Another approach would be some wiki space.
>
> As for the trivial priority, I would remove it and (use labels where
> appropriate) as you suggested.
>
> Regards,
> Roman
>
>
> On Mon, Mar 1, 2021 at 11:53 AM Konstantin Knauf >
> wr
ell it can be a good step towards managing
> > technical debt in some other way, like wiki.
> >
> > Thanks!
> >
> > Regards,
> > Roman
> >
> >
> > On Tue, Mar 2, 2021 at 9:32 AM Dawid Wysakowicz
> > wrote:
> >
> > > I'd be
two `auto-deprioritized-blocker` in rule 1 details
> should
> > be `auto-deprioritized-critical/major`.
> >
> > Thank you~
> >
> > Xintong Song
> >
> >
> >
> > On Fri, Mar 5, 2021 at 7:33 PM Konstantin Knauf
> wrote:
> >
> >> H
Hi everyone,
The discussion has stalled a bit on this thread. I would proceed to a vote
on the currently documented proposal tomorrow if there are no further
concerns or opinions.
Best,
Konstantin
On Fri, Mar 12, 2021 at 5:24 PM Konstantin Knauf wrote:
> Hi Leonard,
>
> Thank you
/re7affbb1357ce4986a7770b0052c39c9a26ebd7cd0df3f15ed320781%40%3Cdev.flink.apache.org%3E
[2]
https://docs.google.com/document/d/19VmykDSn4BHgsCNTXtN89R7xea8e3cUIl-uivW8L6W8/edit#
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
e ideas we collected in [1]
> sound
> > good. I'm looking forward to trying it out.
> > +1 from my side.
> >
> > Best,
> > Matthias
> >
> > [1]
> >
> https://lists.apache.org/thread.html/re7affbb1357ce4986a7770b0052c39c9a26ebd7cd0df3f15ed320
>> management component. We are pretty heavy users of Mesos for scheduling
> >> workloads on our edge datacenters and we do want to continue to be able
> to
> >> run some of our Flink topologies (to compute machine learning short term
> >> features) on those DCs.
; with the release, and would like to kick off the release candidates early
> next week.
>
> Please let us know if you have any concerns.
>
> Thanks,
> Gordon
>
> [1] https://github.com/apache/flink-statefun-playground
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
n resolved with urgency, I also cannot imagine a blocker going
> completely stale, so we probably talk about something that never happens in
> reality. For other tickets, it makes sense.
>
> On Tue, Mar 23, 2021 at 8:09 AM Konstantin Knauf
> wrote:
>
> > Hi everyone,
> >
n stale for
> months.
>
> On 3/26/2021 8:46 AM, Konstantin Knauf wrote:
> > Hi Arvid,
> >
> > I agree that this should never happen for blockers. My thinking was that
> if
> > an unassigned blocker is deprioritized after 1 day it also forces us to
> > find som
he Release
> Manager that this ticket must be completed. How would that work in your
> proposal?
>
> On 3/26/2021 9:18 AM, Konstantin Knauf wrote:
>
> Hi Chesnay,
>
> a blocker is currently defined in the Flink Confluence as a "needs to be
> resolved before a release (matche
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
ours. I’m targeting this vote
> > to
> > > last until April. 2nd, 12pm CET.
> > > It is adopted by majority approval, with at least 3 PMC affirmative
> > votes.
> > >
> > > Thanks,
> > > Gordon
> > >
> > > [1]
> >
the same release cycle could be developed in sync with each
> other.
>
> Let me know what you think.
>
> Regards,
>
> Chesnay
>
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
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
rised
when you see more and more Flink Jira Bot activity in our Jira.
Please let me know if you have any questions.
Cheers,
Konstantin
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
next two weeks. So, don't be surprised
when you see more and more Flink Jira Bot activity in our Jira.
Please let me know if you have any questions.
Cheers,
Konstantin
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
[1] https://issues.apache.org/jira/browse/
; {stale.minor.warning_days} with a comment that encourages > users to
> watch, comment and simply reopen with a higher priority if the problem
> insists.
>
> Why is the ticket for said rule still open?
> https://issues.apache.org/jira/browse/FLINK-22032
>
> On 4/14/2021 12:06
d", "Deployment
/ Kubernetes", "Deployment / Mesos", "Deployment / YARN", flink-docker,
"Release System", "Runtime / Coordination", "Runtime / Metrics", "Runtime /
Queryable State", "Runtime / REST", Travis) AND resolution = Unresolved AND
labels in (stale-assigned) AND labels in (pull-request-available)
Cheers,
Konstantin
[1] https://github.com/apache/flink-jira-bot/blob/master/config.yaml
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
dev@flink.apache.org ;
> matth...@ververica.com
> > <
> > > matth...@ververica.com>
> > > Subject: Re: Re: Re: [ANNOUNCE] New Apache Flink Committer - Rui Li
> > >
> > > Congratulations Rui!
> > >
> > > Best,
> > > Xuanna
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
x27;m proposing to start releasing 1.12.4 on next Monday.
> >
> > I'd volunteer as a release manager again.
> >
> > Best,
> >
> > Arvid
> >
> > [1] https://issues.apache.org/jira/browse/FLINK-22555
> >
>
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
,
Konstantin
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
notification per ticket which
includes the label/comment and status update, instead of separate ones.
Cheers,
Konstantin
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
uot;roll over" many tickets to the next release if
they have not made into the previous release although there is no concrete
plan to fix them or they have even become obsolete by then. Excluding those
from the bot would be counterproductive.
What do you think?
Cheers,
Konstantin
On Fri, Apr
t; Otherwise +1.
> > > >
> > > > Regards,
> > > > Timo
> > > >
> > > >
> > > > On 17.05.21 10:11, Robert Metzger wrote:
> > > > > Thanks a lot for starting the discussion about the release.
> > > >
;
> > I like this idea. +1 for your proposal Konstantin.
> >
> > Cheers,
> > Till
> >
> > On Wed, May 19, 2021 at 1:30 PM Konstantin Knauf <
> konstan...@ververica.com
> > >
> > wrote:
> >
> > > Hi everyone,
> > >
> &
lunteers until Monday I
> can also do it myself. However I'd appreciate if someone else could take
> care of tracking the progress of the issues we want to include in the
> release.
> >
> > Best,
> > Dawid
> >
> > On 20/05/2021 09:59, Konstantin
bot for subtasks or extend the period to 30 days?
>
> The core problem in the past was that we had issues laying around
> untouched for years. Luckily, this is solved with the bot now. But going
> from years to 7 days spams the mail box quite a bit.
>
> Regards,
> Tim
2. What orders to sync data of all matched table? Sync data from all
> > matched tables one by one or at the same time?
> >
> >
> >
> > > AS select_statement: copy source table data into target
> >
> >
> >
> > User could explicitly specify the data type for each column in the CTAS,
> > what happened when run the following example. The demo is from MySQL
> > document,
> https://dev.mysql.com/doc/refman/5.6/en/create-table-select.html
> > , the result is a bit unexpected, I wonder
> >
> > What the behavior would be in Flink.
> >
> >
> > [image: image.png]
> >
> > Best,
> > JING ZHANG
> >
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
> > Qingsheng Ren
> > Email: renqs...@gmail.com
> > On Jun 16, 2021, 5:21 PM +0800, Dawid Wysakowicz ,
> wrote:
> > > Hi all!
> > >
> > > I'm very happy to announce that Arvid Heise has joined the Flink PMC!
> > >
> > > Con
gt;
> > I'm very happy to announce that Xintong Song has joined the Flink PMC!
> >
> > Congratulations and welcome Xintong!
> >
> > Best,
> > Dawid
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
> eventually replace DataSet. We would collect ideas over the next couple
> of
> > weeks without any visible progress on the implementation.
> >
> > On Fri, May 21, 2021 at 2:06 PM Konstantin Knauf
> > wrote:
> >
> > > Hi Timo,
> > >
> > &g
t;>>>>> Unfortunately we
> >>>>>>>>>>>> can't name them in this public list, however
> >>>>>>>>>>>> the customers who specifically asked for this were mainly in
> >>>>>>>>>>>> the banking
> >>>>>>>>>>>> and telco sector.
> >>>>>>>>>>>>
> >>>>>>>>>>>> BR,
> >>>>>>>>>>>> G
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Thu, Jun 3, 2021 at 9:20 AM Till Rohrmann <
> >>>>>>>>>>>> trohrm...@apache.org> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>> > Thanks for updating the document Márton. Why is it that
> banks
> >>>>>>>>>>>> will
> >>>>>>>>>>>> > consider it more secure if Flink comes with Kerberos
> >>>>>>>>>>>> authentication
> >>>>>>>>>>>> > (assuming a properly secured setup)? I mean if an attacker
> >>>>>>>>>>>> can get access
> >>>>>>>>>>>> > to one of the machines, then it should also be possible to
> >>>>>>>>>>>> obtain the right
> >>>>>>>>>>>> > Kerberos token.
> >>>>>>>>>>>> >
> >>>>>>>>>>>> > I am not an authentication expert and that's why I wanted to
> >>>>>>>>>>>> ask what are
> >>>>>>>>>>>> > other authentication protocols other than Kerberos? Why did
> >>>>>>>>>>>> we select
> >>>>>>>>>>>> > Kerberos and not any other authentication protocol? Maybe
> you
> >>>>>>>>>>>> can list the
> >>>>>>>>>>>> > pros and cons for the different protocols. Is Kerberos also
> >>>>>>>>>>>> the standard
> >>>>>>>>>>>> > authentication protocol for Kubernetes deployments? If not,
> >>>>>>>>>>>> what would be
> >>>>>>>>>>>> > the answer when deploying on K8s?
> >>>>>>>>>>>> >
> >>>>>>>>>>>> > Cheers,
> >>>>>>>>>>>> > Till
> >>>>>>>>>>>> >
> >>>>>>>>>>>> > On Wed, Jun 2, 2021 at 12:07 PM Gabor Somogyi <
> >>>>>>>>>>>> gabor.g.somo...@gmail.com>
> >>>>>>>>>>>> > wrote:
> >>>>>>>>>>>> >
> >>>>>>>>>>>> >> Hi team,
> >>>>>>>>>>>> >>
> >>>>>>>>>>>> >> Happy to be here and hope I can provide quality additions
> in
> >>>>>>>>>>>> the future.
> >>>>>>>>>>>> >>
> >>>>>>>>>>>> >> Thank you all for helpful the suggestions!
> >>>>>>>>>>>> >> Considering them the FLIP has been modified and the work
> >>>>>>>>>>>> continues on the
> >>>>>>>>>>>> >> already existing Jira.
> >>>>>>>>>>>> >>
> >>>>>>>>>>>> >> BR,
> >>>>>>>>>>>> >> G
> >>>>>>>>>>>> >>
> >>>>>>>>>>>> >>
> >>>>>>>>>>>> >> On Wed, Jun 2, 2021 at 11:23 AM Márton Balassi <
> >>>>>>>>>>>> balassi.mar...@gmail.com>
> >>>>>>>>>>>> >> wrote:
> >>>>>>>>>>>> >>
> >>>>>>>>>>>> >>> Thanks, Chesney - I totally missed that. Answered on the
> >>>>>>>>>>>> ticket too, let
> >>>>>>>>>>>> >>> us continue there then.
> >>>>>>>>>>>> >>>
> >>>>>>>>>>>> >>> Till, I agree that we should keep this codepath as slim as
> >>>>>>>>>>>> possible. It
> >>>>>>>>>>>> >>> is an important design decision that we aim to keep the
> >>>>>>>>>>>> list of
> >>>>>>>>>>>> >>> authentication protocols to a minimum. We believe that
> this
> >>>>>>>>>>>> should not be a
> >>>>>>>>>>>> >>> primary concern of Flink and a trusted proxy service (for
> >>>>>>>>>>>> example Apache
> >>>>>>>>>>>> >>> Knox) should be used to enable a multitude of enduser
> >>>>>>>>>>>> authentication
> >>>>>>>>>>>> >>> mechanisms. The bare minimum of authentication mechanisms
> >>>>>>>>>>>> to support
> >>>>>>>>>>>> >>> consequently consist of a single strong authentication
> >>>>>>>>>>>> protocol for which
> >>>>>>>>>>>> >>> Kerberos is the enterprise solution and HTTP Basic primary
> >>>>>>>>>>>> for development
> >>>>>>>>>>>> >>> and light-weight scenarios.
> >>>>>>>>>>>> >>>
> >>>>>>>>>>>> >>> Added the above wording to G's doc.
> >>>>>>>>>>>> >>>
> >>>>>>>>>>>> >>>
> >>>>>>>>>>>>
> https://docs.google.com/document/d/1NMPeJ9H0G49TGy3AzTVVJVKmYC0okwOtqLTSPnGqzHw/edit
> >>>>>>>>>>>> >>>
> >>>>>>>>>>>> >>>
> >>>>>>>>>>>> >>>
> >>>>>>>>>>>> >>> On Tue, Jun 1, 2021 at 11:47 AM Chesnay Schepler <
> >>>>>>>>>>>> ches...@apache.org>
> >>>>>>>>>>>> >>> wrote:
> >>>>>>>>>>>> >>>
> >>>>>>>>>>>> >>>> There's a related effort:
> >>>>>>>>>>>> >>>> https://issues.apache.org/jira/browse/FLINK-21108
> >>>>>>>>>>>> >>>>
> >>>>>>>>>>>> >>>> On 6/1/2021 10:14 AM, Till Rohrmann wrote:
> >>>>>>>>>>>> >>>> > Hi Gabor, welcome to the Flink community!
> >>>>>>>>>>>> >>>> >
> >>>>>>>>>>>> >>>> > Thanks for sharing this proposal with the community
> >>>>>>>>>>>> Márton. In
> >>>>>>>>>>>> >>>> general, I
> >>>>>>>>>>>> >>>> > agree that authentication is missing and that this is
> >>>>>>>>>>>> required for
> >>>>>>>>>>>> >>>> using
> >>>>>>>>>>>> >>>> > Flink within an enterprise. The thing I am wondering is
> >>>>>>>>>>>> whether this
> >>>>>>>>>>>> >>>> > feature strictly needs to be implemented inside of
> Flink
> >>>>>>>>>>>> or whether a
> >>>>>>>>>>>> >>>> proxy
> >>>>>>>>>>>> >>>> > setup could do the job? Have you considered this
> option?
> >>>>>>>>>>>> If yes, then
> >>>>>>>>>>>> >>>> it
> >>>>>>>>>>>> >>>> > would be good to list it under the point of rejected
> >>>>>>>>>>>> alternatives.
> >>>>>>>>>>>> >>>> >
> >>>>>>>>>>>> >>>> > I do see the benefit of implementing this feature
> inside
> >>>>>>>>>>>> of Flink if
> >>>>>>>>>>>> >>>> many
> >>>>>>>>>>>> >>>> > users need it. If not, then it might be easier for the
> >>>>>>>>>>>> project to not
> >>>>>>>>>>>> >>>> > increase the surface area since it makes the overall
> >>>>>>>>>>>> maintenance
> >>>>>>>>>>>> >>>> harder.
> >>>>>>>>>>>> >>>> >
> >>>>>>>>>>>> >>>> > Cheers,
> >>>>>>>>>>>> >>>> > Till
> >>>>>>>>>>>> >>>> >
> >>>>>>>>>>>> >>>> > On Mon, May 31, 2021 at 4:57 PM Márton Balassi <
> >>>>>>>>>>>> mbala...@apache.org>
> >>>>>>>>>>>> >>>> wrote:
> >>>>>>>>>>>> >>>> >
> >>>>>>>>>>>> >>>> >> Hi team,
> >>>>>>>>>>>> >>>> >>
> >>>>>>>>>>>> >>>> >> Firstly I would like to introduce Gabor or G [1] for
> >>>>>>>>>>>> short to the
> >>>>>>>>>>>> >>>> >> community, he is a Spark committer who has recently
> >>>>>>>>>>>> transitioned to
> >>>>>>>>>>>> >>>> the
> >>>>>>>>>>>> >>>> >> Flink Engineering team at Cloudera and is looking
> >>>>>>>>>>>> forward to
> >>>>>>>>>>>> >>>> contributing
> >>>>>>>>>>>> >>>> >> to Apache Flink. Previously G primarily focused on
> >>>>>>>>>>>> Spark Streaming
> >>>>>>>>>>>> >>>> and
> >>>>>>>>>>>> >>>> >> security.
> >>>>>>>>>>>> >>>> >>
> >>>>>>>>>>>> >>>> >> Based on requests from our customers G has implemented
> >>>>>>>>>>>> Kerberos and
> >>>>>>>>>>>> >>>> HTTP
> >>>>>>>>>>>> >>>> >> Basic Authentication for the Flink Dashboard and
> >>>>>>>>>>>> HistoryServer.
> >>>>>>>>>>>> >>>> Previously
> >>>>>>>>>>>> >>>> >> lacked an authentication story.
> >>>>>>>>>>>> >>>> >>
> >>>>>>>>>>>> >>>> >> We are looking to contribute this functionality back
> to
> >>>>>>>>>>>> the
> >>>>>>>>>>>> >>>> community, we
> >>>>>>>>>>>> >>>> >> believe that given Flink's maturity there should be a
> >>>>>>>>>>>> common code
> >>>>>>>>>>>> >>>> solution
> >>>>>>>>>>>> >>>> >> for this general pattern.
> >>>>>>>>>>>> >>>> >>
> >>>>>>>>>>>> >>>> >> We are looking forward to your feedback on G's design.
> >>>>>>>>>>>> [2]
> >>>>>>>>>>>> >>>> >>
> >>>>>>>>>>>> >>>> >> [1] http://gaborsomogyi.com/
> >>>>>>>>>>>> >>>> >> [2]
> >>>>>>>>>>>> >>>> >>
> >>>>>>>>>>>> >>>> >>
> >>>>>>>>>>>> >>>>
> >>>>>>>>>>>>
> https://docs.google.com/document/d/1NMPeJ9H0G49TGy3AzTVVJVKmYC0okwOtqLTSPnGqzHw/edit
> >>>>>>>>>>>> >>>> >>
> >>>>>>>>>>>> >>>>
> >>>>>>>>>>>> >>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
most experience with Spark which I think is quite simple and stable. Users
> can be viewers/admins
> and jobs started by others can't be modified. If you can share an example
> over-complication we can discuss on facts.
>
> Thank you in advance!
>
> BR,
> G
>
>
>
ou'd like to have included
> in these versions.
>
> Would someone be willing to volunteer to help with the releases as a
> release manager? I guess there is a couple of spots to fill in here ;)
>
> Best,
>
> Dawid
>
> [1] https://issues.apache.org/jira/browse/
ment applications? This currently only runs on
> > > Kubernetes
> > > >> on Linux, so that's a major limitation, but solves many of the
> request
> > > >> forging concerns at all levels.
> > > >>
> > > >> Thanks,
&g
to consider when developing the next major version.
> > > Admittedly, we have never seen the benefits of collecting the breaking
> > > changes because we haven't started Flink 2.x yet. Also, it is not clear
> > how
> > > relevant these tickets are right now
er example for category 4 would be the ticket where we collect
> > > breaking API changes for Flink 2.0 [1]. The idea behind this ticket is
> to
> > > collect things to consider when developing the next major version.
> > > Admittedly, we have never seen the benefits of co
ly blocked by the reviewer, not the assignee, and having the
> > assignees now additionally having to update JIRA periodically is a bit
> > like rubbing salt into the wound.
> >
> > On 6/23/2021 7:52 AM, Konstantin Knauf wrote:
> > > Hi everyone,
> > >
> > >
t; these
> > tend to be watched anyways.
> >
> > On Wed, Jun 23, 2021 at 2:39 PM JING ZHANG wrote:
> >
> > > Hi Konstantin, Chesnay,
> > >
> > > > I would like it to not unassign people if a PR is open. These are
> > > > usually blocked b
gt; [1]
> https://cwiki.apache.org/confluence/display/FLINK/Flink+Jira+Process
> > >
> > > Cheers,
> > > Till
> > >
> > > On Wed, Jun 30, 2021 at 10:59 AM Piotr Nowojski
> > > wrote:
> > >
> > > > > * Introduce "N
wrote:
> >>>>
> >>>>> Hi everyone, I would like to start a vote on FLIP-181 [1] which was
> >>>>> discussed in this thread [2]. The vote will be open for at least 72
> >>> hours
> >>>>> until July 9th unless there is an objection or not enough votes.
> >>>>>
> >>>>> [1] https://cwiki.apache.org/confluence/x/CAUBCw
> >>>>> [2]
> >>>>>
> >>>>>
> >>
> https://lists.apache.org/thread.html/r53b6b8931b6248a849855dad27b1a431e55cdd48ca055910e8f015a8%40%3Cdev.flink.apache.org%3E
>
>
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk
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
201 - 300 of 478 matches
Mail list logo
