Re: [VOTE] FLIP-446: Kubernetes Operator State Snapshot CRD

+1 (binding) On Wed, Apr 24, 2024 at 5:14 AM Yuepeng Pan wrote: > +1(non-binding) > > > Best, > Yuepeng Pan > > At 2024-04-24 16:05:07, "Rui Fan" <1996fan...@gmail.com> wrote: > >+1(binding) > > > >Best, > >Rui > > > >On Wed, Apr 24, 2024 at 4:03 PM Mate Czagany wrote: > > > >> Hi everyone, >

Re: [DISCUSS] FLIP-446: Kubernetes Operator State Snapshot CRD

Thanks for the proposal. How do you see potential effects on API server performance wrt. number of objects vs mutations? Is the proposal more or less neutral in that regard? Thanks for the thorough feedback Robert. Couple more questions below. --> On Fri, Apr 19, 2024 at 5:07 AM Robert

Re: Re: [VOTE] FLIP-417: Expose JobManagerOperatorMetrics via REST API

+1 (binding) On Mon, Jan 29, 2024 at 5:45 AM Maximilian Michels wrote: > +1 (binding) > > On Fri, Jan 26, 2024 at 6:03 AM Rui Fan <1996fan...@gmail.com> wrote: > > > > +1(binding) > > > > Best, > > Rui > > > > On Fri, Jan 26, 2024 at 11:55 AM Xuyang wrote: > > > > > +1 (non-binding) > > > > >

Re: [VOTE] Apache Flink Kubernetes Operator Release 1.6.1, release candidate #1

+1 (binding) - Verified checksums, signatures, source release content - Run unit tests Side note: mvn clean verifyfails with Java 17 compiler. While the build target version may be 11, preferably a higher JDK version can be used to build the source. Caused by:

Re: [Discuss] CRD for flink sql gateway in the flink k8s operator

It is already possible to bring up a SQL Gateway as a sidecar utilizing the pod templates - I tend to also see this more of a documentation/example issue rather than something that calls for a separate CRD or other dedicated operator support. Thanks, Thomas On Tue, Sep 19, 2023 at 3:41 PM

Re: [DISSCUSS] Kubernetes Operator Flink Version Support Policy

+1, thanks for the proposal On Tue, Sep 5, 2023 at 8:13 AM Gyula Fóra wrote: > Hi All! > > @Maximilian Michels has raised the question of Flink > version support in the operator before the last release. I would like to > open this discussion publicly so we can finalize this before the next >

Re: [VOTE] FLIP-246: Dynamic Kafka Source (originally Multi Cluster Kafka Source)

+1 (binding) On Mon, Jun 19, 2023 at 8:09 AM Ryan van Huuksloot wrote: > +1 (non-binding) > > +1 for DynamicKafkaSource > > Ryan van Huuksloot > Sr. Production Engineer | Streaming Platform > [image: Shopify] > > > > On Mon,

Re: [DISCUSS] FLIP-246: Multi Cluster Kafka Source

Hi Mason, Thanks for the iterations on the FLIP, I think this is in a very good shape now. Small correction for the MultiClusterKafkaSourceEnumerator section: "This reader is responsible for discovering and assigning splits from 1+ cluster" Regarding the user facing name of the connector: I

Re: [NOTICE] Flink master branch now uses Maven 3.8.6

Thanks a lot Chesnay for getting this squared away! It was quite painful to have to keep an outdated maven around specifically for building Flink but many had probably given up on this by now ;-) On Sun, May 14, 2023 at 9:33 PM yuxia wrote: > Thanks Chesnay for the efforts. Happy to see we can

Re: [DISCUSS] SqlClient gateway mode: support for URLs

Hi Alex, Thanks for the investigation and for the ideas on how to improve the SQL gateway REST client. I think the solution could come in 2 parts. Near term the existing client can be patched to support URL mapping and HTTPS based on a standard URL. If I understand your proposal correctly, that

Re: Kubernetes Operator 1.5.0 release planning

+1 and thanks for volunteering! On Mon, May 1, 2023 at 5:04 PM Peter Huang wrote: > +1, thanks. > > On Mon, May 1, 2023 at 7:58 AM Márton Balassi > wrote: > > > +1, thanks. > > > > On Mon, May 1, 2023 at 4:23 PM Őrhidi Mátyás > > wrote: > > > > > +1 SGTM. > > > > > > Cheers, > > > Matyas > >

Re: [Discussion] - Release major Flink version to support JDK 17 (LTS)

Is the intention to bump the Flink major version and only support Java 17+? If so, can Scala not be upgraded at the same time? Thanks, Thomas On Thu, Apr 27, 2023 at 4:53 PM Martijn Visser wrote: > Scala 2.12.7 doesn't compile on Java 17, see >

Re: Flink k8s native support - pod deployments and upgrades

Hi, The Flink k8s native integration does not handle upgrades. That's what flink-kubernates-operator was built for. Please check out: https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/ Thanks, Thomas On Fri, Mar 3, 2023 at 2:02 AM ramkrishna vasudevan wrote: > Hi All, >

Re: [VOTE] Flink minor version support policy for old releases

+1 (binding) Thanks, Thomas On Tue, Feb 28, 2023 at 6:53 AM Sergey Nuyanzin wrote: > +1 (non-binding) > > Thanks for driving this Danny. > > On Tue, Feb 28, 2023 at 9:41 AM Samrat Deb wrote: > > > +1 (non binding) > > > > Thanks for driving it > > > > Bests, > > Samrat > > > > On Tue, 28 Feb

Re: [DISCUSS] Flink minor version support policy for old releases

+1 I would not be surprised to also see future requests to extend the window for older releases in general. Rollout of upgrades may not keep pace with our current release policy for a variety of reasons. Thanks, Thomas On Fri, Feb 17, 2023 at 12:38 PM Jing Ge wrote: > +1 > > Thanks Danny for

Re: [VOTE] Apache Flink Kubernetes Operator Release 1.3.1, release candidate #1

Hi, Sorry for the late reply to this thread, but in the meantime we learned that the assumption based on which the above mentioned change to upgradeMode was approved does not hold true. The assumption was that the generation id in spec metadata and reconciled spec can be used to determine if

[jira] [Created] (FLINK-30858) Kubernetes operator does not update reconciled generation

Thomas Weise created FLINK-30858: Summary: Kubernetes operator does not update reconciled generation Key: FLINK-30858 URL: https://issues.apache.org/jira/browse/FLINK-30858 Project: Flink

Re: [VOTE] Release flink-connector-opensearch, release candidate #1

+1 (binding) * Checked hash and signature * Build from source and run tests * Checked licenses On Mon, Dec 19, 2022 at 1:50 PM Maximilian Michels wrote: > +1 (binding) > > Release looks good. > > 1. Downloaded the source archive release staged at > >

Re: Edit Wiki for Release Verification Steps

Hi Jim, You should have access now (user: jbusche) Thanks On Thu, Dec 8, 2022 at 7:30 PM Jim Busche wrote: > I'd like to be able to edit the wiki page: > https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+Kubernetes+Operator+Release > > It says it's unrestricted, but maybe I

Re: [VOTE] FLIP-271: Autoscaling

+1 (binding) On Sat, Nov 26, 2022 at 8:11 AM Zheng Yu Chen wrote: > +1(no-binding) > > Maximilian Michels 于 2022年11月24日周四 上午12:25写道： > > > Hi everyone, > > > > I'd like to start a vote for FLIP-271 [1] which we previously discussed > on > > the dev mailing list [2]. > > > > I'm planning to

Re: [ANNOUNCE] New Apache Flink Committer - Matyas Orhidi

Congrats Matyas! On Mon, Nov 21, 2022 at 6:28 PM Őrhidi Mátyás wrote: > Thanks folks, > > So proud and honored to be part of the pack! > > Cheers, > Matyas > > On Mon, Nov 21, 2022 at 12:32 PM Danny Cranmer > wrote: > > > Congrats Matyas! > > > > On Mon, 21 Nov 2022, 17:51 ramkrishna

Re: Env Vars in the Flink Web UI

+1 for d) don't print any env vars in the web UI (at least by default) There could be an option to allow-list printing of env vars but it should be off by default. Generally I think that those that should be able to see env vars probably can get there by other means, like kubetcl exec Thanks,

[jira] [Created] (FLINK-30004) Cannot resume deployment after suspend with savepoint due to leftover confgmaps

Thomas Weise created FLINK-30004: Summary: Cannot resume deployment after suspend with savepoint due to leftover confgmaps Key: FLINK-30004 URL: https://issues.apache.org/jira/browse/FLINK-30004

Re: [DISCUSS] Create a dedicated aws-base connector repository

Hi Danny, I'm also leaning slightly towards the single AWS connector repo direction. Bumps in the underlying AWS SDK would bump all of the connectors in any case. And if a change occurs that is isolated to a single connector, then those that do not use that connector can just skip the release.

[jira] [Created] (FLINK-29634) Support periodic checkpoint triggering

Thomas Weise created FLINK-29634: Summary: Support periodic checkpoint triggering Key: FLINK-29634 URL: https://issues.apache.org/jira/browse/FLINK-29634 Project: Flink Issue Type: New

Re: [VOTE] Externalized connector release details​

goes beyond a > patch release you'd create a new minor version and could have that only > support the later version. > > On 13/10/2022 02:05, Thomas Weise wrote: > > "Branches are not specific to a Flink version. (i.e., no v3.2-1.15)" > > > > Sorry for t

Re: [VOTE] Externalized connector release details​

"Branches are not specific to a Flink version. (i.e., no v3.2-1.15)" Sorry for the late question. I could not find in the discussion thread how a connector can make use of features of the latest Flink version that were not present in the previous Flink version, when branches cannot be Flink

Re: [DISCUSS] Reference operator from Flink Kubernetes deployment docs

+1 On Wed, Oct 12, 2022 at 5:03 PM Martijn Visser wrote: > +1 from my end to include the operator in the related Kubernetes sections > of the Flink docs > > On Wed, Oct 12, 2022 at 5:31 PM Chesnay Schepler > wrote: > > > I don't see a reason for why we shouldn't at least mention the operator

Re: [VOTE] Apache Flink Kubernetes Operator Release 1.2.0, release candidate #2

+1 (binding) Built from tag, manually tested upgrade mode change scenarios, upgraded existing environment On Thu, Oct 6, 2022 at 4:00 PM Márton Balassi wrote: > +1 (binding) > > Verified upgrade process from 1.1 with a running application > > On Thu, Oct 6, 2022 at 5:52 PM Biao Geng wrote: >

[jira] [Created] (FLINK-29497) Provide an option to publish the flink-dist jar file artifact

Thomas Weise created FLINK-29497: Summary: Provide an option to publish the flink-dist jar file artifact Key: FLINK-29497 URL: https://issues.apache.org/jira/browse/FLINK-29497 Project: Flink

Re: [VOTE] FLIP-258 Guarantee binary compatibility for Public/-Evolving APIs between patch releases​

+1 On Wed, Sep 7, 2022 at 4:48 AM Danny Cranmer wrote: > +1 > > On Wed, 7 Sept 2022, 07:32 Zhu Zhu, wrote: > > > +1 > > > > Thanks, > > Zhu > > > > Jingsong Li 于2022年9月6日周二 19:49写道： > > > > > > +1 > > > > > > On Tue, Sep 6, 2022 at 7:11 PM Yu Li wrote: > > > > > > > > +1 > > > > > > > >

Re: [DISCUSS] Switch docker iamge base to Eclipse Temurin

+1, the change to Ubuntu (hopefully) also reduces the ripple effect for downstream customizers of the image. On Thu, Sep 1, 2022 at 10:00 AM Chesnay Schepler wrote: > Unless anyone objects I will announce the switch on Monday via the > mailing lists / twitter and execute it on Wednesday. > >

[jira] [Created] (FLINK-29159) Revisit/harden initial deployment logic

Thomas Weise created FLINK-29159: Summary: Revisit/harden initial deployment logic Key: FLINK-29159 URL: https://issues.apache.org/jira/browse/FLINK-29159 Project: Flink Issue Type

[jira] [Created] (FLINK-29109) Checkpoint path conflict with stateless upgrade mode

Thomas Weise created FLINK-29109: Summary: Checkpoint path conflict with stateless upgrade mode Key: FLINK-29109 URL: https://issues.apache.org/jira/browse/FLINK-29109 Project: Flink Issue

[jira] [Created] (FLINK-29100) Deployment with last-state upgrade mode stuck after initial error

Thomas Weise created FLINK-29100: Summary: Deployment with last-state upgrade mode stuck after initial error Key: FLINK-29100 URL: https://issues.apache.org/jira/browse/FLINK-29100 Project: Flink

Re: [DISCUSS] Bump Kafka to 3.2.1 for 1.16.0

+1 for bumping the Kafka dependency. Flink X.Y.0 releases require thorough testing, so considering the severity of the problem this is still good timing, even that close to the first RC. Thanks for bringing this up. Thomas On Tue, Aug 9, 2022 at 7:51 AM Chesnay Schepler wrote: > Hello, > >

Re: [VOTE] FLIP-217: Support watermark alignment of source splits

+1 (binding) On Sun, Jul 31, 2022 at 10:57 PM Sebastian Mattheis wrote: > Hi everyone, > > I would like to start the vote for FLIP-217 [1]. Thanks for your feedback > and the discussion in [2]. > > FLIP-217 is a follow-up on FLIP-182 [3] and adds support for watermark > alignment of source

Re: [DISCUSS] FLIP-217 Support watermark alignment of source splits

As for the parameter naming, I have implemented it the following way > >> (reason: There exists a parameter `pipeline.auto-watermark-interval`.): > >> > >> pipeline.watermark-alignment.allow-unaligned-source-splits (default: > >> false) > >> >

Re: [VOTE] Apache Flink Kubernetes Operator Release 1.1.0, release candidate #1

+1 (binding) * built from source archive * run examples Thanks, Thomas On Wed, Jul 20, 2022 at 5:48 AM Gyula Fóra wrote: > > Hi everyone, > > Please review and vote on the release candidate #1 for the version 1.1.0 of > Apache Flink Kubernetes Operator, > as follows: > [ ] +1, Approve the

Re: [DISCUSS] FLIP-217 Support watermark alignment of source splits

;> > updated implementation [2].) >>>>> > >>>>> > Please consider the following updated specification in the current >>>>> > status >>>>> > of FLIP-217 where the essence is as follows: >>>>> > >>

Re: Python Job Support for the Kubernetes Operator

Since SQL or Python are essentially just examples of how to use the operator vs. features of the operator itself, they should not affect the release schedule and can be added anytime, as examples to the operator or elsewhere. Thanks, Thomas On Wed, Jul 6, 2022 at 8:33 AM Gyula Fóra wrote: > >

Re: [DISCUSS] Contribution of Multi Cluster Kafka Source

Hi Mason, I added mason6345 to the Flink confluence space, you should be able to add a FLIP now. Looking forward to the contribution! Thomas On Thu, Jun 30, 2022 at 9:25 AM Martijn Visser wrote: > > Hi Mason, > > I'm sure there's a PMC (*hint*) out there who can grant you access to > create a

Re: [DISCUSS] FLIP-217 Support watermark alignment of source splits

Hi everyone, Thank you for all the effort that went into this discussion. The split level watermark alignment will be an important feature for Flink that will address operational problems for various use cases. From reading through this thread it appears that not too much remains to bring this

Re: [DISCUSS] Next Flink Kubernetes Operator release timeline

I think before we release 1.0, we need to define and document the compatibility guarantees. At the moment, the CR changes frequently and as was pointed out earlier, there isn't any automation to ensure changes are backward compatible. In addition, our documentation still refers to upgrade as a

Re: [DISCUSS ] HybridSouce Table & Sql api timeline

fyi there is a related ticket here: https://issues.apache.org/jira/browse/FLINK-22793 On Mon, May 9, 2022 at 11:34 PM Becket Qin wrote: > > Cool, I've granted you the permission. > > Cheers, > > Jiangjie (Becket) Qin > > On Tue, May 10, 2022 at 1:14 PM Ran Tao wrote: > > > Hi, Becket. Thanks

Re: JobManager High Availability

+1 to what Konstantin said. There is no real benefit running multiple JMs on k8s, unless you need to optimize the JM startup time. Often the time to get a replacement pod is negligible compared to the job restart time. Thomas On Tue, May 10, 2022 at 2:27 AM Őrhidi Mátyás wrote: > > Ah, ok.

Re: Re: [ANNOUNCE] New Flink PMC member: Yang Wang

Congratulations, Yang! On Tue, May 10, 2022 at 3:15 AM Márton Balassi wrote: > > Congrats, Yang. Well deserved :-) > > On Tue, May 10, 2022 at 9:16 AM Terry Wang wrote: > > > Congrats Yang! > > > > On Mon, May 9, 2022 at 11:19 AM LuNing Wang wrote: > > > > > Congrats Yang! > > > > > > Best, >

Re: [ANNOUNCE] Apache Flink 1.15.0 released

Thank you to all who contributed for making this release happen! Thomas On Thu, May 5, 2022 at 7:41 AM Zhu Zhu wrote: > > Thanks Yun, Till and Joe for the great work and thanks everyone who > makes this release possible! > > Cheers, > Zhu > > Jiangang Liu 于2022年5月5日周四 21:09写道： > > > >

Re: Source alignment for Iceberg

atermarks to increase in cases >> >> where >> >> >> fewer splits than source tasks are available. However, for sources with >> >> >> dynamic split discovery that actually yields incorrect results. Think >> >> of a >> >> >&g

Re: Source alignment for Iceberg

t;> >> > >> >>> >> > In our case, when the pluggables are SplitEnumerator and >> >>> SourceReader, >> >>> >> the >> >>> >> > control flows that only involve user space actions are fully >> &g

Re: [RESULT] [VOTE] Release 1.15.0, release candidate #4

Hi, Thank you for working on the 1.15.0 release. Is there an update wrt finalizing the release? Thanks, Thomas On Mon, Apr 25, 2022 at 9:17 PM Yun Gao wrote: > I'm happy to announce that we have unanimously approved this release. > > There are 6 explicit approving votes, 3 of which are

Re: Failed Unit Test on Master Branch

I reproduced the issue. The inconsistent test result is due to time zone dependency in the test. The underlying issue is that convertToTimestamp attempts to set negative value with java.sql.Timestamp.setNanos https://issues.apache.org/jira/browse/FLINK-27465 Thanks, Thomas On Thu, Apr 28,

[jira] [Created] (FLINK-27465) AvroRowDeserializationSchema.convertToTimestamp fails with negative nano seconds

Thomas Weise created FLINK-27465: Summary: AvroRowDeserializationSchema.convertToTimestamp fails with negative nano seconds Key: FLINK-27465 URL: https://issues.apache.org/jira/browse/FLINK-27465

[jira] [Created] (FLINK-27435) Kubernetes Operator keeps savepoint history

Thomas Weise created FLINK-27435: Summary: Kubernetes Operator keeps savepoint history Key: FLINK-27435 URL: https://issues.apache.org/jira/browse/FLINK-27435 Project: Flink Issue Type

Re: [DISCUSS] FLIP-217 Support watermark alignment of source splits

Thanks for working on this! I wonder if "supporting" split alignment in SourceReaderBase and then doing nothing if the split reader does not implement AlignedSplitReader could be misleading? Perhaps WithSplitsAlignment can instead be added to the specific source reader (i.e. KafkaSourceReader) to

Re: [DISCUSS] Make Kubernetes Operator config "dynamic" and consider merging with flinkConfiguration

Hi Gyula, Can you please specify which of the current settings you see as candidates to expose to the user? Force upgrade definitely makes sense and there will likely be others going forward that govern the upgrade or shutdown behavior. The main consideration should probably be that settings that

Re: [VOTE] Apache Flink Kubernetes Operator Release 0.1.0, release candidate #3

+1 (binding) * installed from staged helm chart and run example * built from source On Wed, Mar 30, 2022 at 7:39 AM Gyula Fóra wrote: > Hi everyone, > > Please review and vote on the release candidate #3 for the version 0.1.0 of > Apache Flink Kubernetes Operator, > as follows: > [ ] +1,

Re: [VOTE] Apache Flink Kubernetes Operator Release 0.1.0, release candidate #1

I believe if we as the PMC distribute a docker image (which is optional, "convenience"), then that image has to follow the rules for binary packages [1]. (And I would assume that applies regardless where we host the images.) Now to say that we only publish sources kind of side steps that problem.

[jira] [Created] (FLINK-26812) Flink native k8s integration should support owner reference

Thomas Weise created FLINK-26812: Summary: Flink native k8s integration should support owner reference Key: FLINK-26812 URL: https://issues.apache.org/jira/browse/FLINK-26812 Project: Flink

[jira] [Created] (FLINK-26811) Document CRD upgrade process

Thomas Weise created FLINK-26811: Summary: Document CRD upgrade process Key: FLINK-26811 URL: https://issues.apache.org/jira/browse/FLINK-26811 Project: Flink Issue Type: Sub-task

Re: [DISCUSS] Support the session job management in kubernetes operator

Hi Aitozi, Thanks for the proposal. Can you please clarify in the FLIP the relationship between the session deployment and the jobs that depend on it? Will, for example, the operator ensure that the individual jobs are deleted when the underlying cluster is deleted? Side note: When the

[jira] [Created] (FLINK-26639) Publish flink-kubernetes-operator maven artifacts

Thomas Weise created FLINK-26639: Summary: Publish flink-kubernetes-operator maven artifacts Key: FLINK-26639 URL: https://issues.apache.org/jira/browse/FLINK-26639 Project: Flink Issue Type

[jira] [Created] (FLINK-26554) Clean termination of FlinkDeployment

Thomas Weise created FLINK-26554: Summary: Clean termination of FlinkDeployment Key: FLINK-26554 URL: https://issues.apache.org/jira/browse/FLINK-26554 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-26538) Ability to restart deployment w/o spec change

Thomas Weise created FLINK-26538: Summary: Ability to restart deployment w/o spec change Key: FLINK-26538 URL: https://issues.apache.org/jira/browse/FLINK-26538 Project: Flink Issue Type

Re: [DISCUSS] Flink Kubernetes Operator controller flow

Thanks for bringing the discussion. It's a good time to revisit this area as the operator implementation becomes more complex. I think the most important part of the design are well defined states and transitions. Unless that can be reasoned about, there will be confusion. For example: 1) For

Re: [DISCUSS] Plan to externalize connectors and versioning

This plan LGTM. Thanks, Thomas On Wed, Feb 23, 2022 at 4:28 AM Chesnay Schepler wrote: > > That sounds fine to me. > > On 23/02/2022 10:49, Konstantin Knauf wrote: > > Hi Chesnay, Hi everyone, > > > > I think the idea for the migration is the following (with the example of > > ElasticSearch). I

[jira] [Created] (FLINK-26290) Revisit serviceAccount and taskSlots direct fields in CRD

Thomas Weise created FLINK-26290: Summary: Revisit serviceAccount and taskSlots direct fields in CRD Key: FLINK-26290 URL: https://issues.apache.org/jira/browse/FLINK-26290 Project: Flink

[jira] [Created] (FLINK-26261) Reconciliation should try to start job when not already started or move to permanent error

Thomas Weise created FLINK-26261: Summary: Reconciliation should try to start job when not already started or move to permanent error Key: FLINK-26261 URL: https://issues.apache.org/jira/browse/FLINK-26261

Re: [DISCUSS] FLIP-212: Introduce Flink Kubernetes Operator

at Netty adds unnecessary complexity to the > > > > > webhook > > > > > > > implementation we are open to alternative backends such as > > > Springboot > > > > > for > > > > > > > instance which would practically eliminate all the boile

Re: [DISCUSS] FLINK-25927: Make flink-connector-base dependency usage consistent across all connectors

> > Doesn't that mean that such dependency conflicts are then user errors? > > On 10/02/2022 20:19, Thomas Weise wrote: > > Hi Alexander, > > It is beneficial for users to be able to replace/choose a connector as > part of their application. When flink-connector-base is includ

Re: [DISCUSS] FLINK-25927: Make flink-connector-base dependency usage consistent across all connectors

Hi Alexander, It is beneficial for users to be able to replace/choose a connector as part of their application. When flink-connector-base is included in dist, that becomes more difficult. We can run into hard to understand dependency conflicts such as [1]. Depending on the Flink platform used, it

[RESULT] [VOTE] FLIP-212: Introduce Flink Kubernetes Operator

Hi everyone, FLIP-212 [1] has been accepted. There were 7 binding +1 votes and 6 non-binding +1 votes. No other votes. binding: Gyula Fóra Márton Balassi Xintong Song Yang Wang Danny Cranmer Yangze Guo Thomas Weise non-binding: Chenya Zhang Shqiprim Bunjaku Israel Ekpo Peter Huang Biao Geng K

Re: [VOTE] FLIP-212: Introduce Flink Kubernetes Operator

:53 AM Shqiprim Bunjaku < > > > > > > > > > shqiprimbunj...@gmail.com> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > +1 (non-binding) > > > > > > > > > > > > > >

Re: [DISCUSS] FLIP-212: Introduce Flink Kubernetes Operator

gt; > > > > > Will definitely check this out. You are right, Kotlin makes it > > > difficult to > > > > > adopt pieces of this code directly but I think it will be good > > > > > to get inspiration for the architecture and look at how > > &

Re: [DISCUSS] Checkpointing (partially) failing jobs

Hi, Thanks for opening this discussion! The proposed enhancement would be interesting for use cases in our infrastructure as well. There are scenarios where it makes sense to have multiple disconnected subgraphs in a single job because it can significantly reduce the operational burden as well

[VOTE] FLIP-212: Introduce Flink Kubernetes Operator

Hi everyone, I'd like to start a vote on FLIP-212: Introduce Flink Kubernetes Operator [1] which has been discussed in [2]. The vote will be open for at least 72 hours unless there is an objection or not enough votes. [1]

Re: [DISCUSS] FLIP-212: Introduce Flink Kubernetes Operator

reat feedback, Thomas has updated the FLIP page > > > > > accordingly. If you are comfortable with the currently existing > > design > > > > and > > > > > depth in the FLIP [1] I suggest moving forward to the voting stage - > > &

[jira] [Created] (FLINK-25963) FLIP-212: Introduce Flink Kubernetes Operator

Thomas Weise created FLINK-25963: Summary: FLIP-212: Introduce Flink Kubernetes Operator Key: FLINK-25963 URL: https://issues.apache.org/jira/browse/FLINK-25963 Project: Flink Issue Type

Re: [DISCUSS] FLIP-212: Introduce Flink Kubernetes Operator

wo versions, similar to how other major features have evolved recently, such as FLIP-27. Would be great to get broader feedback on this one. Cheers, Thomas > > Thank you~ > > Xintong Song > > > > On Fri, Jan 28, 2022 at 1:18 PM Thomas Weise wrote: > > > Thanks

Re: [VOTE] Deprecate Per-Job Mode in Flink 1.15

+1 (binding) On Fri, Jan 28, 2022 at 9:27 AM David Morávek wrote: > +1 (non-binding) > > D. > > On Fri 28. 1. 2022 at 17:53, Till Rohrmann wrote: > > > +1 (binding) > > > > Cheers, > > Till > > > > On Fri, Jan 28, 2022 at 4:57 PM Gabor Somogyi > > > wrote: > > > > > +1 (non-binding) > > > > >

Re: [DISCUSS] FLIP-212: Introduce Flink Kubernetes Operator

Thanks for the feedback! > > # 1 Flink Native vs Standalone integration > Maybe we should make this more clear in the FLIP but we agreed to do the > first version of the operator based on the native integration. > While this clearly does not cover all use-cases and requirements, it seems > this

[DISCUSS] FLIP-212: Introduce Flink Kubernetes Operator

Hi, As promised in [1] we would like to start the discussion on the addition of a Kubernetes operator to the Flink project as FLIP-212: https://cwiki.apache.org/confluence/display/FLINK/FLIP-212%3A+Introduce+Flink+Kubernetes+Operator Please note that the FLIP is currently focussed on the overall

[ANNOUNCE] Apache Flink 1.14.3 released

The Apache Flink community is very happy to announce the release of Apache Flink 1.14.3, which is the second bugfix release for the Apache Flink 1.14 series. Apache Flink® is an open-source stream processing framework for distributed, high-performing, always-available, and accurate data streaming

Re: [VOTE] Moving connectors from Flink to external connector repositories

+1 (binding) I think it would be a good idea to test the new infrastructure with a sample connector for the next release before moving existing connectors. On Wed, Jan 19, 2022 at 7:56 AM Till Rohrmann wrote: > +1 (binding) > > Cheers, > Till > > On Wed, Jan 19, 2022 at 3:58 PM Timo Walther

Re: [VOTE] Creating external connector repositories

+1 (binding) On Wed, Jan 19, 2022 at 7:57 AM Till Rohrmann wrote: > +1 > > Cheers, > Till > > On Wed, Jan 19, 2022 at 4:01 PM Timo Walther wrote: > > > +1 (binding) > > > > Regards, > > Timo > > > > On 19.01.22 14:47, Martijn Visser wrote: > > > Hi everyone, > > > > > > I'd like to start a

Re: [VOTE] Release 1.14.3, release candidate #1

Progress: We are waiting for the dockerhub update: https://github.com/docker-library/official-images/pull/11693 Cheers, Thomas On Mon, Jan 17, 2022 at 1:39 PM Thomas Weise wrote: > > Release finalization steps have been completed, except for the Docker images. > > Can someone pl

Re: [VOTE] Release 1.14.3, release candidate #1

> >>>>>> >> >>>>>> >> >>>>>>* Checked the signature of source code, some of binaries and >> >>>>>> some >> >>>> of >> >>>>>> python packages. >> >>>>

Re: [DISCUSS] Future of Per-Job Mode

Regarding session mode: ## Session Mode * main() method executed in client Session mode also supports execution of the main method on Jobmanager with submission through REST API. That's how Flinkk k8s operators like [1] work. It's actually an important capability because it allows for allocation

Re: Flink native k8s integration vs. operator

> understand the job's resource requirements and adjust the deployment > >>> resource accordingly. Both fine-grained resource management (customizing > >>> TM > >>> resources for different tasks / operators) and adaptive batch scheduler > >>> (

Re: [VOTE] FLIP-206: Support PyFlink Runtime Execution in Thread Mode

+1 (binding) On Wed, Jan 12, 2022 at 4:58 AM Till Rohrmann wrote: > > +1 (binding) > > Cheers, > Till > > On Wed, Jan 12, 2022 at 11:07 AM Wei Zhong wrote: > > > +1(binding) > > > > Best, > > Wei > > > > > 2022年1月12日 下午5:58，Xingbo Huang 写道： > > > > > > Hi all, > > > > > > I would like to start

Use of JIRA fixVersion

Hi, As part of preparing the 1.14.3 release, I observed that there were around 200 JIRA issues with fixVersion 1.14.3 that were unresolved (after blocking issues had been dealt with). Further cleanup resulted in removing fixVersion 1.14.3 from most of these and we are left with [1] - these are

Re: [DISCUSS] FLIP-206: Support PyFlink Runtime Execution in Thread Mode

mplementation can > >> make > >> > it easier to evaluate the performance of different execution modes. > >> > > >> > >>> What do you observe when the function becomes more complex? > >> > > >> > We can analyze the QPS of the

Re: [DISCUSS] Releasing Flink 1.14.3

lts?buildId=1704=results > > Best, > Xingbo > > Thomas Weise 于2022年1月10日周一 11:12写道： > > > Hi Martijn, > > > > I started building the release artifacts. The Maven part is ready. > > Currently blocked on the Azure build for the PyFlink wheel packages. > >

Re: [DISCUSS] Releasing Flink 1.14.3

; > Hi Thomas, > > Thanks for volunteering! There was no volunteer yet, so would be great if > you could help out. > > Best regards, > > Martijn > > Op vr 7 jan. 2022 om 01:54 schreef Thomas Weise > > > Hi Martijn, > > > > Thanks for preparing the rele

Re: [DISCUSS] Releasing Flink 1.14.3

Hi Martijn, Thanks for preparing the release. Did a volunteer check in with you? If not, I would like to take this up. Thomas On Mon, Dec 27, 2021 at 7:11 AM Martijn Visser wrote: > > Thank you all! That means that there's currently no more blocker to start > with the Flink 1.14.3 release. > >

Re: [DISCUSS] Changing the minimal supported version of Hadoop

+1 for bumping minimum supported Hadoop version to 2.8.5 On Mon, Jan 3, 2022 at 12:25 AM David Morávek wrote: > > As there were no strong objections, we'll proceed with bumping the Hadoop > version to 2.8.5 and removing the safeguards and the CI for any earlier > versions. This will effectively

Re: [DISCUSS] FLIP-206: Support PyFlink Runtime Execution in Thread Mode

Interesting discussion. It caught my attention because I was also interested in the Beam fn execution overhead a few years ago. We found back then that while in theory the fn protocol overhead is very significant, for realistic function workloads that overhead was negligible. And of course it all

Re: [DISCUSS] FLIP-207: Flink backward and forward compatibility

Hi Jing, AFAIK most of the pain is caused by lack of backward compatibility (binary). And to make sure I'm not adding to the confusion: It would be necessary to be able to run the iceberg connector built against Flink 1.12 with a Flink 1.13 distribution. That would solve most problems downstream

Re: [DISCUSS] Creating an external connector repository

ures before a release. > >> > > >>>>>>> - If there is a bugfix, release immediately or soonish > >> depending > >> > > >>>>>>> on > >> > > >>>>> the > >> > > >&

Re: [VOTE] Deprecate Java 8 support

+1 (binding) On Wed, Dec 8, 2021 at 2:20 AM Till Rohrmann wrote: > > +1 (binding) > > Cheers, > Till > > On Tue, Dec 7, 2021 at 12:35 PM Matthias Pohl > wrote: > > > Thanks for pushing this Chesnay! > > +1 (binding) > > > > On Mon, Dec 6, 2021 at 9:44 PM Martijn Visser > > wrote: > > > > > +1

  1   2   3   4   >