Re: [DISCUSS] Connector Externalization Retrospective
that getting to the > binary compatibility guarantee is our goal - not just for the connectors > managed within the Flink project but for the ecosystem as a whole - I don't > see the benefit of mono repo or similar approach that targets the symptom > rather than the cause. > > In the final picture we would only need connector releases if/when a > specific connector changes and the repository per connector layout would > work well. > > I also agree with Danny that we may not have to wait for Flink 2.0 for > that. How close are we to assume compatibility of the API surface that > affects connectors? It appears that practically there have been little to > no known issues in the last couple of releases? Would it be possible to > verify that by running e2e tests of connector binaries built against an > earlier Flink minor version against the latest Flink minor release > candidate as part of the release? > > Thanks, > Thomas > > > On Tue, Jun 11, 2024 at 11:05 AM Chesnay Schepler > wrote: > > > On 10/06/2024 18:25, Danny Cranmer wrote: > > > This would > > > mean we would usually not need to release a new connector version per > > Flink > > > version, assuming there are no breaking changes. > > We technically can't do this because we don't provide binary > > compatibility across minor versions. > > That's the entire reason we did this coupling in the first place, and > > imo /we/ shouldn't take a shortcut but still have our users face that > > very problem. > > We knew this was gonna by annoying for us; that was intentional and > > meant to finally push us towards binary compatibility /guarantees/. >
Re: [DISCUSS] Connector releases for Flink 1.19
Hey Sergey, I have completed the 3 tasks. Let me know if you need anything else. Thanks, Danny On Tue, Jun 11, 2024 at 9:11 AM Danny Cranmer wrote: > Thanks for driving this Sergey, I will pick up the PMC tasks. > > Danny > > On Sun, Jun 9, 2024 at 11:09 PM Sergey Nuyanzin > wrote: > >> Hi everyone, >> >> as you might noticed the voting threads for release of flink-opensearch >> connectors (v1, v2) received 3+ binding votes[1][2] >> >> Now I need PMC help to finish the release of these 2. >> I'm on the step "Deploy source and binary releases to dist.apache.org"[3] >> for both versions >> An attempt to execute this step says that access is forbidden, I assume >> that only PMC have access to do it >> >> I guess there are 3 things which should be done and where only PMC have >> access and where I need help >> 1. As mentioned deploying to dist.apache.org >> 2. Mark version as released on jira >> 3. Place a record on reporter.apache.org about the release >> >> Would be great if someone from PMC could help here >> >> [1] https://lists.apache.org/thread/kno142xdzqg592tszmnonk69nl14xszl >> [2] https://lists.apache.org/thread/by44cdpfv6p9394vwxhh1vzh3rfskzms >> [3] >> https://cwiki.apache.org/confluence/display/FLINK/Creating+a+flink-connector+release#Creatingaflinkconnectorrelease-Deploysourceandbinaryreleasestodist.apache.org >> >> On Fri, May 31, 2024 at 7:53 AM Sergey Nuyanzin >> wrote: >> >>> Hi Jing, >>> >Thanks for the hint wrt JDBC connector. Where could users know that it >>> > already supports 1.19? >>> >>> There is no released version supporting/tested against 1.19 >>> However the support was added within [1] and currently >>> there is an active RC in voting stage containing this fix [2] >>> >>> [1] >>> https://github.com/apache/flink-connector-jdbc/commit/7025642d88ff661e486745b23569595e1813a1d0 >>> [2] https://lists.apache.org/thread/b7xbjo4crt1527ldksw4nkwo8vs56csy >>> >> >> >> -- >> Best regards, >> Sergey >> >
Re: [DISCUSS] Connector releases for Flink 1.19
Thanks for driving this Sergey, I will pick up the PMC tasks. Danny On Sun, Jun 9, 2024 at 11:09 PM Sergey Nuyanzin wrote: > Hi everyone, > > as you might noticed the voting threads for release of flink-opensearch > connectors (v1, v2) received 3+ binding votes[1][2] > > Now I need PMC help to finish the release of these 2. > I'm on the step "Deploy source and binary releases to dist.apache.org"[3] > for both versions > An attempt to execute this step says that access is forbidden, I assume > that only PMC have access to do it > > I guess there are 3 things which should be done and where only PMC have > access and where I need help > 1. As mentioned deploying to dist.apache.org > 2. Mark version as released on jira > 3. Place a record on reporter.apache.org about the release > > Would be great if someone from PMC could help here > > [1] https://lists.apache.org/thread/kno142xdzqg592tszmnonk69nl14xszl > [2] https://lists.apache.org/thread/by44cdpfv6p9394vwxhh1vzh3rfskzms > [3] > https://cwiki.apache.org/confluence/display/FLINK/Creating+a+flink-connector+release#Creatingaflinkconnectorrelease-Deploysourceandbinaryreleasestodist.apache.org > > On Fri, May 31, 2024 at 7:53 AM Sergey Nuyanzin > wrote: > >> Hi Jing, >> >Thanks for the hint wrt JDBC connector. Where could users know that it >> > already supports 1.19? >> >> There is no released version supporting/tested against 1.19 >> However the support was added within [1] and currently >> there is an active RC in voting stage containing this fix [2] >> >> [1] >> https://github.com/apache/flink-connector-jdbc/commit/7025642d88ff661e486745b23569595e1813a1d0 >> [2] https://lists.apache.org/thread/b7xbjo4crt1527ldksw4nkwo8vs56csy >> > > > -- > Best regards, > Sergey >
[DISCUSS] Connector Externalization Retrospective
Hello Flink community, It has been over 2 years [1] since we started externalizing the Flink connectors to dedicated repositories from the main Flink code base. The past discussions can be found here [2]. The community decided to externalize the connectors to primarily 1/ improve stability and speed of the CI, and 2/ decouple version and release lifecycle to allow the projects to evolve independently. The outcome of this has resulted in each connector requiring a dedicated release per Flink minor version, which is a burden on the community. Flink 1.19.0 was released on 2024-03-18 [3], the first supported connector followed roughly 2.5 months later on 2024-06-06 [4] (MongoDB). There are still 5 connectors that do not support Flink 1.19 [5]. Two decisions contribute to the high lag between releases. 1/ creating one repository per connector instead of a single flink-connector mono-repo and 2/ coupling the Flink version to the connector version [6]. A single connector repository would reduce the number of connector releases from N to 1, but would couple the connector CI and reduce release flexibility. Decoupling the connector versions from Flink would eliminate the need to release each connector for each new Flink minor version, but we would need a new compatibility mechanism. I propose that from each next connector release we drop the coupling on the Flink version. For example, instead of 3.4.0-1.20 (.) we would release 3.4.0 (). We can model a compatibility matrix within the Flink docs to help users pick the correct versions. This would mean we would usually not need to release a new connector version per Flink version, assuming there are no breaking changes. Worst case, if breaking changes impact all connectors we would still need to release all connectors. However, for Flink 1.17 and 1.18 there were only a handful of issues (breaking changes), and mostly impacting tests. We could decide to align this with Flink 2.0, however I see no compelling reason to do so. This was discussed previously [2] as a long term goal once the connector APIs are stable. But I think the current compatibility rules support this change now. I would prefer to not create a connector mono-repo. Separate repos gives each connector more flexibility to evolve independently, and removing unnecessary releases will significantly reduce the release effort. I would like to hear opinions and ideas from the community. In particular, are there any other issues you have observed that we should consider addressing? Thanks, Danny. [1] https://github.com/apache/flink-connector-elasticsearch/commit/3ca2e625e3149e8864a4ad478773ab4a82720241 [2] https://lists.apache.org/thread/8k1xonqt7hn0xldbky1cxfx3fzh6sj7h [3] https://flink.apache.org/2024/03/18/announcing-the-release-of-apache-flink-1.19/ [4] https://flink.apache.org/downloads/#apache-flink-connectors-1 [5] https://issues.apache.org/jira/browse/FLINK-35131 [6] https://cwiki.apache.org/confluence/display/FLINK/Externalized+Connector+development#ExternalizedConnectordevelopment-Examples
Re: [VOTE] Release flink-connector-opensearch v1.2.0, release candidate #1
Thanks for driving this Sergey. +1 (binding) - Release notes look good - Source archive checksum and signature is correct - Binary checksum and signature is correct - Contents of Maven repo looks good - Verified there are no binaries in the source archive - Builds from source using Java 8 (-Popensearch1) - CI run passed - Tag exists in repo - NOTICE and LICENSE files present and correct Thanks, Danny On Fri, Jun 7, 2024 at 4:27 AM Rui Fan <1996fan...@gmail.com> wrote: > Thanks Sergey for the hard work! > > +1(binding) > > - Verified signatures > - Verified sha512 (hashsums) > - The source archives do not contain any binaries > - Build the source with Maven 3 and java8 (Checked the license as well) > - Checked Github release tag > - Reviewed the flink-web PR > > Best, > Rui > > On Thu, May 30, 2024 at 8:22 PM weijie guo > wrote: > > > Thanks Sergey for driving this release! > > > > +1(non-binding) > > > > 1. Verified signatures and hash sums > > 2. Build from source with 1.8.0_291 succeeded > > 3. Checked RN. > > > > Best regards, > > > > Weijie > > > > > > Yuepeng Pan 于2024年5月30日周四 10:08写道： > > > > > +1 (non-binding) > > > > > > - Built from source code with JDK 1.8 on MaxOS- Run examples locally.- > > > Checked release notes Best, Yuepeng Pan > > > > > > > > > At 2024-05-28 22:53:10, "gongzhongqiang" > > > wrote: > > > >+1(non-binding) > > > > > > > >- Verified signatures and hash sums > > > >- Reviewed the web PR > > > >- Built from source code with JDK 1.8 on Ubuntu 22.04 > > > >- Checked release notes > > > > > > > >Best, > > > >Zhongqiang Gong > > > > > > > > > > > >Sergey Nuyanzin 于2024年5月16日周四 06:03写道： > > > > > > > >> Hi everyone, > > > >> Please review and vote on release candidate #1 for > > > >> flink-connector-opensearch v1.2.0, as follows: > > > >> [ ] +1, Approve the release > > > >> [ ] -1, Do not approve the release (please provide specific > comments) > > > >> > > > >> > > > >> The complete staging area is available for your review, which > > includes: > > > >> * JIRA release notes [1], > > > >> * the official Apache source release to be deployed to > > dist.apache.org > > > >> [2], > > > >> which are signed with the key with fingerprint > > > >> F7529FAE24811A5C0DF3CA741596BBF0726835D8 [3], > > > >> * all artifacts to be deployed to the Maven Central Repository [4], > > > >> * source code tag v1.2.0-rc1 [5], > > > >> * website pull request listing the new release [6]. > > > >> * CI build of the tag [7]. > > > >> > > > >> The vote will be open for at least 72 hours. It is adopted by > majority > > > >> approval, with at least 3 PMC affirmative votes. > > > >> > > > >> Note that this release is for Opensearch v1.x > > > >> > > > >> Thanks, > > > >> Release Manager > > > >> > > > >> [1] https://issues.apache.org/jira/projects/FLINK/versions/12353812 > > > >> [2] > > > >> > > > >> > > > > > > https://dist.apache.org/repos/dist/dev/flink/flink-connector-opensearch-1.2.0-rc1 > > > >> [3] https://dist.apache.org/repos/dist/release/flink/KEYS > > > >> [4] > > > https://repository.apache.org/content/repositories/orgapacheflink-1734 > > > >> [5] > > > >> > > > >> > > > > > > https://github.com/apache/flink-connector-opensearch/releases/tag/v1.2.0-rc1 > > > >> [6] https://github.com/apache/flink-web/pull/740 > > > >> [7] > > > >> > > > >> > > > > > > https://github.com/apache/flink-connector-opensearch/actions/runs/9102334125 > > > >> > > > > > >
Re: [VOTE] Release flink-connector-opensearch v2.0.0, release candidate #1
Thanks for driving this Sergey. +1 (binding) - Release notes look good - Source archive checksum and signature is correct - Binary checksum and signature is correct - Contents of Maven repo looks good - Verified there are no binaries in the source archive - Builds from source using Java 11 (-Popensearch2) - CI run passed - Tag exists in repo - NOTICE and LICENSE files present and correct Thanks, Danny On Fri, Jun 7, 2024 at 4:17 AM Rui Fan <1996fan...@gmail.com> wrote: > Thanks Sergey for the hard work! > > +1(binding) > > - Verified signatures > - Verified sha512 (hashsums) > - The source archives do not contain any binaries > - Build the source with Maven 3 and java8 (Checked the license as well) > - Checked Github release tag > - Reviewed the flink-web PR > > Best, > Rui > > On Mon, May 27, 2024 at 5:35 PM Hang Ruan wrote: > > > +1 (non-binding) > > > > - verified signatures > > - verified hashsums > > - built from source code with JDK 11 succeed > > - checked release notes > > - reviewed the web PR > > > > Best, > > Hang > > > > Leonard Xu 于2024年5月22日周三 21:02写道： > > > > > > > > > +1 (binding) > > > > > > > > - verified signatures > > > > - verified hashsums > > > > - built from source code with JDK 1.8 succeeded > > > > - checked Github release tag > > > > - checked release notes > > > > - reviewed the web PR > > > > > > Supply more information about build from source code with JDK 1.8 > > > > > > > - built from source code with JDK 1.8 succeeded > > > It’s correct as we don’t activate opensearch2 profile by default. > > > > > > - built from source code with JDK 1.8 and -Popensearch2 failed > > > - built from source code with JDK 11 and -Popensearch2 succeeded > > > > > > Best, > > > Leonard > > > > > > > > > > > > > > > > > >> 2024年5月16日 上午6:58，Andrey Redko 写道： > > > >> > > > >> +1 (non-binding), thanks Sergey! > > > >> > > > >> On Wed, May 15, 2024, 6:00 p.m. Sergey Nuyanzin < > snuyan...@gmail.com> > > > wrote: > > > >> > > > >>> Hi everyone, > > > >>> Please review and vote on release candidate #1 for > > > >>> flink-connector-opensearch v2.0.0, as follows: > > > >>> [ ] +1, Approve the release > > > >>> [ ] -1, Do not approve the release (please provide specific > comments) > > > >>> > > > >>> > > > >>> The complete staging area is available for your review, which > > includes: > > > >>> * JIRA release notes [1], > > > >>> * the official Apache source release to be deployed to > > dist.apache.org > > > >>> [2], > > > >>> which are signed with the key with fingerprint > > > >>> F7529FAE24811A5C0DF3CA741596BBF0726835D8 [3], > > > >>> * all artifacts to be deployed to the Maven Central Repository [4], > > > >>> * source code tag v2.0.0-rc1 [5], > > > >>> * website pull request listing the new release [6]. > > > >>> * CI build of the tag [7]. > > > >>> > > > >>> The vote will be open for at least 72 hours. It is adopted by > > majority > > > >>> approval, with at least 3 PMC affirmative votes. > > > >>> > > > >>> Note that this release is for Opensearch v2.x > > > >>> > > > >>> Thanks, > > > >>> Release Manager > > > >>> > > > >>> [1] > https://issues.apache.org/jira/projects/FLINK/versions/12354674 > > > >>> [2] > > > >>> > > > >>> > > > > > > https://dist.apache.org/repos/dist/dev/flink/flink-connector-opensearch-2.0.0-rc1 > > > >>> [3] https://dist.apache.org/repos/dist/release/flink/KEYS > > > >>> [4] > > > >>> > > > > https://repository.apache.org/content/repositories/orgapacheflink-1735/ > > > >>> [5] > > > >>> > > > >>> > > > > > > https://github.com/apache/flink-connector-opensearch/releases/tag/v2.0.0-rc1 > > > >>> [6] https://github.com/apache/flink-web/pull/741 > > > >>> [7] > > > >>> > > > >>> > > > > > > https://github.com/apache/flink-connector-opensearch/actions/runs/9102980808 > > > >>> > > > > > > > > > > > > >
[ANNOUNCE] Apache flink-connector-kafka 3.2.0 released
The Apache Flink community is very happy to announce the release of Apache flink-connector-kafka 3.2.0 for Flink 1.18 and 1.19. Apache Flink® is an open-source stream processing framework for distributed, high-performing, always-available, and accurate data streaming applications. The release is available for download at: https://flink.apache.org/downloads.html The full release notes are available in Jira: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12354209 We would like to thank all contributors of the Apache Flink community who made this release possible! Regards, Danny
[ANNOUNCE] Apache flink-connector-jdbc 3.2.0 released
The Apache Flink community is very happy to announce the release of Apache flink-connector-jdbc 3.2.0 for Flink 1.18 and 1.19. Apache Flink® is an open-source stream processing framework for distributed, high-performing, always-available, and accurate data streaming applications. The release is available for download at: https://flink.apache.org/downloads.html The full release notes are available in Jira: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353143 We would like to thank all contributors of the Apache Flink community who made this release possible! Regards, Danny
[RESULT][VOTE] flink-connector-kafka 3.2.0, release candidate #1
I'm happy to announce that we have unanimously approved this release. There are 9 approving votes, 3 of which are binding: * Muhammet Orazov * Ahmed Hamdy * Hang Ruan * Aleksandr Pilipenko * Leonard Xu (binding) * Fabian Paul * Martijn Visser (binding) * Yanquan Lv * Danny Cranmer (binding) There are no disapproving votes. Thanks, Danny
Re: [VOTE] Release flink-connector-kafka v3.2.0, release candidate #1
Thanks all. This vote is now closed, I will announce the results in a separate thread. On Fri, Jun 7, 2024 at 11:45 AM Danny Cranmer wrote: > +1 (binding) > > - Release notes look good > - Source archive checksum and signature is correct > - Binary checksum and signature is correct > - Contents of Maven repo looks good > - Verified there are no binaries in the source archive > - Builds from source, tests pass using Java 8 > - CI run passed [1] > - Tag exists in repo > - NOTICE and LICENSE files present and correct > > Thanks, > Danny > > [1] > https://github.com/apache/flink-connector-kafka/actions/runs/8785158288 > > > On Fri, Jun 7, 2024 at 7:19 AM Yanquan Lv wrote: > >> +1 (non-binding) >> >> - verified gpg signatures >> - verified sha512 hash >> - built from source code with java 8/11/17 >> - checked Github release tag >> - checked the CI result >> - checked release notes >> >> Danny Cranmer 于2024年4月22日周一 21:56写道： >> >> > Hi everyone, >> > >> > Please review and vote on release candidate #1 for flink-connector-kafka >> > v3.2.0, as follows: >> > [ ] +1, Approve the release >> > [ ] -1, Do not approve the release (please provide specific comments) >> > >> > This release supports Flink 1.18 and 1.19. >> > >> > The complete staging area is available for your review, which includes: >> > * JIRA release notes [1], >> > * the official Apache source release to be deployed to dist.apache.org >> > [2], >> > which are signed with the key with fingerprint 125FD8DB [3], >> > * all artifacts to be deployed to the Maven Central Repository [4], >> > * source code tag v3.2.0-rc1 [5], >> > * website pull request listing the new release [6]. >> > * CI build of the tag [7]. >> > >> > The vote will be open for at least 72 hours. It is adopted by majority >> > approval, with at least 3 PMC affirmative votes. >> > >> > Thanks, >> > Danny >> > >> > [1] >> > >> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12354209 >> > [2] >> > >> > >> https://dist.apache.org/repos/dist/dev/flink/flink-connector-kafka-3.2.0-rc1 >> > [3] https://dist.apache.org/repos/dist/release/flink/KEYS >> > [4] >> https://repository.apache.org/content/repositories/orgapacheflink-1723 >> > [5] >> > https://github.com/apache/flink-connector-kafka/releases/tag/v3.2.0-rc1 >> > [6] https://github.com/apache/flink-web/pull/738 >> > [7] https://github.com/apache/flink-connector-kafka >> > >> >
Re: [VOTE] Release flink-connector-kafka v3.2.0, release candidate #1
+1 (binding) - Release notes look good - Source archive checksum and signature is correct - Binary checksum and signature is correct - Contents of Maven repo looks good - Verified there are no binaries in the source archive - Builds from source, tests pass using Java 8 - CI run passed [1] - Tag exists in repo - NOTICE and LICENSE files present and correct Thanks, Danny [1] https://github.com/apache/flink-connector-kafka/actions/runs/8785158288 On Fri, Jun 7, 2024 at 7:19 AM Yanquan Lv wrote: > +1 (non-binding) > > - verified gpg signatures > - verified sha512 hash > - built from source code with java 8/11/17 > - checked Github release tag > - checked the CI result > - checked release notes > > Danny Cranmer 于2024年4月22日周一 21:56写道： > > > Hi everyone, > > > > Please review and vote on release candidate #1 for flink-connector-kafka > > v3.2.0, as follows: > > [ ] +1, Approve the release > > [ ] -1, Do not approve the release (please provide specific comments) > > > > This release supports Flink 1.18 and 1.19. > > > > The complete staging area is available for your review, which includes: > > * JIRA release notes [1], > > * the official Apache source release to be deployed to dist.apache.org > > [2], > > which are signed with the key with fingerprint 125FD8DB [3], > > * all artifacts to be deployed to the Maven Central Repository [4], > > * source code tag v3.2.0-rc1 [5], > > * website pull request listing the new release [6]. > > * CI build of the tag [7]. > > > > The vote will be open for at least 72 hours. It is adopted by majority > > approval, with at least 3 PMC affirmative votes. > > > > Thanks, > > Danny > > > > [1] > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12354209 > > [2] > > > > > https://dist.apache.org/repos/dist/dev/flink/flink-connector-kafka-3.2.0-rc1 > > [3] https://dist.apache.org/repos/dist/release/flink/KEYS > > [4] > https://repository.apache.org/content/repositories/orgapacheflink-1723 > > [5] > > https://github.com/apache/flink-connector-kafka/releases/tag/v3.2.0-rc1 > > [6] https://github.com/apache/flink-web/pull/738 > > [7] https://github.com/apache/flink-connector-kafka > > >
Re: [RESULT][VOTE] flink-connector-jdbc 3.2.0, release candidate #1
Apologies, this was RC2, not RC1. On Fri, Jun 7, 2024 at 11:12 AM Danny Cranmer wrote: > I'm happy to announce that we have unanimously approved this release. > > There are 7 approving votes, 3 of which are binding: > * Ahmed Hamdy > * Hang Ruan > * Leonard Xu (binding) > * Yuepeng Pan > * Zhongqiang Gong > * Rui Fan (binding) > * Weijie Guo (binding) > > There was one -1 vote that was cancelled. > * Yuepeng Pan (CANCELLED) > > Thanks everyone! >
[RESULT][VOTE] flink-connector-jdbc 3.2.0, release candidate #1
I'm happy to announce that we have unanimously approved this release. There are 7 approving votes, 3 of which are binding: * Ahmed Hamdy * Hang Ruan * Leonard Xu (binding) * Yuepeng Pan * Zhongqiang Gong * Rui Fan (binding) * Weijie Guo (binding) There was one -1 vote that was cancelled. * Yuepeng Pan (CANCELLED) Thanks everyone!
Re: [VOTE] Release flink-connector-jdbc v3.2.0, release candidate #2
Thanks all. This vote is now closed, I will announce the results in a separate thread. On Fri, Jun 7, 2024 at 4:59 AM weijie guo wrote: > Thanks Danny! > > +1(binding) > - Verified signatures and hash sums > - Checked the CI build > - Checked the release note > - Reviewed the flink-web PR > - Build from source. > > Best regards, > > Weijie > > > Rui Fan <1996fan...@gmail.com> 于2024年6月7日周五 11:08写道： > > > Thanks Danny for the hard work! > > > > +1(binding) > > > > - Verified signatures > > - Verified sha512 (hashsums) > > - The source archives do not contain any binaries > > - Build the source with Maven 3 and java8 (Checked the license as well) > > - Checked Github release tag > > - Reviewed the flink-web PR > > > > Best, > > Rui > > > > On Tue, Jun 4, 2024 at 1:31 PM gongzhongqiang > > > wrote: > > > > > +1 (non-binding) > > > > > > - Validated checksum hash and signature. > > > - Confirmed that no binaries exist in the source archive. > > > - Built the source with JDK 8. > > > - Verified the web PR. > > > - Ensured the JAR is built by JDK 8. > > > > > > Best, > > > Zhongqiang Gong > > > > > > Danny Cranmer 于2024年4月18日周四 18:20写道： > > > > > > > Hi everyone, > > > > > > > > Please review and vote on the release candidate #1 for the version > > 3.2.0, > > > > as follows: > > > > [ ] +1, Approve the release > > > > [ ] -1, Do not approve the release (please provide specific comments) > > > > > > > > This release supports Flink 1.18 and 1.19. > > > > > > > > The complete staging area is available for your review, which > includes: > > > > * JIRA release notes [1], > > > > * the official Apache source release to be deployed to > dist.apache.org > > > > [2], > > > > which are signed with the key with fingerprint 125FD8DB [3], > > > > * all artifacts to be deployed to the Maven Central Repository [4], > > > > * source code tag v3.2.0-rc1 [5], > > > > * website pull request listing the new release [6]. > > > > * CI run of tag [7]. > > > > > > > > The vote will be open for at least 72 hours. It is adopted by > majority > > > > approval, with at least 3 PMC affirmative votes. > > > > > > > > Thanks, > > > > Danny > > > > > > > > [1] > > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353143 > > > > [2] > > > > > > > > > > https://dist.apache.org/repos/dist/dev/flink/flink-connector-jdbc-3.2.0-rc2 > > > > [3] https://dist.apache.org/repos/dist/release/flink/KEYS > > > > [4] > > > > > > https://repository.apache.org/content/repositories/orgapacheflink-1718/ > > > > [5] > > > https://github.com/apache/flink-connector-jdbc/releases/tag/v3.2.0-rc2 > > > > [6] https://github.com/apache/flink-web/pull/734 > > > > [7] > > > https://github.com/apache/flink-connector-jdbc/actions/runs/8736019099 > > > > > > > > > >
[ANNOUNCE] Apache flink-connector-cassandra 3.2.0 released
The Apache Flink community is very happy to announce the release of Apache flink-connector-cassandra 3.2.0 for Flink 1.18 and 1.19. Apache Flink® is an open-source stream processing framework for distributed, high-performing, always-available, and accurate data streaming applications. The release is available for download at: https://flink.apache.org/downloads.html The full release notes are available in Jira: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353148 We would like to thank all contributors of the Apache Flink community who made this release possible! Regards, Danny
[RESULT][VOTE] flink-connector-cassandra 3.2.0, release candidate #1
I'm happy to announce that we have unanimously approved this release. There are 6 approving votes, 3 of which are binding: * Muhammet Orazov * Ahmed Hamdy * Hang Ruan * Weijie Guo (binding) * Leonard Xu (binding) * Rui Fan (binding) There are no disapproving votes. Thanks, Danny
Re: [VOTE] Release flink-connector-cassandra v3.2.0, release candidate #1
Thanks all. This vote is now closed, I will announce the results in a separate thread. On Fri, Jun 7, 2024 at 5:02 AM weijie guo wrote: > Thanks Danny! > > +1(binding) > > - Verified signatures and hash sum > - Checked the CI build from tag > - Build from source > - Reviewed flink-web PR > > Best regards, > > Weijie > > > Rui Fan <1996fan...@gmail.com> 于2024年6月7日周五 11:01写道： > >> Thanks Danny for the hard work! >> >> +1(binding) >> >> - Verified signatures >> - Verified sha512 (hashsums) >> - The source archives do not contain any binaries >> - Build the source with Maven 3 and java8 (Checked the license as well) >> - Checked Github release tag >> - Reviewed the flink-web PR >> >> Best, >> Rui >> >> On Wed, May 22, 2024 at 8:01 PM Leonard Xu wrote: >> >> > +1 (binding) >> > >> > - verified signatures >> > - verified hashsums >> > - built from source code with java 1.8 succeeded >> > - checked Github release tag >> > - checked release notes status which only left one issue is used for >> > release tracking >> > - reviewed the web PR >> > >> > Best, >> > Leonard >> > >> > > 2024年5月22日 下午6:10，weijie guo 写道： >> > > >> > > +1(non-binding) >> > > >> > > -Validated checksum hash >> > > -Verified signature >> > > -Build from source >> > > >> > > Best regards, >> > > >> > > Weijie >> > > >> > > >> > > Hang Ruan 于2024年5月22日周三 10:12写道： >> > > >> > >> +1 (non-binding) >> > >> >> > >> - Validated checksum hash >> > >> - Verified signature >> > >> - Verified that no binaries exist in the source archive >> > >> - Build the source with Maven and jdk8 >> > >> - Verified web PR >> > >> - Check that the jar is built by jdk8 >> > >> >> > >> Best, >> > >> Hang >> > >> >> > >> Muhammet Orazov 于2024年5月22日周三 >> 04:15写道： >> > >> >> > >>> Hey all, >> > >>> >> > >>> Could we please get some more votes to proceed with the release? >> > >>> >> > >>> Thanks and best, >> > >>> Muhammet >> > >>> >> > >>> On 2024-04-22 13:04, Danny Cranmer wrote: >> > >>>> Hi everyone, >> > >>>> >> > >>>> Please review and vote on release candidate #1 for >> > >>>> flink-connector-cassandra v3.2.0, as follows: >> > >>>> [ ] +1, Approve the release >> > >>>> [ ] -1, Do not approve the release (please provide specific >> comments) >> > >>>> >> > >>>> This release supports Flink 1.18 and 1.19. >> > >>>> >> > >>>> The complete staging area is available for your review, which >> > includes: >> > >>>> * JIRA release notes [1], >> > >>>> * the official Apache source release to be deployed to >> > dist.apache.org >> > >>>> [2], >> > >>>> which are signed with the key with fingerprint 125FD8DB [3], >> > >>>> * all artifacts to be deployed to the Maven Central Repository [4], >> > >>>> * source code tag v3.2.0-rc1 [5], >> > >>>> * website pull request listing the new release [6]. >> > >>>> * CI build of the tag [7]. >> > >>>> >> > >>>> The vote will be open for at least 72 hours. It is adopted by >> majority >> > >>>> approval, with at least 3 PMC affirmative votes. >> > >>>> >> > >>>> Thanks, >> > >>>> Danny >> > >>>> >> > >>>> [1] >> > >>>> >> > >>> >> > >> >> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353148 >> > >>>> [2] >> > >>>> >> > >>> >> > >> >> > >> https://dist.apache.org/repos/dist/dev/flink/flink-connector-cassandra-3.2.0-rc1 >> > >>>> [3] https://dist.apache.org/repos/dist/release/flink/KEYS >> > >>>> [4] >> > >>>> >> > https://repository.apache.org/content/repositories/orgapacheflink-1722 >> > >>>> [5] >> > >>>> >> > >>> >> > >> >> > >> https://github.com/apache/flink-connector-cassandra/releases/tag/v3.2.0-rc1 >> > >>>> [6] https://github.com/apache/flink-web/pull/737 >> > >>>> [7] >> > >>>> >> > >>> >> > >> >> > >> https://github.com/apache/flink-connector-cassandra/actions/runs/8784310241 >> > >>> >> > >> >> > >> > >> >
[ANNOUNCE] Apache flink-connector-aws 4.3.0 released
The Apache Flink community is very happy to announce the release of Apache flink-connector-aws 4.3.0 for Flink 1.18 and 1.19. Apache Flink® is an open-source stream processing framework for distributed, high-performing, always-available, and accurate data streaming applications. The release is available for download at: https://flink.apache.org/downloads.html The full release notes are available in Jira: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353793 We would like to thank all contributors of the Apache Flink community who made this release possible! Regards, Danny Cranmer
[RESULT][VOTE] flink-connector-aws 4.3.0, release candidate #2
I'm happy to announce that we have unanimously approved this release. There are 7 approving votes, 3 of which are binding: * Hang Ruan * Ahmed Hamdy * Aleksandr Pilipenko * Leonard Xu (binding) * Zhongqiang Gong * Rui Fan (binding) * Weijie Guo (binding) There are no disapproving votes. Thanks, Danny
Re: [VOTE] Release flink-connector-aws v4.3.0, release candidate #2
Thanks all, this vote is now closed, I will announce the results on a separate thread. On Fri, Jun 7, 2024 at 4:58 AM weijie guo wrote: > Thanks Danny! > > +1(binding) > > - Verified signatures and hashsums > - Build from source > - Checked release tag > - Reviewed the flink-web PR > - Checked the CI build. > > Best regards, > > Weijie > > > Rui Fan <1996fan...@gmail.com> 于2024年6月7日周五 11:00写道： > > > Thanks Danny for the hard work! > > > > +1(binding) > > > > - Verified signatures > > - Verified sha512 (hashsums) > > - The source archives do not contain any binaries > > - Build the source with Maven 3 and java8 (Checked the license as well) > > - Checked Github release tag > > - Reviewed the flink-web PR > > > > Best, > > Rui > > > > On Fri, May 31, 2024 at 11:47 AM gongzhongqiang < > gongzhongqi...@apache.org > > > > > wrote: > > > > > +1 (non-binding) > > > > > > - Validated the checksum hash and signature. > > > - No binaries exist in the source archive. > > > - Built the source with JDK 8 succeed. > > > - Verified the flink-web PR. > > > - Ensured the JAR is built by JDK 8. > > > > > > Best, > > > Zhongqiang Gong > > > > > > Danny Cranmer 于2024年4月19日周五 18:08写道： > > > > > > > Hi everyone, > > > > > > > > Please review and vote on release candidate #2 for > flink-connector-aws > > > > v4.3.0, as follows: > > > > [ ] +1, Approve the release > > > > [ ] -1, Do not approve the release (please provide specific comments) > > > > > > > > This version supports Flink 1.18 and 1.19. > > > > > > > > The complete staging area is available for your review, which > includes: > > > > * JIRA release notes [1], > > > > * the official Apache source release to be deployed to > dist.apache.org > > > > [2], > > > > which are signed with the key with fingerprint 125FD8DB [3], > > > > * all artifacts to be deployed to the Maven Central Repository [4], > > > > * source code tag v4.3.0-rc2 [5], > > > > * website pull request listing the new release [6]. > > > > * CI build of the tag [7]. > > > > > > > > The vote will be open for at least 72 hours. It is adopted by > majority > > > > approval, with at least 3 PMC affirmative votes. > > > > > > > > Thanks, > > > > Release Manager > > > > > > > > [1] > > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353793 > > > > [2] > > > > > > > > > > https://dist.apache.org/repos/dist/dev/flink/flink-connector-aws-4.3.0-rc2 > > > > [3] https://dist.apache.org/repos/dist/release/flink/KEYS > > > > [4] > > > > > > https://repository.apache.org/content/repositories/orgapacheflink-1721/ > > > > [5] > > > https://github.com/apache/flink-connector-aws/releases/tag/v4.3.0-rc2 > > > > [6] https://github.com/apache/flink-web/pull/733 > > > > [7] > > > https://github.com/apache/flink-connector-aws/actions/runs/8751694197 > > > > > > > > > >
[ANNOUNCE] Apache flink-connector-gcp-pubsub 3.1.0 released
The Apache Flink community is very happy to announce the release of Apache flink-connector-gcp-pubsub 3.1.0 for Flink 1.18 and 1.19. Apache Flink® is an open-source stream processing framework for distributed, high-performing, always-available, and accurate data streaming applications. The release is available for download at: https://flink.apache.org/downloads.html The full release notes are available in Jira: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353813 We would like to thank all contributors of the Apache Flink community who made this release possible! Regards, Danny
[RESULT][VOTE] flink-connector-gcp-pubsub 3.1.0, release candidate #1
I'm happy to announce that we have unanimously approved this release. There are 5 approving votes, 3 of which are binding: * Ahmed Hamdy * Hang Ruan * Leonard Xu (binding) * Rui Fan (binding) * Danny Cranmer (binding) There are no disapproving votes. Thanks everyone!
Re: [VOTE] Release flink-connector-gcp-pubsub v3.1.0, release candidate #1
This vote is now closed, I will announce the results on a separate thread. Thanks all. On Fri, Jun 7, 2024 at 10:10 AM Danny Cranmer wrote: > +1 (binding) > > - Release notes look good > - Source archive checksum and signature is correct > - Binary checksum and signature is correct > - Contents of Maven repo looks good > - Verified there are no binaries in the source archive > - Builds from source, tests pass using Java 8 > - CI run passed > - Tag exists in repo > - NOTICE and LICENSE files present and correct > > Thanks, > Danny > > On Fri, Jun 7, 2024 at 4:43 AM Rui Fan <1996fan...@gmail.com> wrote: > >> Thanks Danny for the hard work! >> >> +1(binding) >> >> - Verified signatures >> - Verified sha512 (hashsums) >> - The source archives do not contain any binaries >> - Build the source with Maven 3 and java8 (Checked the license as well) >> - Checked Github release tag >> - Reviewed the flink-web PR >> >> Best, >> Rui >> >> On Wed, May 22, 2024 at 8:07 PM Leonard Xu wrote: >> >> > >> > +1 (binding) >> > >> > - verified signatures >> > - verified hashsums >> > - built from source code with java 1.8 succeeded >> > - checked Github release tag >> > - checked release notes >> > - reviewed the web PR >> > >> > Best, >> > Leonard >> > >> > > 2024年4月21日 下午9:52，Hang Ruan 写道： >> > > >> > > +1 (non-binding) >> > > >> > > - Validated checksum hash >> > > - Verified signature >> > > - Verified that no binaries exist in the source archive >> > > - Build the source with Maven and jdk8 >> > > - Verified web PR >> > > - Check that the jar is built by jdk8 >> > > >> > > Best, >> > > Hang >> > > >> > > Ahmed Hamdy 于2024年4月18日周四 20:01写道： >> > > >> > >> Hi Danny, >> > >> +1 (non-binding) >> > >> >> > >> - verified hashes and checksums >> > >> - verified signature >> > >> - verified source contains no binaries >> > >> - tag exists in github >> > >> - reviewed web PR >> > >> >> > >> Best Regards >> > >> Ahmed Hamdy >> > >> >> > >> >> > >> On Thu, 18 Apr 2024 at 11:32, Danny Cranmer > > >> > >> wrote: >> > >> >> > >>> Hi everyone, >> > >>> >> > >>> Please review and vote on release candidate #1 for >> > >>> flink-connector-gcp-pubsub v3.1.0, as follows: >> > >>> [ ] +1, Approve the release >> > >>> [ ] -1, Do not approve the release (please provide specific >> comments) >> > >>> >> > >>> This release supports Flink 1.18 and 1.19. >> > >>> >> > >>> The complete staging area is available for your review, which >> includes: >> > >>> * JIRA release notes [1], >> > >>> * the official Apache source release to be deployed to >> dist.apache.org >> > >>> [2], >> > >>> which are signed with the key with fingerprint 125FD8DB [3], >> > >>> * all artifacts to be deployed to the Maven Central Repository [4], >> > >>> * source code tag v3.1.0-rc1 [5], >> > >>> * website pull request listing the new release [6]. >> > >>> * CI build of the tag [7]. >> > >>> >> > >>> The vote will be open for at least 72 hours. It is adopted by >> majority >> > >>> approval, with at least 3 PMC affirmative votes. >> > >>> >> > >>> Thanks, >> > >>> Danny >> > >>> >> > >>> [1] >> > >>> >> > >>> >> > >> >> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353813 >> > >>> [2] >> > >>> >> > >>> >> > >> >> > >> https://dist.apache.org/repos/dist/dev/flink/flink-connector-gcp-pubsub-3.1.0-rc1 >> > >>> [3] https://dist.apache.org/repos/dist/release/flink/KEYS >> > >>> [4] >> > >> >> https://repository.apache.org/content/repositories/orgapacheflink-1720 >> > >>> [5] >> > >>> >> > >>> >> > >> >> > >> https://github.com/apache/flink-connector-gcp-pubsub/releases/tag/v3.1.0-rc1 >> > >>> [6] https://github.com/apache/flink-web/pull/736/files >> > >>> [7] >> > >>> >> > >>> >> > >> >> > >> https://github.com/apache/flink-connector-gcp-pubsub/actions/runs/8735952883 >> > >>> >> > >> >> > >> > >> >
Re: [VOTE] Release flink-connector-gcp-pubsub v3.1.0, release candidate #1
+1 (binding) - Release notes look good - Source archive checksum and signature is correct - Binary checksum and signature is correct - Contents of Maven repo looks good - Verified there are no binaries in the source archive - Builds from source, tests pass using Java 8 - CI run passed - Tag exists in repo - NOTICE and LICENSE files present and correct Thanks, Danny On Fri, Jun 7, 2024 at 4:43 AM Rui Fan <1996fan...@gmail.com> wrote: > Thanks Danny for the hard work! > > +1(binding) > > - Verified signatures > - Verified sha512 (hashsums) > - The source archives do not contain any binaries > - Build the source with Maven 3 and java8 (Checked the license as well) > - Checked Github release tag > - Reviewed the flink-web PR > > Best, > Rui > > On Wed, May 22, 2024 at 8:07 PM Leonard Xu wrote: > > > > > +1 (binding) > > > > - verified signatures > > - verified hashsums > > - built from source code with java 1.8 succeeded > > - checked Github release tag > > - checked release notes > > - reviewed the web PR > > > > Best, > > Leonard > > > > > 2024年4月21日 下午9:52，Hang Ruan 写道： > > > > > > +1 (non-binding) > > > > > > - Validated checksum hash > > > - Verified signature > > > - Verified that no binaries exist in the source archive > > > - Build the source with Maven and jdk8 > > > - Verified web PR > > > - Check that the jar is built by jdk8 > > > > > > Best, > > > Hang > > > > > > Ahmed Hamdy 于2024年4月18日周四 20:01写道： > > > > > >> Hi Danny, > > >> +1 (non-binding) > > >> > > >> - verified hashes and checksums > > >> - verified signature > > >> - verified source contains no binaries > > >> - tag exists in github > > >> - reviewed web PR > > >> > > >> Best Regards > > >> Ahmed Hamdy > > >> > > >> > > >> On Thu, 18 Apr 2024 at 11:32, Danny Cranmer > > >> wrote: > > >> > > >>> Hi everyone, > > >>> > > >>> Please review and vote on release candidate #1 for > > >>> flink-connector-gcp-pubsub v3.1.0, as follows: > > >>> [ ] +1, Approve the release > > >>> [ ] -1, Do not approve the release (please provide specific comments) > > >>> > > >>> This release supports Flink 1.18 and 1.19. > > >>> > > >>> The complete staging area is available for your review, which > includes: > > >>> * JIRA release notes [1], > > >>> * the official Apache source release to be deployed to > dist.apache.org > > >>> [2], > > >>> which are signed with the key with fingerprint 125FD8DB [3], > > >>> * all artifacts to be deployed to the Maven Central Repository [4], > > >>> * source code tag v3.1.0-rc1 [5], > > >>> * website pull request listing the new release [6]. > > >>> * CI build of the tag [7]. > > >>> > > >>> The vote will be open for at least 72 hours. It is adopted by > majority > > >>> approval, with at least 3 PMC affirmative votes. > > >>> > > >>> Thanks, > > >>> Danny > > >>> > > >>> [1] > > >>> > > >>> > > >> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353813 > > >>> [2] > > >>> > > >>> > > >> > > > https://dist.apache.org/repos/dist/dev/flink/flink-connector-gcp-pubsub-3.1.0-rc1 > > >>> [3] https://dist.apache.org/repos/dist/release/flink/KEYS > > >>> [4] > > >> > https://repository.apache.org/content/repositories/orgapacheflink-1720 > > >>> [5] > > >>> > > >>> > > >> > > > https://github.com/apache/flink-connector-gcp-pubsub/releases/tag/v3.1.0-rc1 > > >>> [6] https://github.com/apache/flink-web/pull/736/files > > >>> [7] > > >>> > > >>> > > >> > > > https://github.com/apache/flink-connector-gcp-pubsub/actions/runs/8735952883 > > >>> > > >> > > > > >
[ANNOUNCE] Apache flink-connector-mongodb 1.2.0 released
The Apache Flink community is very happy to announce the release of Apache flink-connector-mongodb 1.2.0 for Flink 1.18 and 1.19. Apache Flink® is an open-source stream processing framework for distributed, high-performing, always-available, and accurate data streaming applications. The release is available for download at: https://flink.apache.org/downloads.html The full release notes are available in Jira: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12354192 We would like to thank all contributors of the Apache Flink community who made this release possible! Regards, Danny Cranmer
[RESULT][VOTE] flink-connector-mongodb 1.2.0, release candidate #2
I'm happy to announce that we have unanimously approved this release. There are 6 approving votes, 3 of which are binding: * Ahmed Hamdy * Hang Ruan * Jiabao Sun * Qingsheng Ren (binding) * Leonard Xu (binding) * Danny Cranmer (binding) There are no disapproving votes. Thanks everyone! Danny
Re: [VOTE] Release flink-connector-mongodb v1.2.0, release candidate #2
This vote is now closed, I will announce the results in a new threaad On Thu, Jun 6, 2024 at 10:43 AM Danny Cranmer wrote: > +1 (binding) > > - Release notes look good > - Source archive checksum and signature is correct > - Binary checksum and signature is correct > - Contents of Maven repo looks good > - Verified there are no binaries in the source archive > - Builds from source, tests pass using Java 8 > - CI run passed > - Tag exists in repo > - NOTICE and LICENSE files present and correct > > Thanks, > Danny > > On Wed, May 22, 2024 at 1:29 PM Leonard Xu wrote: > >> +1 (binding) >> >> - verified signatures >> - verified hashsums >> - built from source code with java 1.8 succeeded >> - checked Github release tag >> - checked release notes >> - reviewed the web PR >> >> Best, >> Leonard >> >> > 2024年5月22日 下午4:16，Qingsheng Ren 写道： >> > >> > +1 (binding) >> > >> > - Verified checksum and signature >> > - Built from source with Java 8 >> > - Verified source release contains no binaries >> > - Verified tag exists on GitHub >> > - Verified JARs on Maven repo is built by Java 8 >> > - Reviewed web PR >> > >> > Thanks for the awesome work, Danny! >> > >> > Best, >> > Qingsheng >> > >> > On Mon, May 20, 2024 at 2:53 PM Jiabao Sun >> wrote: >> >> >> >> We need more votes for this release. >> >> Much appreciated for helping with this release verification. >> >> >> >> Best, >> >> Jiabao >> >> >> >> Jiabao Sun 于2024年4月21日周日 21:35写道： >> >> >> >>> +1 (non-binding) >> >>> >> >>> - Validated checksum hash >> >>> - Verified signature >> >>> - Tag is present >> >>> - Build successful with jdk8, jdk11 and jdk17 >> >>> - Checked the dist jar was built by jdk8 >> >>> - Reviewed web PR >> >>> Best, >> >>> Jiabao >> >>> >> >>> Hang Ruan 于2024年4月21日周日 21:33写道： >> >>> >> >>>> +1 (non-binding) >> >>>> >> >>>> - Validated checksum hash >> >>>> - Verified signature >> >>>> - Verified that no binaries exist in the source archive >> >>>> - Build the source with Maven and jdk8 >> >>>> - Verified web PR >> >>>> - Check that the jar is built by jdk8 >> >>>> >> >>>> Best, >> >>>> Hang >> >>>> >> >>>> Ahmed Hamdy 于2024年4月18日周四 21:40写道： >> >>>> >> >>>>> +1 (non-binding) >> >>>>> >> >>>>> - verified hashes and checksums >> >>>>> - verified signature >> >>>>> - verified source contains no binaries >> >>>>> - tag exists in github >> >>>>> - reviewed web PR >> >>>>> >> >>>>> >> >>>>> Best Regards >> >>>>> Ahmed Hamdy >> >>>>> >> >>>>> >> >>>>> On Thu, 18 Apr 2024 at 11:21, Danny Cranmer < >> dannycran...@apache.org> >> >>>>> wrote: >> >>>>> >> >>>>>> Hi everyone, >> >>>>>> >> >>>>>> Please review and vote on the release candidate #2 for v1.2.0, as >> >>>>> follows: >> >>>>>> [ ] +1, Approve the release >> >>>>>> [ ] -1, Do not approve the release (please provide specific >> comments) >> >>>>>> >> >>>>>> This release supports Flink 1.18 and 1.19. >> >>>>>> >> >>>>>> The complete staging area is available for your review, which >> >>>> includes: >> >>>>>> * JIRA release notes [1], >> >>>>>> * the official Apache source release to be deployed to >> >>>> dist.apache.org >> >>>>>> [2], >> >>>>>> which are signed with the key with fingerprint 125FD8DB [3], >> >>>>>> * all artifacts to be deployed to the Maven Central Repository [4], >> >>>>>> * source code tag v1.2.0-rc2 [5], >> >>>>>> * website pull request listing the new release [6]. >> >>>>>> * CI build of tag [7]. >> >>>>>> >> >>>>>> The vote will be open for at least 72 hours. It is adopted by >> majority >> >>>>>> approval, with at least 3 PMC affirmative votes. >> >>>>>> >> >>>>>> Thanks, >> >>>>>> Danny >> >>>>>> >> >>>>>> [1] >> >>>>>> >> >>>>>> >> >>>>> >> >>>> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12354192 >> >>>>>> [2] >> >>>>>> >> >>>>>> >> >>>>> >> >>>> >> https://dist.apache.org/repos/dist/dev/flink/flink-connector-mongodb-1.2.0-rc2 >> >>>>>> [3] https://dist.apache.org/repos/dist/release/flink/KEYS >> >>>>>> [4] >> >>>>>> >> >>>> >> https://repository.apache.org/content/repositories/orgapacheflink-1719/ >> >>>>>> [5] >> >>>>>> >> >>>>> >> >>>> >> https://github.com/apache/flink-connector-mongodb/releases/tag/v1.2.0-rc2 >> >>>>>> [6] https://github.com/apache/flink-web/pull/735 >> >>>>>> [7] >> >>>>>> >> >>>>> >> >>>> >> https://github.com/apache/flink-connector-mongodb/actions/runs/8735987710 >> >>>>>> >> >>>>> >> >>>> >> >>> >> >>
Re: [VOTE] Release flink-connector-mongodb v1.2.0, release candidate #2
+1 (binding) - Release notes look good - Source archive checksum and signature is correct - Binary checksum and signature is correct - Contents of Maven repo looks good - Verified there are no binaries in the source archive - Builds from source, tests pass using Java 8 - CI run passed - Tag exists in repo - NOTICE and LICENSE files present and correct Thanks, Danny On Wed, May 22, 2024 at 1:29 PM Leonard Xu wrote: > +1 (binding) > > - verified signatures > - verified hashsums > - built from source code with java 1.8 succeeded > - checked Github release tag > - checked release notes > - reviewed the web PR > > Best, > Leonard > > > 2024年5月22日 下午4:16，Qingsheng Ren 写道： > > > > +1 (binding) > > > > - Verified checksum and signature > > - Built from source with Java 8 > > - Verified source release contains no binaries > > - Verified tag exists on GitHub > > - Verified JARs on Maven repo is built by Java 8 > > - Reviewed web PR > > > > Thanks for the awesome work, Danny! > > > > Best, > > Qingsheng > > > > On Mon, May 20, 2024 at 2:53 PM Jiabao Sun wrote: > >> > >> We need more votes for this release. > >> Much appreciated for helping with this release verification. > >> > >> Best, > >> Jiabao > >> > >> Jiabao Sun 于2024年4月21日周日 21:35写道： > >> > >>> +1 (non-binding) > >>> > >>> - Validated checksum hash > >>> - Verified signature > >>> - Tag is present > >>> - Build successful with jdk8, jdk11 and jdk17 > >>> - Checked the dist jar was built by jdk8 > >>> - Reviewed web PR > >>> Best, > >>> Jiabao > >>> > >>> Hang Ruan 于2024年4月21日周日 21:33写道： > >>> > >>>> +1 (non-binding) > >>>> > >>>> - Validated checksum hash > >>>> - Verified signature > >>>> - Verified that no binaries exist in the source archive > >>>> - Build the source with Maven and jdk8 > >>>> - Verified web PR > >>>> - Check that the jar is built by jdk8 > >>>> > >>>> Best, > >>>> Hang > >>>> > >>>> Ahmed Hamdy 于2024年4月18日周四 21:40写道： > >>>> > >>>>> +1 (non-binding) > >>>>> > >>>>> - verified hashes and checksums > >>>>> - verified signature > >>>>> - verified source contains no binaries > >>>>> - tag exists in github > >>>>> - reviewed web PR > >>>>> > >>>>> > >>>>> Best Regards > >>>>> Ahmed Hamdy > >>>>> > >>>>> > >>>>> On Thu, 18 Apr 2024 at 11:21, Danny Cranmer > > >>>>> wrote: > >>>>> > >>>>>> Hi everyone, > >>>>>> > >>>>>> Please review and vote on the release candidate #2 for v1.2.0, as > >>>>> follows: > >>>>>> [ ] +1, Approve the release > >>>>>> [ ] -1, Do not approve the release (please provide specific > comments) > >>>>>> > >>>>>> This release supports Flink 1.18 and 1.19. > >>>>>> > >>>>>> The complete staging area is available for your review, which > >>>> includes: > >>>>>> * JIRA release notes [1], > >>>>>> * the official Apache source release to be deployed to > >>>> dist.apache.org > >>>>>> [2], > >>>>>> which are signed with the key with fingerprint 125FD8DB [3], > >>>>>> * all artifacts to be deployed to the Maven Central Repository [4], > >>>>>> * source code tag v1.2.0-rc2 [5], > >>>>>> * website pull request listing the new release [6]. > >>>>>> * CI build of tag [7]. > >>>>>> > >>>>>> The vote will be open for at least 72 hours. It is adopted by > majority > >>>>>> approval, with at least 3 PMC affirmative votes. > >>>>>> > >>>>>> Thanks, > >>>>>> Danny > >>>>>> > >>>>>> [1] > >>>>>> > >>>>>> > >>>>> > >>>> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12354192 > >>>>>> [2] > >>>>>> > >>>>>> > >>>>> > >>>> > https://dist.apache.org/repos/dist/dev/flink/flink-connector-mongodb-1.2.0-rc2 > >>>>>> [3] https://dist.apache.org/repos/dist/release/flink/KEYS > >>>>>> [4] > >>>>>> > >>>> > https://repository.apache.org/content/repositories/orgapacheflink-1719/ > >>>>>> [5] > >>>>>> > >>>>> > >>>> > https://github.com/apache/flink-connector-mongodb/releases/tag/v1.2.0-rc2 > >>>>>> [6] https://github.com/apache/flink-web/pull/735 > >>>>>> [7] > >>>>>> > >>>>> > >>>> > https://github.com/apache/flink-connector-mongodb/actions/runs/8735987710 > >>>>>> > >>>>> > >>>> > >>> > >
Re: [DISCUSS] Flink 1.19.1 release
Hello, Thanks for opening this discussion Hong. +1 for the 1.19.1 release and +1 for Hong as release manager. I am happy to help out, however I will not be back at my laptop until 5th June onwards. Danny. On Fri, May 24, 2024 at 1:57 PM Hong Liang wrote: > Hi all, > > I would like to discuss creating a new 1.19 patch release (1.19.1). The > last 1.19 release is two months old, and since then, 35 tickets have been > closed [1], of which 7 are blocker/critical [2]. > > There are 5 items open at the moment; 2 of which are not blocking because > they affect previous Flink versions as well [3][4], 3 of which have > approved PRs [5][6][7], and will be merged soon. I propose that we create a > release after [5][6][7] have been closed. > > Please let me know if there are any unresolved issues you'd like to be > included in this release. > > If the community agrees to create this new patch release, I'm happy to > volunteer as the release manager, if another PMC (Danny?) is happy to > assist with the PMC-related release steps! > > Best regards, > Hong > > [1] > https://issues.apache.org/jira/projects/FLINK/versions/12354399 > [2] > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20fixVersion%20%3D%201.19.1%20and%20resolution%20%20!%3D%20Unresolved%20%20and%20priority%20in%20(Blocker%2C%20Critical)%20ORDER%20by%20priority%20%20DESC > [3] https://issues.apache.org/jira/browse/FLINK-34672 > [4] https://issues.apache.org/jira/browse/FLINK-35229 > [5] https://issues.apache.org/jira/browse/FLINK-35358 > [6] https://issues.apache.org/jira/browse/FLINK-34746 > [7] https://issues.apache.org/jira/browse/FLINK-34379 >
Re: [VOTE] FLIP-454: New Apicurio Avro format
+1 (binding) On Tue, May 14, 2024 at 5:26 PM David Radley wrote: > Hi Danny, > Thankyou so much for supporting this flip and for your feedback. I have > copied your points and responded on the discussion thread here: > https://lists.apache.org/thread/rmcc67z35ysk0sv2jhz2wq0mwzjorhjb > > kind regards, David. > > From: Danny Cranmer > Date: Tuesday, 14 May 2024 at 11:58 > To: dev@flink.apache.org > Subject: [EXTERNAL] Re: [VOTE] FLIP-454: New Apicurio Avro format > Hello all, > > Thanks for Driving this David. I am +1 for adding support for the new > format, however have some questions/suggestions on the details. > > 1. Passing around Map additionalInputProperties feels a bit > dirty. It looks like this is mainly for the Kafka connector. This connector > already has a de/serialization schema extension to access record > headers, KafkaRecordDeserializationSchema [1], can we use this instead? > 2. Can you elaborate why we need to change the SchemaCoder interface? Again > I am not a fan of adding these Map parameters > 3. I assume this integration will go into the core Flink repo under > flink-formats [2], and not be a separate repository like the connectors? > > Thanks, > Danny > > [1] > > https://github.com/apache/flink-connector-kafka/blob/main/flink-connector-kafka/src/main/java/org/apache/flink/connector/kafka/source/reader/deserializer/KafkaRecordDeserializationSchema.java > [2] https://github.com/apache/flink/tree/master/flink-formats > > On Sat, May 4, 2024 at 12:46 PM Ahmed Hamdy wrote: > > > +1 (non-binding) > > > > Best Regards > > Ahmed Hamdy > > > > > > On Fri, 3 May 2024 at 15:16, Jeyhun Karimov > wrote: > > > > > +1 (non binding) > > > > > > Thanks for driving this FLIP David. > > > > > > Regards, > > > Jeyhun > > > > > > On Fri, May 3, 2024 at 2:21 PM Mark Nuttall > wrote: > > > > > > > +1, I would also like to see first class support for Avro and > Apicurio > > > > > > > > -- Mark Nuttall, mnutt...@apache.org > > > > Senior Software Engineer, IBM Event Automation > > > > > > > > On 2024/05/02 09:41:09 David Radley wrote: > > > > > Hi everyone, > > > > > > > > > > I'd like to start a vote on the FLIP-454: New Apicurio Avro format > > > > > [1]. The discussion thread is here [2]. > > > > > > > > > > The vote will be open for at least 72 hours unless there is an > > > > > objection > > > > > or > > > > > insufficient votes. > > > > > > > > > > [1] > > > > > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-454%3A+New+Apicurio+Avro+format > > > > > [2] > https://lists.apache.org/thread/wtkl4yn847tdd0wrqm5xgv9wc0cb0kr8 > > > > > > > > > > > > > > > Kind regards, David. > > > > > > > > > > Unless otherwise stated above: > > > > > > > > > > IBM United Kingdom Limited > > > > > Registered in England and Wales with number 741598 > > > > > Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 > > 3AU > > > > > > > > > > > > > > > > Unless otherwise stated above: > > IBM United Kingdom Limited > Registered in England and Wales with number 741598 > Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU >
Re: [DISCUSS] FLIP-XXX Apicurio-avro format
Hello, > I am curious what you mean by abused. I just meant we will end up adding more and more fields to this map over time, and it may be hard to undo. > For Apicurio it can be sent at the start of the payload like Confluent Avro does. Confluent Avro have a magic byte followed by 4 bytes of schema id, at the start of the payload. Apicurio clients and SerDe libraries can be configured to not put the schema id in the headers in which case there is a magic byte followed by an 8 byte schema at the start of the payload. In the deserialization case, we would not need to look at the headers – though the encoding is also in the headers. That sounds like it would fit in better, I assume we cannot just take that approach? Thanks for the discussion. I am not 100% happy with the solution but I cannot offer a better option. I would be interested to hear if others have any suggestions. Playing devil's advocate against myself, we pass maps around to configure connectors so it is not too far away from that. Thanks, Danny On Fri, May 24, 2024 at 2:23 PM David Radley wrote: > Hi Danny, > No worries, thanks for replying. I have working prototype code that is > being reviewed. It needs some cleaning up and more complete testing before > it is ready, but will give you the general idea [1][2] to help to assess > this approach. > > > I am curious what you mean by abused. I guess the approaches are between > generic map, mechanism vs a more particular more granular things being > passed that might be used by another connector. > > Your first question: > “how would this work if the schema ID is not in the Kafka headers, as > hinted to in the FLIP "usually the global ID in a Kafka header"? > > For Apicurio it can be sent at the start of the payload like Confluent > Avro does. Confluent Avro have a magic byte followed by 4 bytes of schema > id, at the start of the payload. Apicurio clients and SerDe libraries can > be configured to not put the schema id in the headers in which case there > is a magic byte followed by an 8 byte schema at the start of the payload. > In the deserialization case, we would not need to look at the headers – > though the encoding is also in the headers. > > Your second question: > “I am wondering if there are any other instances where the source would be > aware of the schema ID and pass it through in this way? > ” > The examples I can think of are: > - Avro can send the complete schema in a header, this is not recommended > but in theory fits the need for a message payload to require something else > to get the structure. > - I see [2] that Apicurio Protobuf uses headers. > - it might be that other message queuing projects like Rabbit MQ would > need this to be able to support Apicurio Avro & protobuf. > > Kind regards, David, > > > > > [1] https://github.com/apache/flink/pull/24715 > [2] https://github.com/apache/flink-connector-kafka/pull/99 > [3] > https://www.apicur.io/registry/docs/apicurio-registry/2.5.x/getting-started/assembly-configuring-kafka-client-serdes.html#registry-serdes-types-json_registry > > > > > > > > > > > > > From: Danny Cranmer > Date: Friday, 24 May 2024 at 12:22 > To: dev@flink.apache.org > Subject: [EXTERNAL] Re: [DISCUSS] FLIP-XXX Apicurio-avro format > Hello, > > Apologies, I am on vacation and have limited access to email. > > I can see the logic here and why you ended up where you did. I can also see > there are other useful metadata fields that we might want to pass through, > which might result in this Map being abused (Kafka Topic, Kinesis Shard, > etc). > > I have a follow up question, how would this work if the schema ID is not in > the Kafka headers, as hinted to in the FLIP "usually the global ID in a > Kafka header"? I am wondering if there are any other instances where the > source would be aware of the schema ID and pass it through in this way? > > Thanks, > Danny > > > > On Wed, May 22, 2024 at 3:43 PM David Radley > wrote: > > > Hi Danny, > > Did you have a chance you have a look at my responses to your feedback? I > > am hoping to keep the momentum going on this one, kind regards, David. > > > > > > From: David Radley > > Date: Tuesday, 14 May 2024 at 17:21 > > To: dev@flink.apache.org > > Subject: [EXTERNAL] [DISCUSS] FLIP-XXX Apicurio-avro format > > Hi Danny, > > > > Thank you very much for the feedback and your support. I have copied your > > feedback from the VOTE thread to this discussion thread, so we can > continue > > our discussions off the VOTE thread. > > > > > > > > Your feedback: > > > > Thanks for Driving this David. I am +1 for ad
Re: [DISCUSS] FLIP-XXX Apicurio-avro format
Hello, Apologies, I am on vacation and have limited access to email. I can see the logic here and why you ended up where you did. I can also see there are other useful metadata fields that we might want to pass through, which might result in this Map being abused (Kafka Topic, Kinesis Shard, etc). I have a follow up question, how would this work if the schema ID is not in the Kafka headers, as hinted to in the FLIP "usually the global ID in a Kafka header"? I am wondering if there are any other instances where the source would be aware of the schema ID and pass it through in this way? Thanks, Danny On Wed, May 22, 2024 at 3:43 PM David Radley wrote: > Hi Danny, > Did you have a chance you have a look at my responses to your feedback? I > am hoping to keep the momentum going on this one, kind regards, David. > > > From: David Radley > Date: Tuesday, 14 May 2024 at 17:21 > To: dev@flink.apache.org > Subject: [EXTERNAL] [DISCUSS] FLIP-XXX Apicurio-avro format > Hi Danny, > > Thank you very much for the feedback and your support. I have copied your > feedback from the VOTE thread to this discussion thread, so we can continue > our discussions off the VOTE thread. > > > > Your feedback: > > Thanks for Driving this David. I am +1 for adding support for the new > > format, however have some questions/suggestions on the details. > > > > 1. Passing around Map additionalInputProperties feels a bit > > dirty. It looks like this is mainly for the Kafka connector. This connector > > already has a de/serialization schema extension to access record > > headers, KafkaRecordDeserializationSchema [1], can we use this instead? > > 2. Can you elaborate why we need to change the SchemaCoder interface? Again > > I am not a fan of adding these Map parameters > > 3. I assume this integration will go into the core Flink repo under > > flink-formats [2], and not be a separate repository like the connectors? > > > > My response: > > Addressing 1. and 2. > > I agree that sending maps around is a bit dirty. If we can see a better > way that would be great. I was looking for a way to pass this kafka header > information in a non-Kafka way - the most obvious way I could think was as > a map. Here are the main considerations I saw, if I have missed anything or > could improve something I would be grateful for any further feedback. > > > > * I see KafkaRecordDeserializationSchema is a Kafka interface that > works at the Kafka record level (so includes the headers). We need a > mechanism to send over the headers from the Kafka record to Flink > * Flink core is not aware of Kafka headers, and I did not want to add > a Kafka dependancy to core flink. > * The formats are stateless so it did not appear to be in fitting with > the Flink architecture to pass through header information to stash in state > in the format waiting for the deserialise to be subsequently called to pick > up the header information. > * We could have used Thread local storage to stash the header content, > but this would be extra state to manage; and this would seem like an > obtrusive change. > * The SchemaCoder deserialise is where Confluent Avro gets the schema > id from the payload, so it can lookup the schema. In line with this > approach it made sense to extend the deserialise so it had the header > contents so the Apicurio Avro format could lookup the schema. > * I did not want to have Apicurio specific logic in the Kafka > connector, if we did we could pull out the appropriate headers and only > send over the schema ids. > * For deserialise, the schema id we are interested in is the one in > the Kafka headers on the message and is for the writer schema (an Avro > format concept) currently used by the confluent-avro format in deserialize. > * For serialise the schema ids need to be obtained from apicurio then > passed through to Kafka. > * For serialise there is existing logic around handling the metadata > which includes passing the headers. But the presence of the metadata would > imply we have a metadata column. Maybe a change to the metadata mechanism > may have allowed to use to pass the headers, but not create a metadata > column; instead I pass through the additional headers in a map to be > appended. > > > > 3. > > Yes this integration will go into the core Flink repo under > > flink-formats and sit next to the confluent-avro format. The Avro format > has the concept of a Registry and drives the confluent-avro format. The > Apicurio Avro format will use the same approach. > > Unless otherwise stated above: > > IBM United Kingdom Limited > Registered in England and Wales with number 741598 > Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU > > Unless otherwise stated above: > > IBM United Kingdom Limited > Registered in England and Wales with number 741598 > Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU >
Re: [VOTE] FLIP-454: New Apicurio Avro format
Hello all, Thanks for Driving this David. I am +1 for adding support for the new format, however have some questions/suggestions on the details. 1. Passing around Map additionalInputProperties feels a bit dirty. It looks like this is mainly for the Kafka connector. This connector already has a de/serialization schema extension to access record headers, KafkaRecordDeserializationSchema [1], can we use this instead? 2. Can you elaborate why we need to change the SchemaCoder interface? Again I am not a fan of adding these Map parameters 3. I assume this integration will go into the core Flink repo under flink-formats [2], and not be a separate repository like the connectors? Thanks, Danny [1] https://github.com/apache/flink-connector-kafka/blob/main/flink-connector-kafka/src/main/java/org/apache/flink/connector/kafka/source/reader/deserializer/KafkaRecordDeserializationSchema.java [2] https://github.com/apache/flink/tree/master/flink-formats On Sat, May 4, 2024 at 12:46 PM Ahmed Hamdy wrote: > +1 (non-binding) > > Best Regards > Ahmed Hamdy > > > On Fri, 3 May 2024 at 15:16, Jeyhun Karimov wrote: > > > +1 (non binding) > > > > Thanks for driving this FLIP David. > > > > Regards, > > Jeyhun > > > > On Fri, May 3, 2024 at 2:21 PM Mark Nuttall wrote: > > > > > +1, I would also like to see first class support for Avro and Apicurio > > > > > > -- Mark Nuttall, mnutt...@apache.org > > > Senior Software Engineer, IBM Event Automation > > > > > > On 2024/05/02 09:41:09 David Radley wrote: > > > > Hi everyone, > > > > > > > > I'd like to start a vote on the FLIP-454: New Apicurio Avro format > > > > [1]. The discussion thread is here [2]. > > > > > > > > The vote will be open for at least 72 hours unless there is an > > > > objection > > > > or > > > > insufficient votes. > > > > > > > > [1] > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-454%3A+New+Apicurio+Avro+format > > > > [2] https://lists.apache.org/thread/wtkl4yn847tdd0wrqm5xgv9wc0cb0kr8 > > > > > > > > > > > > Kind regards, David. > > > > > > > > Unless otherwise stated above: > > > > > > > > IBM United Kingdom Limited > > > > Registered in England and Wales with number 741598 > > > > Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 > 3AU > > > > > > > > > >
Re: [VOTE] FLIP-454: New Apicurio Avro format
Hello all, Thanks for Driving this David. I am +1 for adding support for the new format, however have some questions/suggestions on the details. 1. Passing around Map additionalInputProperties feels a bit dirty. It looks like this is mainly for the Kafka connector. This connector already has a de/serialization schema extension to access record headers, KafkaRecordDeserializationSchema [1], can we use this instead? 2. Can you elaborate why we need to change the SchemaCoder interface? Again I am not a fan of adding these Map parameters 3. I assume this integration will go into the core Flink repo under flink-formats [2], and not be a separate repository like the connectors? Thanks, Danny [1] https://github.com/apache/flink-connector-kafka/blob/main/flink-connector-kafka/src/main/java/org/apache/flink/connector/kafka/source/reader/deserializer/KafkaRecordDeserializationSchema.java [2] https://github.com/apache/flink/tree/master/flink-formats On Sat, May 4, 2024 at 12:46 PM Ahmed Hamdy wrote: > +1 (non-binding) > > Best Regards > Ahmed Hamdy > > > On Fri, 3 May 2024 at 15:16, Jeyhun Karimov wrote: > > > +1 (non binding) > > > > Thanks for driving this FLIP David. > > > > Regards, > > Jeyhun > > > > On Fri, May 3, 2024 at 2:21 PM Mark Nuttall wrote: > > > > > +1, I would also like to see first class support for Avro and Apicurio > > > > > > -- Mark Nuttall, mnutt...@apache.org > > > Senior Software Engineer, IBM Event Automation > > > > > > On 2024/05/02 09:41:09 David Radley wrote: > > > > Hi everyone, > > > > > > > > I'd like to start a vote on the FLIP-454: New Apicurio Avro format > > > > [1]. The discussion thread is here [2]. > > > > > > > > The vote will be open for at least 72 hours unless there is an > > > > objection > > > > or > > > > insufficient votes. > > > > > > > > [1] > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-454%3A+New+Apicurio+Avro+format > > > > [2] https://lists.apache.org/thread/wtkl4yn847tdd0wrqm5xgv9wc0cb0kr8 > > > > > > > > > > > > Kind regards, David. > > > > > > > > Unless otherwise stated above: > > > > > > > > IBM United Kingdom Limited > > > > Registered in England and Wales with number 741598 > > > > Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 > 3AU > > > > > > > > > > -- Best Regards Danny Cranmer
Re: [VOTE] FLIP-451: Introduce timeout configuration to AsyncSink
Thanks for driving this Ahmed. This is a nice improvement to the API: +1 (binding) Thanks, Danny On Mon, May 13, 2024 at 7:58 PM Ahmed Hamdy wrote: > Thanks David, > I have replied to your question in the discussion thread. > Best Regards > Ahmed Hamdy > > > On Mon, 13 May 2024 at 16:21, David Radley > wrote: > > > Hi, > > I raised a question on the discussion thread, around retriable errors, as > > a possible alternative, > > Kind regards, David. > > > > > > From: Aleksandr Pilipenko > > Date: Monday, 13 May 2024 at 16:07 > > To: dev@flink.apache.org > > Subject: [EXTERNAL] Re: [VOTE] FLIP-451: Introduce timeout configuration > > to AsyncSink > > Thanks for driving this! > > > > +1 (non-binding) > > > > Thanks, > > Aleksandr > > > > On Mon, 13 May 2024 at 14:08, > > wrote: > > > > > Thanks Ahmed! > > > > > > +1 non binding > > > On May 13, 2024 at 12:40 +0200, Jeyhun Karimov , > > > wrote: > > > > Thanks for driving this Ahmed. > > > > > > > > +1 (non-binding) > > > > > > > > Regards, > > > > Jeyhun > > > > > > > > On Mon, May 13, 2024 at 12:37 PM Muhammet Orazov > > > > wrote: > > > > > > > > > Thanks Ahmed, +1 (non-binding) > > > > > > > > > > Best, > > > > > Muhammet > > > > > > > > > > On 2024-05-13 09:50, Ahmed Hamdy wrote: > > > > > > > Hi all, > > > > > > > > > > > > > > Thanks for the feedback on the discussion thread[1], I would > like > > > to > > > > > > > start > > > > > > > a vote on FLIP-451[2]: Introduce timeout configuration to > > AsyncSink > > > > > > > > > > > > > > The vote will be open for at least 72 hours unless there is an > > > > > > > objection or > > > > > > > insufficient votes. > > > > > > > > > > > > > > 1- > > https://lists.apache.org/thread/ft7wcw7kyftvww25n5fm4l925tlgdfg0 > > > > > > > 2- > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-451%3A+Introduce+timeout+configuration+to+AsyncSink+API > > > > > > > Best Regards > > > > > > > Ahmed Hamdy > > > > > > > > > > > > Unless otherwise stated above: > > > > IBM United Kingdom Limited > > Registered in England and Wales with number 741598 > > Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU > > >
Re: [DISCUSS] Connector releases for Flink 1.19
Hello, @Sergey Nuyanzin , it looks like opensearch-2.0.0 has been created now, all good. @Hongshun Wang, thanks, since the CDC connectors are not yet released I had omitted them from this task. But happy to include them, thanks for the support. Thanks, Danny On Mon, May 13, 2024 at 3:40 AM Hongshun Wang wrote: > Hello Danny, > Thanks for pushing this forward. I am available to assist with the CDC > connector[1]. > > [1] https://github.com/apache/flink-cdc > > Best > Hongshun > > On Sun, May 12, 2024 at 8:48 PM Sergey Nuyanzin > wrote: > > > I'm in a process of preparation of RC for OpenSearch connector > > > > however it seems I need PMC help: need to create opensearch-2.0.0 on jira > > since as it was proposed in another ML[1] to have 1.x for OpenSearch > > v1 and 2.x for OpenSearch v2 > > > > would be great if someone from PMC could help here > > > > [1] https://lists.apache.org/thread/3w1rnjp5y612xy5k9yv44hy37zm9ph15 > > > > On Wed, Apr 17, 2024 at 12:42 PM Ferenc Csaky > > wrote: > > > > > > Thank you Danny and Sergey for pushing this! > > > > > > I can help with the HBase connector if necessary, will comment the > > > details to the relevant Jira ticket. > > > > > > Best, > > > Ferenc > > > > > > > > > > > > > > > On Wednesday, April 17th, 2024 at 11:17, Danny Cranmer < > > dannycran...@apache.org> wrote: > > > > > > > > > > > > > > > Hello all, > > > > > > > > I have created a parent Jira to cover the releases [1]. I have > > assigned AWS > > > > and MongoDB to myself and OpenSearch to Sergey. Please assign the > > > > relevant issue to yourself as you pick up the tasks. > > > > > > > > Thanks! > > > > > > > > [1] https://issues.apache.org/jira/browse/FLINK-35131 > > > > > > > > On Tue, Apr 16, 2024 at 2:41 PM Muhammet Orazov > > > > mor+fl...@morazow.com.invalid wrote: > > > > > > > > > Thanks Sergey and Danny for clarifying, indeed it > > > > > requires committer to go through the process. > > > > > > > > > > Anyway, please let me know if I can be any help. > > > > > > > > > > Best, > > > > > Muhammet > > > > > > > > > > On 2024-04-16 11:19, Danny Cranmer wrote: > > > > > > > > > > > Hello, > > > > > > > > > > > > I have opened the VOTE thread for the AWS connectors release [1]. > > > > > > > > > > > > > If I'm not mistaking (please correct me if I'm wrong) this > > request is > > > > > > > not > > > > > > > about version update it is about new releases for connectors > > > > > > > > > > > > Yes, correct. If there are any other code changes required then > > help > > > > > > would be appreciated. > > > > > > > > > > > > > Are you going to create an umbrella issue for it? > > > > > > > > > > > > We do not usually create JIRA issues for releases. That being > said > > it > > > > > > sounds like a good idea to have one place to track the status of > > the > > > > > > connector releases and pre-requisite code changes. > > > > > > > > > > > > > I would like to work on this task, thanks for initiating it! > > > > > > > > > > > > The actual release needs to be performed by a committer. However, > > help > > > > > > getting the connectors building against Flink 1.19 and testing > the > > RC > > > > > > is > > > > > > appreciated. > > > > > > > > > > > > Thanks, > > > > > > Danny > > > > > > > > > > > > [1] > > https://lists.apache.org/thread/0nw9smt23crx4gwkf6p1dd4jwvp1g5s0 > > > > > > > > > > > > On Tue, Apr 16, 2024 at 6:34 AM Sergey Nuyanzin > > snuyan...@gmail.com > > > > > > wrote: > > > > > > > > > > > > > Thanks for volunteering Muhammet! > > > > > > > And thanks Danny for starting the activity. > > > > > > > > > > > > > > If I'm not mistaking (please correct me if I'm wrong) > &
Re: flink-connector-kafka weekly CI job failing
Hello, Is there a reason we cannot fix the code rather than disabling the test? If we skip the tests this will likely be missed and cause delays for 1.20 support down the road. Thanks, Danny On Wed, 8 May 2024, 23:35 Robert Young, wrote: > Hi, > > I noticed the flink-connector-kafka weekly CI job is failing: > > https://github.com/apache/flink-connector-kafka/actions/runs/8954222477 > > Looks like flink-connector-kafka main has a compile error against flink > 1.20-SNAPSHOT, I tried locally and get a different compile failure > > KafkaSerializerUpgradeTest.java:[23,45] cannot find symbol > [ERROR] symbol: class TypeSerializerMatchers > [ERROR] location: package org.apache.flink.api.common.typeutils > > Should 1.20-SNAPSHOT be removed from the weekly tests for now? > > Thanks > Rob >
[VOTE] Release flink-connector-kafka v3.2.0, release candidate #1
Hi everyone, Please review and vote on release candidate #1 for flink-connector-kafka v3.2.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) This release supports Flink 1.18 and 1.19. The complete staging area is available for your review, which includes: * JIRA release notes [1], * the official Apache source release to be deployed to dist.apache.org [2], which are signed with the key with fingerprint 125FD8DB [3], * all artifacts to be deployed to the Maven Central Repository [4], * source code tag v3.2.0-rc1 [5], * website pull request listing the new release [6]. * CI build of the tag [7]. The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Thanks, Danny [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12354209 [2] https://dist.apache.org/repos/dist/dev/flink/flink-connector-kafka-3.2.0-rc1 [3] https://dist.apache.org/repos/dist/release/flink/KEYS [4] https://repository.apache.org/content/repositories/orgapacheflink-1723 [5] https://github.com/apache/flink-connector-kafka/releases/tag/v3.2.0-rc1 [6] https://github.com/apache/flink-web/pull/738 [7] https://github.com/apache/flink-connector-kafka
[VOTE] Release flink-connector-cassandra v3.2.0, release candidate #1
Hi everyone, Please review and vote on release candidate #1 for flink-connector-cassandra v3.2.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) This release supports Flink 1.18 and 1.19. The complete staging area is available for your review, which includes: * JIRA release notes [1], * the official Apache source release to be deployed to dist.apache.org [2], which are signed with the key with fingerprint 125FD8DB [3], * all artifacts to be deployed to the Maven Central Repository [4], * source code tag v3.2.0-rc1 [5], * website pull request listing the new release [6]. * CI build of the tag [7]. The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Thanks, Danny [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353148 [2] https://dist.apache.org/repos/dist/dev/flink/flink-connector-cassandra-3.2.0-rc1 [3] https://dist.apache.org/repos/dist/release/flink/KEYS [4] https://repository.apache.org/content/repositories/orgapacheflink-1722 [5] https://github.com/apache/flink-connector-cassandra/releases/tag/v3.2.0-rc1 [6] https://github.com/apache/flink-web/pull/737 [7] https://github.com/apache/flink-connector-cassandra/actions/runs/8784310241
[jira] [Created] (FLINK-35174) Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.1 for Flink RabbitMQ connector
Danny Cranmer created FLINK-35174: - Summary: Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.1 for Flink RabbitMQ connector Key: FLINK-35174 URL: https://issues.apache.org/jira/browse/FLINK-35174 Project: Flink Issue Type: Technical Debt Components: Connectors / AWS Reporter: Danny Cranmer Assignee: Danny Cranmer Fix For: aws-connector-4.3.0 Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.1 for Flink AWS connectors -- This message was sent by Atlassian Jira (v8.20.10#820010)
[VOTE] Release flink-connector-aws v4.3.0, release candidate #2
Hi everyone, Please review and vote on release candidate #2 for flink-connector-aws v4.3.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) This version supports Flink 1.18 and 1.19. The complete staging area is available for your review, which includes: * JIRA release notes [1], * the official Apache source release to be deployed to dist.apache.org [2], which are signed with the key with fingerprint 125FD8DB [3], * all artifacts to be deployed to the Maven Central Repository [4], * source code tag v4.3.0-rc2 [5], * website pull request listing the new release [6]. * CI build of the tag [7]. The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Thanks, Release Manager [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353793 [2] https://dist.apache.org/repos/dist/dev/flink/flink-connector-aws-4.3.0-rc2 [3] https://dist.apache.org/repos/dist/release/flink/KEYS [4] https://repository.apache.org/content/repositories/orgapacheflink-1721/ [5] https://github.com/apache/flink-connector-aws/releases/tag/v4.3.0-rc2 [6] https://github.com/apache/flink-web/pull/733 [7] https://github.com/apache/flink-connector-aws/actions/runs/8751694197
Re: [DISCUSS][QUESTION] Drop jdk 8 support for Flink connector Opensearch
Hey Sergey, Given the circumstances I think it is ok to drop JDK 8 support with the opensearch v2.0.0 connector. However, in parallel we should still support the 1.x line for Flink 1.x series with JDK 8. This would mean two releases: 1/ flink-connector-opensearch v2.0.0 for Flink 1.18/1.19, opensearch 1.x/2.x and JDK 11 2/ flink-connector-opensearch v1.2.0 (or maybe just 1.1.0-1.19) for Flink 1.18/1.19, opensearch 1.x and JDK 8 What do you think? Thanks, Danny On Wed, Apr 17, 2024 at 10:07 AM Sergey Nuyanzin wrote: > Hi everyone > > I'm working on support for Opensearch v2.x for Flink connector > Opensearch[1]. > Unfortunately after several breaking changes (e.g. [2], [3]) on Opensearch > side it is not possible > anymore to use the same connector built for both Opensearch v1 and v2. > This makes us to go in a similar way as for Elasticsearch 6/7 and build a > dedicated Opensearch v2 module. > > However the main pain point here is that Opensearch 2.x is built with jdk11 > and requires jdk11 to build and use Flink connector as well. > Also in README[4] of most of the connectors it is mentioned explicitly that > jdk11 is required to build connectors. > > At the same time it looks like we need to release a connector for > Opensearch v1 with jdk8 and for Opensearch v2 with jdk11. > > The suggestion is to drop support of jdk8 for the Opensearch connector to > make the release/testing for both modules (for Opensearch v1 and Openseach > v2) easier. > > Other opinions are welcome > > [1] https://github.com/apache/flink-connector-opensearch/pull/38 > [2] opensearch-project/OpenSearch#9082 > [3] opensearch-project/OpenSearch#5902 > [4] > > https://github.com/apache/flink-connector-opensearch/blob/main/README.md?plain=1#L18 > > -- > Best regards, > Sergey >
[VOTE] Release flink-connector-gcp-pubsub v3.1.0, release candidate #1
Hi everyone, Please review and vote on release candidate #1 for flink-connector-gcp-pubsub v3.1.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) This release supports Flink 1.18 and 1.19. The complete staging area is available for your review, which includes: * JIRA release notes [1], * the official Apache source release to be deployed to dist.apache.org [2], which are signed with the key with fingerprint 125FD8DB [3], * all artifacts to be deployed to the Maven Central Repository [4], * source code tag v3.1.0-rc1 [5], * website pull request listing the new release [6]. * CI build of the tag [7]. The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Thanks, Danny [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353813 [2] https://dist.apache.org/repos/dist/dev/flink/flink-connector-gcp-pubsub-3.1.0-rc1 [3] https://dist.apache.org/repos/dist/release/flink/KEYS [4] https://repository.apache.org/content/repositories/orgapacheflink-1720 [5] https://github.com/apache/flink-connector-gcp-pubsub/releases/tag/v3.1.0-rc1 [6] https://github.com/apache/flink-web/pull/736/files [7] https://github.com/apache/flink-connector-gcp-pubsub/actions/runs/8735952883
Re: [VOTE] Release flink-connector-jdbc v3.2.0, release candidate #2
Sorry for typos: > Please review and vote on the release candidate #1 for the version 3.2.0, as follows: Should be "release candidate #2" > * source code tag v3.2.0-rc1 [5], Should be "source code tag v3.2.0-rc2" Thanks, Danny On Thu, Apr 18, 2024 at 11:19 AM Danny Cranmer wrote: > Hi everyone, > > Please review and vote on the release candidate #1 for the version 3.2.0, > as follows: > [ ] +1, Approve the release > [ ] -1, Do not approve the release (please provide specific comments) > > This release supports Flink 1.18 and 1.19. > > The complete staging area is available for your review, which includes: > * JIRA release notes [1], > * the official Apache source release to be deployed to dist.apache.org > [2], which are signed with the key with fingerprint 125FD8DB [3], > * all artifacts to be deployed to the Maven Central Repository [4], > * source code tag v3.2.0-rc1 [5], > * website pull request listing the new release [6]. > * CI run of tag [7]. > > The vote will be open for at least 72 hours. It is adopted by majority > approval, with at least 3 PMC affirmative votes. > > Thanks, > Danny > > [1] > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353143 > [2] > https://dist.apache.org/repos/dist/dev/flink/flink-connector-jdbc-3.2.0-rc2 > [3] https://dist.apache.org/repos/dist/release/flink/KEYS > [4] > https://repository.apache.org/content/repositories/orgapacheflink-1718/ > [5] https://github.com/apache/flink-connector-jdbc/releases/tag/v3.2.0-rc2 > [6] https://github.com/apache/flink-web/pull/734 > [7] https://github.com/apache/flink-connector-jdbc/actions/runs/8736019099 >
[VOTE] Release flink-connector-mongodb v1.2.0, release candidate #2
Hi everyone, Please review and vote on the release candidate #2 for v1.2.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) This release supports Flink 1.18 and 1.19. The complete staging area is available for your review, which includes: * JIRA release notes [1], * the official Apache source release to be deployed to dist.apache.org [2], which are signed with the key with fingerprint 125FD8DB [3], * all artifacts to be deployed to the Maven Central Repository [4], * source code tag v1.2.0-rc2 [5], * website pull request listing the new release [6]. * CI build of tag [7]. The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Thanks, Danny [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12354192 [2] https://dist.apache.org/repos/dist/dev/flink/flink-connector-mongodb-1.2.0-rc2 [3] https://dist.apache.org/repos/dist/release/flink/KEYS [4] https://repository.apache.org/content/repositories/orgapacheflink-1719/ [5] https://github.com/apache/flink-connector-mongodb/releases/tag/v1.2.0-rc2 [6] https://github.com/apache/flink-web/pull/735 [7] https://github.com/apache/flink-connector-mongodb/actions/runs/8735987710
[VOTE] Release flink-connector-jdbc v3.2.0, release candidate #2
Hi everyone, Please review and vote on the release candidate #1 for the version 3.2.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) This release supports Flink 1.18 and 1.19. The complete staging area is available for your review, which includes: * JIRA release notes [1], * the official Apache source release to be deployed to dist.apache.org [2], which are signed with the key with fingerprint 125FD8DB [3], * all artifacts to be deployed to the Maven Central Repository [4], * source code tag v3.2.0-rc1 [5], * website pull request listing the new release [6]. * CI run of tag [7]. The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Thanks, Danny [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353143 [2] https://dist.apache.org/repos/dist/dev/flink/flink-connector-jdbc-3.2.0-rc2 [3] https://dist.apache.org/repos/dist/release/flink/KEYS [4] https://repository.apache.org/content/repositories/orgapacheflink-1718/ [5] https://github.com/apache/flink-connector-jdbc/releases/tag/v3.2.0-rc2 [6] https://github.com/apache/flink-web/pull/734 [7] https://github.com/apache/flink-connector-jdbc/actions/runs/8736019099
Re: [VOTE] Release flink-connector-mongodb v1.2.0, release candidate #1
-1 (binding) There is a bug [1] in the connector release utils resulting in the build tools [2] not being copied into the source archive. As a result the source archive fails build due to checkstyle errors. This vote is now closed, I will follow up with an RC2. Thanks, Danny [1] https://issues.apache.org/jira/browse/FLINK-35124 [2] https://github.com/apache/flink-connector-jdbc/tree/main/tools On Wed, Apr 17, 2024 at 2:31 PM Jeyhun Karimov wrote: > Thanks for driving this. > > +1 (non-binding) > > - Validated checksum hash > - Verified signature > - Tag is present > - Reviewed web PR > > Regards, > Jeyhun > > On Wed, Apr 17, 2024 at 3:26 PM gongzhongqiang > wrote: > > > +1 (non-binding) > > > > - Flink website pr reviewed > > - Check source code without binary files > > - Validated checksum hash and signature > > - CI passed with tag v1.2.0-rc1 > > > > Best, > > Zhongqiang Gong > > > > Danny Cranmer 于2024年4月17日周三 18:44写道： > > > > > Hi everyone, > > > > > > Please review and vote on the release candidate #1 for v1.2.0, as > > follows: > > > [ ] +1, Approve the release > > > [ ] -1, Do not approve the release (please provide specific comments) > > > > > > This release supports Flink 1.18 and 1.19. > > > > > > The complete staging area is available for your review, which includes: > > > * JIRA release notes [1], > > > * the official Apache source release to be deployed to dist.apache.org > > > [2], > > > which are signed with the key with fingerprint 125FD8DB [3], > > > * all artifacts to be deployed to the Maven Central Repository [4], > > > * source code tag v1.2.0-rc1 [5], > > > * website pull request listing the new release [6]. > > > * CI build of tag [7]. > > > > > > The vote will be open for at least 72 hours. It is adopted by majority > > > approval, with at least 3 PMC affirmative votes. > > > > > > Thanks, > > > Danny > > > > > > [1] > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12354192 > > > [2] > > > > > > > > > https://dist.apache.org/repos/dist/dev/flink/flink-connector-mongodb-1.2.0-rc1 > > > [3] https://dist.apache.org/repos/dist/release/flink/KEYS > > > [4] > > > > https://repository.apache.org/content/repositories/orgapacheflink-1715/ > > > [5] > > > > > > https://github.com/apache/flink-connector-mongodb/releases/tag/v1.2.0-rc1 > > > [6] https://github.com/apache/flink-web/pull/735 > > > [7] > > > > > > https://github.com/apache/flink-connector-mongodb/actions/runs/8720057880 > > > > > >
Re: [VOTE] Release flink-connector-jdbc v3.2.0, release candidate #1
-1 (binding) There is a bug [1] in the connector release utils resulting in the build tools [2] not being copied into the source archive. As a result the source archive fails build due to checkstyle errors. This vote is now closed, I will follow up with an RC2. Thanks, Danny [1] https://issues.apache.org/jira/browse/FLINK-35124 [2] https://github.com/apache/flink-connector-jdbc/tree/main/tools On Thu, Apr 18, 2024 at 4:02 AM Yuepeng Pan wrote: > +1 (non-binding) > > - Checked source-build for source code tag v3.2.0-rc1 > - Did test for some examples with mysql 5.8. > - Checked release note page. > > > Thanks for driving it! > > > Best, > Yuepeng Pan > > > > > At 2024-04-17 18:02:06, "Danny Cranmer" wrote: > >Hi everyone, > > > >Please review and vote on the release candidate #1 for the version 3.2.0, > >as follows: > >[ ] +1, Approve the release > >[ ] -1, Do not approve the release (please provide specific comments) > > > >This release supports Flink 1.18 and 1.19. > > > >The complete staging area is available for your review, which includes: > >* JIRA release notes [1], > >* the official Apache source release to be deployed to dist.apache.org > [2], > >which are signed with the key with fingerprint 125FD8DB [3], > >* all artifacts to be deployed to the Maven Central Repository [4], > >* source code tag v3.2.0-rc1 [5], > >* website pull request listing the new release [6]. > >* CI run of tag [7]. > > > >The vote will be open for at least 72 hours. It is adopted by majority > >approval, with at least 3 PMC affirmative votes. > > > >Thanks, > >Danny > > > >[1] > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353143 > >[2] > > > https://dist.apache.org/repos/dist/dev/flink/flink-connector-jdbc-3.2.0-rc1 > >[3] https://dist.apache.org/repos/dist/release/flink/KEYS > >[4] > https://repository.apache.org/content/repositories/orgapacheflink-1714/ > >[5] > https://github.com/apache/flink-connector-jdbc/releases/tag/v3.2.0-rc1 > >[6] https://github.com/apache/flink-web/pull/734 > >[7] > https://github.com/apache/flink-connector-jdbc/actions/runs/8719743185 >
Re: [VOTE] Release flink-connector-aws v4.3.0, release candidate #1
Hey, Thanks for root causing this. I agree this needs to be fixed. -1 binding Thanks, Danny On Wed, 17 Apr 2024, 15:43 Aleksandr Pilipenko, wrote: > Hi Danny, > > There is a blocker bug reported in Kinesis connector [1] > We should pause the release until it is resolved. > > [1] > https://issues.apache.org/jira/browse/FLINK-35115 > > Thanks, > Aleksandr >
[VOTE] Release flink-connector-mongodb v1.2.0, release candidate #1
Hi everyone, Please review and vote on the release candidate #1 for v1.2.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) This release supports Flink 1.18 and 1.19. The complete staging area is available for your review, which includes: * JIRA release notes [1], * the official Apache source release to be deployed to dist.apache.org [2], which are signed with the key with fingerprint 125FD8DB [3], * all artifacts to be deployed to the Maven Central Repository [4], * source code tag v1.2.0-rc1 [5], * website pull request listing the new release [6]. * CI build of tag [7]. The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Thanks, Danny [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12354192 [2] https://dist.apache.org/repos/dist/dev/flink/flink-connector-mongodb-1.2.0-rc1 [3] https://dist.apache.org/repos/dist/release/flink/KEYS [4] https://repository.apache.org/content/repositories/orgapacheflink-1715/ [5] https://github.com/apache/flink-connector-mongodb/releases/tag/v1.2.0-rc1 [6] https://github.com/apache/flink-web/pull/735 [7] https://github.com/apache/flink-connector-mongodb/actions/runs/8720057880
[jira] [Created] (FLINK-35141) Release flink-connector-pulsar vX.X.X for Flink 1.19
Danny Cranmer created FLINK-35141: - Summary: Release flink-connector-pulsar vX.X.X for Flink 1.19 Key: FLINK-35141 URL: https://issues.apache.org/jira/browse/FLINK-35141 Project: Flink Issue Type: Sub-task Components: Connectors / Pulsar Reporter: Danny Cranmer https://github.com/apache/flink-connector-pulsar -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-35134) Release flink-connector-elasticsearch vX.X.X for Flink 1.18/1.19
Danny Cranmer created FLINK-35134: - Summary: Release flink-connector-elasticsearch vX.X.X for Flink 1.18/1.19 Key: FLINK-35134 URL: https://issues.apache.org/jira/browse/FLINK-35134 Project: Flink Issue Type: Sub-task Components: Connectors / ElasticSearch Reporter: Danny Cranmer https://github.com/apache/flink-connector-elasticsearch -- This message was sent by Atlassian Jira (v8.20.10#820010)
[VOTE] Release flink-connector-jdbc v3.2.0, release candidate #1
Hi everyone, Please review and vote on the release candidate #1 for the version 3.2.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) This release supports Flink 1.18 and 1.19. The complete staging area is available for your review, which includes: * JIRA release notes [1], * the official Apache source release to be deployed to dist.apache.org [2], which are signed with the key with fingerprint 125FD8DB [3], * all artifacts to be deployed to the Maven Central Repository [4], * source code tag v3.2.0-rc1 [5], * website pull request listing the new release [6]. * CI run of tag [7]. The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Thanks, Danny [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353143 [2] https://dist.apache.org/repos/dist/dev/flink/flink-connector-jdbc-3.2.0-rc1 [3] https://dist.apache.org/repos/dist/release/flink/KEYS [4] https://repository.apache.org/content/repositories/orgapacheflink-1714/ [5] https://github.com/apache/flink-connector-jdbc/releases/tag/v3.2.0-rc1 [6] https://github.com/apache/flink-web/pull/734 [7] https://github.com/apache/flink-connector-jdbc/actions/runs/8719743185
[jira] [Created] (FLINK-35136) Release flink-connector-hbase vX.X.X for Flink 1.19
Danny Cranmer created FLINK-35136: - Summary: Release flink-connector-hbase vX.X.X for Flink 1.19 Key: FLINK-35136 URL: https://issues.apache.org/jira/browse/FLINK-35136 Project: Flink Issue Type: Sub-task Components: Connectors / HBase Reporter: Danny Cranmer -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-35142) Release flink-connector-rabbitmq vX.X.X for Flink 1.19
Danny Cranmer created FLINK-35142: - Summary: Release flink-connector-rabbitmq vX.X.X for Flink 1.19 Key: FLINK-35142 URL: https://issues.apache.org/jira/browse/FLINK-35142 Project: Flink Issue Type: Sub-task Components: Connectors/ RabbitMQ Reporter: Danny Cranmer https://github.com/apache/flink-connector-rabbitmq -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-35140) Release flink-connector-opensearch vX.X.X for Flink 1.19
Danny Cranmer created FLINK-35140: - Summary: Release flink-connector-opensearch vX.X.X for Flink 1.19 Key: FLINK-35140 URL: https://issues.apache.org/jira/browse/FLINK-35140 Project: Flink Issue Type: Sub-task Components: Connectors / Opensearch Reporter: Danny Cranmer -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [DISCUSS] Connector releases for Flink 1.19
Hello all, I have created a parent Jira to cover the releases [1]. I have assigned AWS and MongoDB to myself and OpenSearch to Sergey. Please assign the relevant issue to yourself as you pick up the tasks. Thanks! [1] https://issues.apache.org/jira/browse/FLINK-35131 On Tue, Apr 16, 2024 at 2:41 PM Muhammet Orazov wrote: > Thanks Sergey and Danny for clarifying, indeed it > requires committer to go through the process. > > Anyway, please let me know if I can be any help. > > Best, > Muhammet > > > On 2024-04-16 11:19, Danny Cranmer wrote: > > Hello, > > > > I have opened the VOTE thread for the AWS connectors release [1]. > > > >> If I'm not mistaking (please correct me if I'm wrong) this request is > >> not > > about version update it is about new releases for connectors > > > > Yes, correct. If there are any other code changes required then help > > would be appreciated. > > > >> Are you going to create an umbrella issue for it? > > > > We do not usually create JIRA issues for releases. That being said it > > sounds like a good idea to have one place to track the status of the > > connector releases and pre-requisite code changes. > > > >> I would like to work on this task, thanks for initiating it! > > > > The actual release needs to be performed by a committer. However, help > > getting the connectors building against Flink 1.19 and testing the RC > > is > > appreciated. > > > > Thanks, > > Danny > > > > [1] https://lists.apache.org/thread/0nw9smt23crx4gwkf6p1dd4jwvp1g5s0 > > > > > > > > On Tue, Apr 16, 2024 at 6:34 AM Sergey Nuyanzin > > wrote: > > > >> Thanks for volunteering Muhammet! > >> And thanks Danny for starting the activity. > >> > >> If I'm not mistaking (please correct me if I'm wrong) > >> > >> this request is not about version update it is about new releases for > >> connectors > >> btw for jdbc connector support of 1.19 and 1.20-SNAPSHOT is already > >> done > >> > >> I would volunteer for Opensearch connector since currently I'm working > >> on > >> support of Opensearch v2 > >> and I think it would make sense to have a release after it is done > >> > >> On Tue, Apr 16, 2024 at 4:29 AM Muhammet Orazov > >> wrote: > >> > >>> Hello Danny, > >>> > >>> I would like to work on this task, thanks for initiating it! > >>> > >>> I could update the versions on JDBC and Pulsar connectors. > >>> > >>> Are you going to create an umbrella issue for it? > >>> > >>> Best, > >>> Muhammet > >>> > >>> On 2024-04-15 13:44, Danny Cranmer wrote: > >>> > Hello all, > >>> > > >>> > Flink 1.19 was released on 2024-03-18 [1] and the connectors have not > >>> > yet > >>> > caught up. I propose we start releasing the connectors with support > for > >>> > Flink 1.19 as per the connector support guidelines [2]. > >>> > > >>> > I will make a start on flink-connector-aws, then pickup others in the > >>> > coming days. Please respond to the thread if you are/want to work on > a > >>> > particular connector to avoid duplicate work. > >>> > > >>> > Thanks, > >>> > Danny > >>> > > >>> > [1] > >>> > > >>> > https://flink.apache.org/2024/03/18/announcing-the-release-of-apache-flink-1.19/ > >>> > [2] > >>> > > >>> > https://cwiki.apache.org/confluence/display/FLINK/Externalized+Connector+development#ExternalizedConnectordevelopment-Flinkcompatibility > >>> > [3] https://github.com/apache/flink-connector-aws > >>> > >> > >> > >> -- > >> Best regards, > >> Sergey > >> >
[jira] [Created] (FLINK-35133) Release flink-connector-cassandra v4.3.0 for Flink 1.18/1.19
Danny Cranmer created FLINK-35133: - Summary: Release flink-connector-cassandra v4.3.0 for Flink 1.18/1.19 Key: FLINK-35133 URL: https://issues.apache.org/jira/browse/FLINK-35133 Project: Flink Issue Type: Sub-task Reporter: Danny Cranmer https://github.com/apache/flink-connector-cassandra -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-35139) Release flink-connector-mongodb vX.X.X for Flink 1.19
Danny Cranmer created FLINK-35139: - Summary: Release flink-connector-mongodb vX.X.X for Flink 1.19 Key: FLINK-35139 URL: https://issues.apache.org/jira/browse/FLINK-35139 Project: Flink Issue Type: Sub-task Components: Connectors / MongoDB Reporter: Danny Cranmer https://github.com/apache/flink-connector-mongodb -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-35138) Release flink-connector-kafka vX.X.X for Flink 1.19
Danny Cranmer created FLINK-35138: - Summary: Release flink-connector-kafka vX.X.X for Flink 1.19 Key: FLINK-35138 URL: https://issues.apache.org/jira/browse/FLINK-35138 Project: Flink Issue Type: Sub-task Reporter: Danny Cranmer https://github.com/apache/flink-connector-kafka -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-35137) Release flink-connector-jdbc vX.X.X for Flink 1.19
Danny Cranmer created FLINK-35137: - Summary: Release flink-connector-jdbc vX.X.X for Flink 1.19 Key: FLINK-35137 URL: https://issues.apache.org/jira/browse/FLINK-35137 Project: Flink Issue Type: Sub-task Reporter: Danny Cranmer https://github.com/apache/flink-connector-jdbc -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-35135) Release flink-connector-gcp-pubsub vX.X.X for Flink 1.18/1.19
Danny Cranmer created FLINK-35135: - Summary: Release flink-connector-gcp-pubsub vX.X.X for Flink 1.18/1.19 Key: FLINK-35135 URL: https://issues.apache.org/jira/browse/FLINK-35135 Project: Flink Issue Type: Sub-task Reporter: Danny Cranmer https://github.com/apache/flink-connector-gcp-pubsub -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-35132) Release flink-connector-aws v4.3.0 for Flink 1.18/1.19
Danny Cranmer created FLINK-35132: - Summary: Release flink-connector-aws v4.3.0 for Flink 1.18/1.19 Key: FLINK-35132 URL: https://issues.apache.org/jira/browse/FLINK-35132 Project: Flink Issue Type: Sub-task Reporter: Danny Cranmer Fix For: aws-connector-4.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-35131) Support and Release Connectors for Flink 1.19
Danny Cranmer created FLINK-35131: - Summary: Support and Release Connectors for Flink 1.19 Key: FLINK-35131 URL: https://issues.apache.org/jira/browse/FLINK-35131 Project: Flink Issue Type: Improvement Reporter: Danny Cranmer This is the parent task to contain connector support and releases for Flink 1.19. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [DISCUSS] Connector releases for Flink 1.19
Hello, I have opened the VOTE thread for the AWS connectors release [1]. > If I'm not mistaking (please correct me if I'm wrong) this request is not about version update it is about new releases for connectors Yes, correct. If there are any other code changes required then help would be appreciated. > Are you going to create an umbrella issue for it? We do not usually create JIRA issues for releases. That being said it sounds like a good idea to have one place to track the status of the connector releases and pre-requisite code changes. > I would like to work on this task, thanks for initiating it! The actual release needs to be performed by a committer. However, help getting the connectors building against Flink 1.19 and testing the RC is appreciated. Thanks, Danny [1] https://lists.apache.org/thread/0nw9smt23crx4gwkf6p1dd4jwvp1g5s0 On Tue, Apr 16, 2024 at 6:34 AM Sergey Nuyanzin wrote: > Thanks for volunteering Muhammet! > And thanks Danny for starting the activity. > > If I'm not mistaking (please correct me if I'm wrong) > > this request is not about version update it is about new releases for > connectors > btw for jdbc connector support of 1.19 and 1.20-SNAPSHOT is already done > > I would volunteer for Opensearch connector since currently I'm working on > support of Opensearch v2 > and I think it would make sense to have a release after it is done > > On Tue, Apr 16, 2024 at 4:29 AM Muhammet Orazov > wrote: > >> Hello Danny, >> >> I would like to work on this task, thanks for initiating it! >> >> I could update the versions on JDBC and Pulsar connectors. >> >> Are you going to create an umbrella issue for it? >> >> Best, >> Muhammet >> >> On 2024-04-15 13:44, Danny Cranmer wrote: >> > Hello all, >> > >> > Flink 1.19 was released on 2024-03-18 [1] and the connectors have not >> > yet >> > caught up. I propose we start releasing the connectors with support for >> > Flink 1.19 as per the connector support guidelines [2]. >> > >> > I will make a start on flink-connector-aws, then pickup others in the >> > coming days. Please respond to the thread if you are/want to work on a >> > particular connector to avoid duplicate work. >> > >> > Thanks, >> > Danny >> > >> > [1] >> > >> https://flink.apache.org/2024/03/18/announcing-the-release-of-apache-flink-1.19/ >> > [2] >> > >> https://cwiki.apache.org/confluence/display/FLINK/Externalized+Connector+development#ExternalizedConnectordevelopment-Flinkcompatibility >> > [3] https://github.com/apache/flink-connector-aws >> > > > -- > Best regards, > Sergey >
[VOTE] Release flink-connector-aws v4.3.0, release candidate #1
Hi everyone, Please review and vote on the release candidate #1 for flink-connector-aws v4.3.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) This release supports Apache Flink 1.18 and 1.19. The complete staging area is available for your review, which includes: * JIRA release notes [1], * the official Apache source release to be deployed to dist.apache.org [2], which are signed with the key with fingerprint 125FD8DB [3], * all artifacts to be deployed to the Maven Central Repository [4], * source code tag v4.3.0-rc1 [5], * website pull request listing the new release [6]. * CI build of the tag against Flink 1.18.1 and 1.19.0 [7]. The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Thanks, Danny [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353793 [2] https://dist.apache.org/repos/dist/dev/flink/flink-connector-aws-4.3.0-rc1 [3] https://dist.apache.org/repos/dist/release/flink/KEYS [4] https://repository.apache.org/content/repositories/orgapacheflink-1711/ [5] https://github.com/apache/flink-connector-aws/releases/tag/v4.3.0-rc1 [6] https://github.com/apache/flink-web/pull/733 [7] https://github.com/apache/flink-connector-aws/actions/runs/8703830985
[jira] [Created] (FLINK-35124) Connector Release Fails to run Checkstyle
Danny Cranmer created FLINK-35124:
-
Summary: Connector Release Fails to run Checkstyle
Key: FLINK-35124
URL: https://issues.apache.org/jira/browse/FLINK-35124
Project: Flink
Issue Type: Bug
Components: Build System
Reporter: Danny Cranmer
During a release of the AWS connectors the build was failing at the
\{{./tools/releasing/shared/stage_jars.sh}} step due to a checkstyle error.
{code:java}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-checkstyle-plugin:3.1.2:check (validate) on
project flink-connector-aws: Failed during checkstyle execution: Unable to find
suppressions file at location: /tools/maven/suppressions.xml: Could not find
resource '/tools/maven/suppressions.xml'. -> [Help 1] {code}
Looks like it is caused by this
[https://github.com/apache/flink-connector-shared-utils/commit/a75b89ee3f8c9a03e97ead2d0bd9d5b7bb02b51a]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[DISCUSS] Connector releases for Flink 1.19
Hello all, Flink 1.19 was released on 2024-03-18 [1] and the connectors have not yet caught up. I propose we start releasing the connectors with support for Flink 1.19 as per the connector support guidelines [2]. I will make a start on flink-connector-aws, then pickup others in the coming days. Please respond to the thread if you are/want to work on a particular connector to avoid duplicate work. Thanks, Danny [1] https://flink.apache.org/2024/03/18/announcing-the-release-of-apache-flink-1.19/ [2] https://cwiki.apache.org/confluence/display/FLINK/Externalized+Connector+development#ExternalizedConnectordevelopment-Flinkcompatibility [3] https://github.com/apache/flink-connector-aws
Re: [ANNOUNCE] New Apache Flink PMC Member - Jing Ge
Congrats Jing! Best Regards, Danny On Mon, Apr 15, 2024 at 11:51 AM Swapnal Varma wrote: > Congratulations, Jing! > > Best, > Swapnal > > On Mon, 15 Apr 2024, 15:14 Jacky Lau, wrote: > > > Congratulations, Jing! > > > > Best, > > Jacky Lau > > >
Re: [Vote] FLIP-438: Amazon SQS Sink Connector
Thanks for driving this Priya. +1 (binding) Danny. On Sun, Apr 14, 2024 at 12:33 PM Samrat Deb wrote: > +1 (non-binding) > > Bests, > Samrat > > On Sun, 14 Apr 2024 at 3:38 PM, Ahmed Hamdy wrote: > > > Hi Priya > > +1 (non-binding) > > Best Regards > > Ahmed Hamdy > > > > > > On Fri, 12 Apr 2024 at 22:56, Dhingra, Priya > > > wrote: > > > > > Hi devs, > > > > > > > > > > > > Thank you to everyone for the feedback on FLIP-438: Amazon SQS Sink > > > Connector< > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-438%3A+Amazon+SQS+Sink+Connector > > > > > > > > > > > > > > > > I would like to start a vote for it. The vote will be open for at least > > 72 > > > > > > hours unless there is an objection or not enough votes. > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-438%3A+Amazon+SQS+Sink+Connector > > > > > > Regards > > > Priya > > > > > >
Re: [DISCUSS] FLIP-438: Amazon SQS Sink Connector
Thanks for the FLIP Priya. I have seen many custom implementations of SQS sinks, so having an Apache supported connector will be great. I agree on the points about implementation detail in the FLIP. There is still too much code really, we will review that in the PR. The FLIP is mainly to agree we should add this connector, we can leave the implementation details for later. nit: Wrt to versioning, it is actually Flink 1.18 and 1.19 now, since 1.17 is out of support. But since we are using the flink-connector-aws repo we will use the supported version there. > Would it make sense to use here docker based integration testing using Testcontainer +1, we typically use localstack for the Integration tests and hit AWS in the e2e test packages. Having coverage of both will be great. Thanks, Danny On Mon, Apr 15, 2024 at 3:23 AM Muhammet Orazov wrote: > Hey Priya, > > Thanks for the FLIP and driving it! > > One question from my side on test plan: > > > End to end integration tests that hit the real Amazon SQS service. > > These tests will be enabled when credentials are defined. > > Would it make sense to use here docker based integration testing using > Testcontainer[1], for example, with Localstack[2]? Seems like the SQS > service is provided on the free tier. > > [1]: https://java.testcontainers.org/modules/localstack/ > [2]: https://docs.localstack.cloud/user-guide/aws/sqs/ > > On 2024-04-05 18:16, Dhingra, Priya wrote: > > Hi Dev, > > > > I would like to start a discussion about FLIP-438: Amazon SQS Sink > > Connector< > https://cwiki.apache.org/confluence/display/FLINK/FLIP-438%3A+Amazon+SQS+Sink+Connector>. > > > This FLIP is proposing to add support for AWS SQS sink in > > flink-connector-aws repo. > > > > For more details, see FLIP-438. Looking forward to your feedback. > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-438%3A+Amazon+SQS+Sink+Connector > > > > Thanks, > > Priya >
[jira] [Created] (FLINK-35113) Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.1 for Flink AWS connectors
Danny Cranmer created FLINK-35113: - Summary: Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.1 for Flink AWS connectors Key: FLINK-35113 URL: https://issues.apache.org/jira/browse/FLINK-35113 Project: Flink Issue Type: Technical Debt Components: Connectors / Kafka Reporter: Martijn Visser Assignee: Martijn Visser Fix For: kafka-4.0.0, kafka-3.1.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [ANNOUNCE] New Apache Flink Committer - Zakelly Lan
Congrats Zakelly! Danny. On Mon, Apr 15, 2024 at 9:26 AM Xia Sun wrote: > Congratulations Zakelly! > > Best, > Xia > > Leonard Xu 于2024年4月15日周一 16:16写道： > > > Congratulations Zakelly! > > > > > > Best, > > Leonard > > > 2024年4月15日 下午3:56，Samrat Deb 写道： > > > > > > Congratulations Zakelly! > > > > >
Re: [VOTE] FLIP-418: Show data skew score on Flink Dashboard
Thanks for driving thie Emre, +1 (binding) Thanks, Danny. On Mon, Feb 12, 2024 at 9:42 PM Hong Liang wrote: > +1 (binding) > > Thank you for driving this Emre! This is a good step towards better user > experience when diagnosing performance issues with Flink jobs. > > Best, > Hong > > On Wed, Jan 31, 2024 at 3:00 AM Aleksandr Pilipenko > wrote: > > > Thanks for the FLIP! > > > > +1 (non-binding) > > > > Best, > > Aleksandr > > > > On Mon, 29 Jan 2024 at 10:11, Kartoglu, Emre > > > wrote: > > > > > Hello, > > > > > > I'd like to call votes on FLIP-418: Show data skew score on Flink > > > Dashboard. > > > > > > FLIP: > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-418%3A+Show+data+skew+score+on+Flink+Dashboard > > > Discussion: > > > https://lists.apache.org/thread/m5ockoork0h2zr78h77dcrn71rbt35ql > > > > > > Kind regards, > > > Emre > > > > > > > > >
[jira] [Created] (FLINK-34342) Address ListShards Consistency for DDB Streams Source
Danny Cranmer created FLINK-34342: - Summary: Address ListShards Consistency for DDB Streams Source Key: FLINK-34342 URL: https://issues.apache.org/jira/browse/FLINK-34342 Project: Flink Issue Type: Sub-task Components: Connectors / DynamoDB Reporter: Danny Cranmer -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-34341) Implement DDB Streams Table API support
Danny Cranmer created FLINK-34341: - Summary: Implement DDB Streams Table API support Key: FLINK-34341 URL: https://issues.apache.org/jira/browse/FLINK-34341 Project: Flink Issue Type: Sub-task Components: Connectors / Kinesis Reporter: Hong Liang Teoh Implement Table API support for KDS Source. Consider: * Configurations to support. Should have customisation parity with DataStream API * Testing should include both SQL client + Table API via Java -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-34340) Add support for DDB Streams
Danny Cranmer created FLINK-34340:
-
Summary: Add support for DDB Streams
Key: FLINK-34340
URL: https://issues.apache.org/jira/browse/FLINK-34340
Project: Flink
Issue Type: Sub-task
Components: Connectors / DynamoDB
Reporter: Danny Cranmer
In the legacy KDS source we support Amazon DynamoDB streams via an adapter
shim. Both KDS and DDB streams have a similar API.
This task builds upon https://issues.apache.org/jira/browse/FLINK-34339 and
will add a {{DynamoDBStreamsSource}} which will setup a DDB SDK client shim.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-34339) Add connector abstraction layer to remove reliance on AWWS SDK classes
Danny Cranmer created FLINK-34339:
-
Summary: Add connector abstraction layer to remove reliance on
AWWS SDK classes
Key: FLINK-34339
URL: https://issues.apache.org/jira/browse/FLINK-34339
Project: Flink
Issue Type: Sub-task
Reporter: Danny Cranmer
In order to shim DDB streams we need to be able to support the
Stream/Shard/Record etc concepts without tying to a specific implementation.
This will allow us to mimic the KDS/DDB streams support in the old connector by
providing a shim at the AWS SDK client.
# Model {{software.amazon.awssdk.services.kinesis}} classes as native concepts
# Push down any usage of {{software.amazon.awssdk.services.kinesis}} to a KDS
specific class
# Ensure that the bulk of the connector logic is reusable, the top level class
would be implementation specific and shim in the write client factories and
configuration
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[ANNOUNCE] Apache flink-connector-opensearch 1.1.0 released
The Apache Flink community is very happy to announce the release of Apache flink-connector-opensearch 1.1.0. This release supports Apache Flink 1.17 and 1.18. Apache Flink® is an open-source stream processing framework for distributed, high-performing, always-available, and accurate data streaming applications. The release is available for download at: https://flink.apache.org/downloads.html The full release notes are available in Jira: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353141 We would like to thank all contributors of the Apache Flink community who made this release possible! Regards, Danny
[RESULT] [VOTE] flink-connector-opensearch v1.1.0, release candidate #1
I'm happy to announce that we have unanimously approved this release. There are 8 approving votes, 3 of which are binding: * Andriy Redko * Ahmed Hamdy * Ryan Skraba * Sergy Nuyanzin * Martijn Visser (binding) * Danny Cranmer (binding) * Jiabao Sun * Leonard Xu (binding) There are no disapproving votes. Thanks everyone!
Re: [VOTE] Release flink-connector-opensearch v1.1.0, release candidate #1
Thanks all, this vote is now closed, I will announce the results on a separate thread. On Tue, Jan 30, 2024 at 11:33 AM Leonard Xu wrote: > Sorry for late verification, +1(binding) > > - built from source code succeeded > - verified signatures > - verified hashsums > - checked the contents contains jar and pom files in apache repo > - checked Github release tag > - checked release notes > - reviewed the web PR > > > Best, > Leonard > > > 2024年1月13日 下午4:41，Jiabao Sun 写道： > > > > +1 (non-binding) > > > > - Validated hashes > > - Verified signature > > - Verified tags > > - Verified no binaries in the source archive > > - Reviewed web pr and found that there're some conflicts need to be > resolved > > > > Best, > > Jiabao > > > > > >> 2024年1月12日 23:58，Danny Cranmer 写道： > >> > >> Apologies I jumped the gun on this one. We only have 2 binding votes. > >> Reopening the thread. > >> > >> On Fri, Jan 12, 2024 at 3:43 PM Danny Cranmer > >> wrote: > >> > >>> Thanks all, this vote is now closed, I will announce the results on a > >>> separate thread. > >>> > >>> Thanks, > >>> Danny > >>> > >>> On Fri, Jan 12, 2024 at 3:43 PM Danny Cranmer > > >>> wrote: > >>> > >>>> +1 (binding) > >>>> > >>>> - Verified signatures and checksums > >>>> - Reviewed release notes > >>>> - Verified no binaries in the source archive > >>>> - Source builds using Maven > >>>> - Reviewed NOTICE files (I suppose the copyright needs to be 2024 > now!) > >>>> > >>>> Thanks, > >>>> Danny > >>>> > >>>> On Fri, Jan 12, 2024 at 12:56 PM Martijn Visser < > martijnvis...@apache.org> > >>>> wrote: > >>>> > >>>>> One non blocking nit: the version for flink.version in the main POM > is > >>>>> set to 1.17.1. I think this should be 1.17.0 (since that's the lowest > >>>>> possible Flink version that's supported). > >>>>> > >>>>> +1 (binding) > >>>>> > >>>>> - Validated hashes > >>>>> - Verified signature > >>>>> - Verified that no binaries exist in the source archive > >>>>> - Build the source with Maven > >>>>> - Verified licenses > >>>>> - Verified web PRs > >>>>> > >>>>> On Mon, Jan 1, 2024 at 11:57 AM Danny Cranmer < > dannycran...@apache.org> > >>>>> wrote: > >>>>>> > >>>>>> Hey, > >>>>>> > >>>>>> Gordon, apologies for the delay. Yes this is the correct > >>>>> understanding, all > >>>>>> connectors follow a similar pattern. > >>>>>> > >>>>>> Would appreciate some PMC eyes on this release. > >>>>>> > >>>>>> Thanks, > >>>>>> Danny > >>>>>> > >>>>>> On Thu, 23 Nov 2023, 23:28 Tzu-Li (Gordon) Tai, < > tzuli...@apache.org> > >>>>> wrote: > >>>>>> > >>>>>>> Hi Danny, > >>>>>>> > >>>>>>> Thanks for starting a RC for this. > >>>>>>> > >>>>>>> From the looks of the staged POMs for 1.1.0-1.18, the flink > versions > >>>>> for > >>>>>>> Flink dependencies still point to 1.17.1. > >>>>>>> > >>>>>>> My understanding is that this is fine, as those provided scope > >>>>>>> dependencies (e.g. flink-streaming-java) will have their versions > >>>>>>> overwritten by the user POM if they do intend to compile their jobs > >>>>> against > >>>>>>> Flink 1.18.x. > >>>>>>> Can you clarify if this is the correct understanding of how we > >>>>> intend the > >>>>>>> externalized connector artifacts to be published? Related > discussion > >>>>> on > >>>>>>> [1]. > >>>>>>> > >>>>>>> Thanks, > >>>>>>> Gordon > >>>>>>> > >>>>>>>
Re: [VOTE] Release flink-connector-mongodb v1.1.0, release candidate #2
Thanks for driving this Leonard! +1 (binding) - Release notes look ok - Signatures/checksums of source archive are good - Verified there are no binaries in the source archive - Built sources locally successfully - v1.0.0-rc2 tag exists in github - Tag build passing on CI [1] - Contents of Maven dist look complete - Verified signatures/checksums of binary in maven dist is correct - Verified NOTICE files and bundled dependencies Thanks, Danny [1] https://github.com/apache/flink-connector-mongodb/actions/runs/7709467379 On Wed, Jan 31, 2024 at 7:54 AM gongzhongqiang wrote: > +1(non-binding) > > - Signatures and Checksums are good > - No binaries in the source archive > - Tag is present > - Build successful with jdk8 on ubuntu 22.04 > > > Leonard Xu 于2024年1月30日周二 18:23写道： > > > Hey all, > > > > Please help review and vote on the release candidate #2 for the version > > v1.1.0 of the > > Apache Flink MongoDB Connector as follows: > > > > [ ] +1, Approve the release > > [ ] -1, Do not approve the release (please provide specific comments) > > > > The complete staging area is available for your review, which includes: > > * JIRA release notes [1], > > * The official Apache source release to be deployed to dist.apache.org > > [2], > > which are signed with the key with fingerprint > > 5B2F6608732389AEB67331F5B197E1F1108998AD [3], > > * All artifacts to be deployed to the Maven Central Repository [4], > > * Source code tag v1.1.0-rc2 [5], > > * Website pull request listing the new release [6]. > > > > The vote will be open for at least 72 hours. It is adopted by majority > > approval, with at least 3 PMC affirmative votes. > > > > > > Best, > > Leonard > > [1] > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353483 > > [2] > > > https://dist.apache.org/repos/dist/dev/flink/flink-connector-mongodb-1.1.0-rc2/ > > [3] https://dist.apache.org/repos/dist/release/flink/KEYS > > [4] > > https://repository.apache.org/content/repositories/orgapacheflink-1705/ > > [5] https://github.com/apache/flink-connector-mongodb/tree/v1.1.0-rc2 > > [6] https://github.com/apache/flink-web/pull/719 >
Re: [VOTE] Release flink-connector-rabbitmq, v3.0.2 release candidate #1
+1 (binding) - Release notes look good - Signatures match for binary/source archive - Checksums match for binary/source archive - Contents of Maven dist look complete - Verified there are no binaries in the source archive - Built src/tests pass running Maven locally - Tag is present in Github - CI built tag successfully [1] - Approved docs PR Thanks, Danny [1] https://github.com/apache/flink-connector-rabbitmq/actions/runs/7502278783 On Mon, Jan 15, 2024 at 5:01 AM Zhongqiang Gong wrote: > +1 (non-binding) > > - Build with JDK 11 on ubuntu 22.04 > - Gpg sign is correct > - No binary files in the source release > - Reviewed web pr (need to rebase) > > Best, > Zhongqiang Gong > > On 2024/01/12 12:50:53 Martijn Visser wrote: > > Hi everyone, > > Please review and vote on the release candidate #1 for the version > > 3.0.2, as follows: > > [ ] +1, Approve the release > > [ ] -1, Do not approve the release (please provide specific comments) > > > > This version is compatible with Flink 1.16.x, 1.17.x and 1.18.x. > > > > The complete staging area is available for your review, which includes: > > * JIRA release notes [1], > > * the official Apache source release to be deployed to dist.apache.org > > [2], which are signed with the key with fingerprint > > A5F3BCE4CBE993573EC5966A65321B8382B219AF [3], > > * all artifacts to be deployed to the Maven Central Repository [4], > > * source code tag v3.0.2-rc1 [5], > > * website pull request listing the new release [6]. > > > > The vote will be open for at least 72 hours. It is adopted by majority > > approval, with at least 3 PMC affirmative votes. > > > > Thanks, > > Release Manager > > > > [1] > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353145 > > [2] > https://dist.apache.org/repos/dist/dev/flink/flink-connector-rabbitmq-3.0.2-rc1 > > [3] https://dist.apache.org/repos/dist/release/flink/KEYS > > [4] > https://repository.apache.org/content/repositories/orgapacheflink-1697 > > [5] > https://github.com/apache/flink-connector-rabbitmq/releases/tag/v3.0.2-rc1 > > [6] https://github.com/apache/flink-web/pull/712 > > >
Re: [DISCUSS] FLIP-416: Deprecate and remove the RestoreMode#LEGACY
+1 to removing LEGACY mode in Flink 2.0. Thanks for driving. Danny, On Sat, 13 Jan 2024, 08:20 Yanfei Lei, wrote: > Thanks Zakelly for starting this discussion. > > Regardless of whether it is for users or developers, deprecating > RestoreMode#LEGACY makes the semantics clearer and lower maintenance > costs, and Flink 2.0 is a good time point to do this. > So +1 for the overall idea. > > Best, > Yanfei > > Zakelly Lan 于2024年1月11日周四 14:57写道： > > > > > Hi devs, > > > > I'd like to start a discussion on FLIP-416: Deprecate and remove the > > RestoreMode#LEGACY[1]. > > > > The FLIP-193[2] introduced two modes of state file ownership during > > checkpoint restoration: RestoreMode#CLAIM and RestoreMode#NO_CLAIM. The > > LEGACY mode, which was how Flink worked until 1.15, has been superseded > by > > NO_CLAIM as the default mode. The main drawback of LEGACY mode is that > the > > new job relies on artifacts from the old job without cleaning them up, > > leaving users uncertain about when it is safe to delete the old > checkpoint > > directories. This leads to the accumulation of unnecessary checkpoint > files > > that are never cleaned up. Considering cluster availability and job > > maintenance, it is not recommended to use LEGACY mode. Users could choose > > the other two modes to get a clear semantic for the state file ownership. > > > > This FLIP proposes to deprecate the LEGACY mode and remove it completely > in > > the upcoming Flink 2.0. This will make the semantic clear as well as > > eliminate many bugs caused by mode transitions involving LEGACY mode > (e.g. > > FLINK-27114 [3]) and enhance code maintainability. > > > > Looking forward to hearing from you! > > > > [1] https://cwiki.apache.org/confluence/x/ookkEQ > > [2] https://cwiki.apache.org/confluence/x/bIyqCw > > [3] https://issues.apache.org/jira/browse/FLINK-27114 > > > > Best, > > Zakelly >
[ANNOUNCE] Apache flink-connector-gcp-pubsub 3.0.2 released
The Apache Flink community is very happy to announce the release of Apache flink-connector-gcp-pubsub v3.0.2 with support for Flink 1.17 and 1.18. Apache Flink® is an open-source stream processing framework for distributed, high-performing, always-available, and accurate data streaming applications. The release is available for download at: https://flink.apache.org/downloads.html The full release notes are available in Jira: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353144 We would like to thank all contributors of the Apache Flink community who made this release possible! Best Regards Danny Cranmer
[RESULT][VOTE] flink-connector-gcp-pubsub v3.0.2, release candidate #2
I'm happy to announce that we have unanimously approved this release. There are 4 approving votes, 3 of which are binding: * Leonard Xu (binding) * Martijn Visser (binding) * Rui Fan * Danny Cranmer (binding) There are no disapproving votes. Thanks everyone! Danny
Re: [VOTE] Release flink-connector-gcp-pubsub v3.0.2, release candidate #2
Thanks all, This vote is now closed, I will announce the results in a separate thread. Danny. On Fri, Jan 12, 2024 at 4:53 PM Danny Cranmer wrote: > +1 (binding) > > - Verified signatures and checksums > - Reviewed release notes > - Verified contents of Maven repo > - Verified no binaries in the source archive > - Source builds using Maven > - Reviewed NOTICE files (I suppose the copyright needs to be 2024 now!) > - Verified the tag exists in Github > > Thanks, > Danny > > On Sat, Nov 25, 2023 at 5:50 AM Rui Fan <1996fan...@gmail.com> wrote: > >> +1 (non-binding) >> >> - Validated checksum hash >> - Verified signature >> - Verified that no binaries exist in the source archive >> - Build the source with Maven and jdk8 >> - Verified licenses >> - Verified web PRs, left a minor comment >> >> Best, >> Rui >> >> On Fri, Nov 24, 2023 at 10:26 PM Martijn Visser > > >> wrote: >> >> > +1 (binding) >> > >> > - Validated hashes >> > - Verified signature >> > - Verified that no binaries exist in the source archive >> > - Build the source with Maven >> > - Verified licenses >> > - Verified web PRs >> > >> > On Fri, Nov 24, 2023 at 12:38 PM Leonard Xu wrote: >> > > >> > > Thanks Danny for driving this. >> > > >> > > >> > > +1 (binding) >> > > >> > > - built from source code succeeded >> > > - verified signatures >> > > - verified hashsums >> > > - checked the contents contains jar and pom files in apache repo >> > > - checked the lowest supported flink version issue has been fixed >> > > - checked Github release tag >> > > - checked release notes >> > > - reviewed the web PR >> > > >> > > Best, >> > > Leonard >> > > >> > > > 2023年11月15日 下午11:48，Danny Cranmer 写道： >> > > > >> > > > Hi everyone, >> > > > >> > > > Please review and vote on the release candidate #2 for the version >> > 3.0.2 of >> > > > flink-connector-gcp-pubsub, as follows: >> > > > [ ] +1, Approve the release >> > > > [ ] -1, Do not approve the release (please provide specific >> comments) >> > > > >> > > > The complete staging area is available for your review, which >> includes: >> > > > * JIRA release notes [1], >> > > > * the official Apache source release to be deployed to >> dist.apache.org >> > [2], >> > > > which are signed with the key with fingerprint >> > > > 0F79F2AFB2351BC29678544591F9C1EC125FD8DB [3], >> > > > * all artifacts to be deployed to the Maven Central Repository [4], >> > > > * source code tag v3.0.2-rc2 [5], >> > > > * website pull request listing the new release [6]. >> > > > >> > > > The vote will be open for at least 72 hours. It is adopted by >> majority >> > > > approval, with at least 3 PMC affirmative votes. >> > > > >> > > > Thanks, >> > > > Danny >> > > > >> > > > [1] >> > > > >> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353144 >> > > > [2] >> > > > >> > >> https://dist.apache.org/repos/dist/dev/flink/flink-connector-gcp-pubsub-3.0.2-rc2 >> > > > [3] https://dist.apache.org/repos/dist/release/flink/KEYS >> > > > [4] >> > https://repository.apache.org/content/repositories/orgapacheflink-1673/ >> > > > [5] >> > https://github.com/apache/flink-connector-gcp-pubsub/tree/v3.0.2-rc2 >> > > > [6] https://github.com/apache/flink-web/pull/695 >> > > >> > >> >
Re: [VOTE] Release flink-connector-gcp-pubsub v3.0.2, release candidate #2
+1 (binding) - Verified signatures and checksums - Reviewed release notes - Verified contents of Maven repo - Verified no binaries in the source archive - Source builds using Maven - Reviewed NOTICE files (I suppose the copyright needs to be 2024 now!) - Verified the tag exists in Github Thanks, Danny On Sat, Nov 25, 2023 at 5:50 AM Rui Fan <1996fan...@gmail.com> wrote: > +1 (non-binding) > > - Validated checksum hash > - Verified signature > - Verified that no binaries exist in the source archive > - Build the source with Maven and jdk8 > - Verified licenses > - Verified web PRs, left a minor comment > > Best, > Rui > > On Fri, Nov 24, 2023 at 10:26 PM Martijn Visser > wrote: > > > +1 (binding) > > > > - Validated hashes > > - Verified signature > > - Verified that no binaries exist in the source archive > > - Build the source with Maven > > - Verified licenses > > - Verified web PRs > > > > On Fri, Nov 24, 2023 at 12:38 PM Leonard Xu wrote: > > > > > > Thanks Danny for driving this. > > > > > > > > > +1 (binding) > > > > > > - built from source code succeeded > > > - verified signatures > > > - verified hashsums > > > - checked the contents contains jar and pom files in apache repo > > > - checked the lowest supported flink version issue has been fixed > > > - checked Github release tag > > > - checked release notes > > > - reviewed the web PR > > > > > > Best, > > > Leonard > > > > > > > 2023年11月15日 下午11:48，Danny Cranmer 写道： > > > > > > > > Hi everyone, > > > > > > > > Please review and vote on the release candidate #2 for the version > > 3.0.2 of > > > > flink-connector-gcp-pubsub, as follows: > > > > [ ] +1, Approve the release > > > > [ ] -1, Do not approve the release (please provide specific comments) > > > > > > > > The complete staging area is available for your review, which > includes: > > > > * JIRA release notes [1], > > > > * the official Apache source release to be deployed to > dist.apache.org > > [2], > > > > which are signed with the key with fingerprint > > > > 0F79F2AFB2351BC29678544591F9C1EC125FD8DB [3], > > > > * all artifacts to be deployed to the Maven Central Repository [4], > > > > * source code tag v3.0.2-rc2 [5], > > > > * website pull request listing the new release [6]. > > > > > > > > The vote will be open for at least 72 hours. It is adopted by > majority > > > > approval, with at least 3 PMC affirmative votes. > > > > > > > > Thanks, > > > > Danny > > > > > > > > [1] > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353144 > > > > [2] > > > > > > > https://dist.apache.org/repos/dist/dev/flink/flink-connector-gcp-pubsub-3.0.2-rc2 > > > > [3] https://dist.apache.org/repos/dist/release/flink/KEYS > > > > [4] > > https://repository.apache.org/content/repositories/orgapacheflink-1673/ > > > > [5] > > https://github.com/apache/flink-connector-gcp-pubsub/tree/v3.0.2-rc2 > > > > [6] https://github.com/apache/flink-web/pull/695 > > > > > >
Re: [VOTE] Release flink-connector-opensearch v1.1.0, release candidate #1
Apologies I jumped the gun on this one. We only have 2 binding votes. Reopening the thread. On Fri, Jan 12, 2024 at 3:43 PM Danny Cranmer wrote: > Thanks all, this vote is now closed, I will announce the results on a > separate thread. > > Thanks, > Danny > > On Fri, Jan 12, 2024 at 3:43 PM Danny Cranmer > wrote: > >> +1 (binding) >> >> - Verified signatures and checksums >> - Reviewed release notes >> - Verified no binaries in the source archive >> - Source builds using Maven >> - Reviewed NOTICE files (I suppose the copyright needs to be 2024 now!) >> >> Thanks, >> Danny >> >> On Fri, Jan 12, 2024 at 12:56 PM Martijn Visser >> wrote: >> >>> One non blocking nit: the version for flink.version in the main POM is >>> set to 1.17.1. I think this should be 1.17.0 (since that's the lowest >>> possible Flink version that's supported). >>> >>> +1 (binding) >>> >>> - Validated hashes >>> - Verified signature >>> - Verified that no binaries exist in the source archive >>> - Build the source with Maven >>> - Verified licenses >>> - Verified web PRs >>> >>> On Mon, Jan 1, 2024 at 11:57 AM Danny Cranmer >>> wrote: >>> > >>> > Hey, >>> > >>> > Gordon, apologies for the delay. Yes this is the correct >>> understanding, all >>> > connectors follow a similar pattern. >>> > >>> > Would appreciate some PMC eyes on this release. >>> > >>> > Thanks, >>> > Danny >>> > >>> > On Thu, 23 Nov 2023, 23:28 Tzu-Li (Gordon) Tai, >>> wrote: >>> > >>> > > Hi Danny, >>> > > >>> > > Thanks for starting a RC for this. >>> > > >>> > > From the looks of the staged POMs for 1.1.0-1.18, the flink versions >>> for >>> > > Flink dependencies still point to 1.17.1. >>> > > >>> > > My understanding is that this is fine, as those provided scope >>> > > dependencies (e.g. flink-streaming-java) will have their versions >>> > > overwritten by the user POM if they do intend to compile their jobs >>> against >>> > > Flink 1.18.x. >>> > > Can you clarify if this is the correct understanding of how we >>> intend the >>> > > externalized connector artifacts to be published? Related discussion >>> on >>> > > [1]. >>> > > >>> > > Thanks, >>> > > Gordon >>> > > >>> > > [1] https://lists.apache.org/thread/x1pyrrrq7o1wv1lcdovhzpo4qhd4tvb4 >>> > > >>> > > On Thu, Nov 23, 2023 at 3:14 PM Sergey Nuyanzin >> > >>> > > wrote: >>> > > >>> > > > +1 (non-binding) >>> > > > >>> > > > - downloaded artifacts >>> > > > - built from source >>> > > > - verified checksums and signatures >>> > > > - reviewed web pr >>> > > > >>> > > > >>> > > > On Mon, Nov 6, 2023 at 5:31 PM Ryan Skraba >>> >> > > > >>> > > > wrote: >>> > > > >>> > > > > Hello! +1 (non-binding) Thanks for the release! >>> > > > > >>> > > > > I've validated the source for the RC1: >>> > > > > * flink-connector-opensearch-1.1.0-src.tgz at r64995 >>> > > > > * The sha512 checksum is OK. >>> > > > > * The source file is signed correctly. >>> > > > > * The signature 0F79F2AFB2351BC29678544591F9C1EC125FD8DB is >>> found in >>> > > the >>> > > > > KEYS file, and on https://keyserver.ubuntu.com/ >>> > > > > * The source file is consistent with the GitHub tag v1.1.0-rc1, >>> which >>> > > > > corresponds to commit 0f659cc65131c9ff7c8c35eb91f5189e80414ea1 >>> > > > > - The files explicitly excluded by create_pristine_sources (such >>> as >>> > > > > .gitignore and the submodule tools/releasing/shared) are not >>> present. >>> > > > > * Has a LICENSE file and a NOTICE file >>> > > > > * Does not contain any compiled binaries. >>> > > > > >>> > > > > * The sources can be compiled and unit tests pass
Re: [VOTE] Release flink-connector-opensearch v1.1.0, release candidate #1
+1 (binding) - Verified signatures and checksums - Reviewed release notes - Verified no binaries in the source archive - Source builds using Maven - Reviewed NOTICE files (I suppose the copyright needs to be 2024 now!) Thanks, Danny On Fri, Jan 12, 2024 at 12:56 PM Martijn Visser wrote: > One non blocking nit: the version for flink.version in the main POM is > set to 1.17.1. I think this should be 1.17.0 (since that's the lowest > possible Flink version that's supported). > > +1 (binding) > > - Validated hashes > - Verified signature > - Verified that no binaries exist in the source archive > - Build the source with Maven > - Verified licenses > - Verified web PRs > > On Mon, Jan 1, 2024 at 11:57 AM Danny Cranmer > wrote: > > > > Hey, > > > > Gordon, apologies for the delay. Yes this is the correct understanding, > all > > connectors follow a similar pattern. > > > > Would appreciate some PMC eyes on this release. > > > > Thanks, > > Danny > > > > On Thu, 23 Nov 2023, 23:28 Tzu-Li (Gordon) Tai, > wrote: > > > > > Hi Danny, > > > > > > Thanks for starting a RC for this. > > > > > > From the looks of the staged POMs for 1.1.0-1.18, the flink versions > for > > > Flink dependencies still point to 1.17.1. > > > > > > My understanding is that this is fine, as those provided scope > > > dependencies (e.g. flink-streaming-java) will have their versions > > > overwritten by the user POM if they do intend to compile their jobs > against > > > Flink 1.18.x. > > > Can you clarify if this is the correct understanding of how we intend > the > > > externalized connector artifacts to be published? Related discussion on > > > [1]. > > > > > > Thanks, > > > Gordon > > > > > > [1] https://lists.apache.org/thread/x1pyrrrq7o1wv1lcdovhzpo4qhd4tvb4 > > > > > > On Thu, Nov 23, 2023 at 3:14 PM Sergey Nuyanzin > > > wrote: > > > > > > > +1 (non-binding) > > > > > > > > - downloaded artifacts > > > > - built from source > > > > - verified checksums and signatures > > > > - reviewed web pr > > > > > > > > > > > > On Mon, Nov 6, 2023 at 5:31 PM Ryan Skraba > > > > > > > > wrote: > > > > > > > > > Hello! +1 (non-binding) Thanks for the release! > > > > > > > > > > I've validated the source for the RC1: > > > > > * flink-connector-opensearch-1.1.0-src.tgz at r64995 > > > > > * The sha512 checksum is OK. > > > > > * The source file is signed correctly. > > > > > * The signature 0F79F2AFB2351BC29678544591F9C1EC125FD8DB is found > in > > > the > > > > > KEYS file, and on https://keyserver.ubuntu.com/ > > > > > * The source file is consistent with the GitHub tag v1.1.0-rc1, > which > > > > > corresponds to commit 0f659cc65131c9ff7c8c35eb91f5189e80414ea1 > > > > > - The files explicitly excluded by create_pristine_sources (such as > > > > > .gitignore and the submodule tools/releasing/shared) are not > present. > > > > > * Has a LICENSE file and a NOTICE file > > > > > * Does not contain any compiled binaries. > > > > > > > > > > * The sources can be compiled and unit tests pass with > flink.version > > > > 1.17.1 > > > > > and flink.version 1.18.0 > > > > > > > > > > * Nexus has three staged artifact ids for 1.1.0-1.17 and 1.1.0-1.18 > > > > > - flink-connector-opensearch (.jar, -javadoc.jar, -sources.jar, > > > > > -tests.jar and .pom) > > > > > - flink-sql-connector-opensearch (.jar, -sources.jar and .pom) > > > > > - flink-connector-gcp-pubsub-parent (only .pom) > > > > > > > > > > All my best, Ryan > > > > > > > > > > On Fri, Nov 3, 2023 at 10:29 AM Danny Cranmer < > dannycran...@apache.org > > > > > > > > > wrote: > > > > > > > > > > > > Hi everyone, > > > > > > > > > > > > Please review and vote on the release candidate #1 for the > version > > > > 1.1.0 > > > > > of > > > > > > flink-connector-opensearch, as follows: > > > > > > [ ] +1, Approve the release > > > > > > [ ] -1, Do not approve the release (please provide specifi
Re: [VOTE] Release flink-connector-opensearch v1.1.0, release candidate #1
Thanks all, this vote is now closed, I will announce the results on a separate thread. Thanks, Danny On Fri, Jan 12, 2024 at 3:43 PM Danny Cranmer wrote: > +1 (binding) > > - Verified signatures and checksums > - Reviewed release notes > - Verified no binaries in the source archive > - Source builds using Maven > - Reviewed NOTICE files (I suppose the copyright needs to be 2024 now!) > > Thanks, > Danny > > On Fri, Jan 12, 2024 at 12:56 PM Martijn Visser > wrote: > >> One non blocking nit: the version for flink.version in the main POM is >> set to 1.17.1. I think this should be 1.17.0 (since that's the lowest >> possible Flink version that's supported). >> >> +1 (binding) >> >> - Validated hashes >> - Verified signature >> - Verified that no binaries exist in the source archive >> - Build the source with Maven >> - Verified licenses >> - Verified web PRs >> >> On Mon, Jan 1, 2024 at 11:57 AM Danny Cranmer >> wrote: >> > >> > Hey, >> > >> > Gordon, apologies for the delay. Yes this is the correct understanding, >> all >> > connectors follow a similar pattern. >> > >> > Would appreciate some PMC eyes on this release. >> > >> > Thanks, >> > Danny >> > >> > On Thu, 23 Nov 2023, 23:28 Tzu-Li (Gordon) Tai, >> wrote: >> > >> > > Hi Danny, >> > > >> > > Thanks for starting a RC for this. >> > > >> > > From the looks of the staged POMs for 1.1.0-1.18, the flink versions >> for >> > > Flink dependencies still point to 1.17.1. >> > > >> > > My understanding is that this is fine, as those provided scope >> > > dependencies (e.g. flink-streaming-java) will have their versions >> > > overwritten by the user POM if they do intend to compile their jobs >> against >> > > Flink 1.18.x. >> > > Can you clarify if this is the correct understanding of how we intend >> the >> > > externalized connector artifacts to be published? Related discussion >> on >> > > [1]. >> > > >> > > Thanks, >> > > Gordon >> > > >> > > [1] https://lists.apache.org/thread/x1pyrrrq7o1wv1lcdovhzpo4qhd4tvb4 >> > > >> > > On Thu, Nov 23, 2023 at 3:14 PM Sergey Nuyanzin >> > > wrote: >> > > >> > > > +1 (non-binding) >> > > > >> > > > - downloaded artifacts >> > > > - built from source >> > > > - verified checksums and signatures >> > > > - reviewed web pr >> > > > >> > > > >> > > > On Mon, Nov 6, 2023 at 5:31 PM Ryan Skraba >> > > > > >> > > > wrote: >> > > > >> > > > > Hello! +1 (non-binding) Thanks for the release! >> > > > > >> > > > > I've validated the source for the RC1: >> > > > > * flink-connector-opensearch-1.1.0-src.tgz at r64995 >> > > > > * The sha512 checksum is OK. >> > > > > * The source file is signed correctly. >> > > > > * The signature 0F79F2AFB2351BC29678544591F9C1EC125FD8DB is found >> in >> > > the >> > > > > KEYS file, and on https://keyserver.ubuntu.com/ >> > > > > * The source file is consistent with the GitHub tag v1.1.0-rc1, >> which >> > > > > corresponds to commit 0f659cc65131c9ff7c8c35eb91f5189e80414ea1 >> > > > > - The files explicitly excluded by create_pristine_sources (such >> as >> > > > > .gitignore and the submodule tools/releasing/shared) are not >> present. >> > > > > * Has a LICENSE file and a NOTICE file >> > > > > * Does not contain any compiled binaries. >> > > > > >> > > > > * The sources can be compiled and unit tests pass with >> flink.version >> > > > 1.17.1 >> > > > > and flink.version 1.18.0 >> > > > > >> > > > > * Nexus has three staged artifact ids for 1.1.0-1.17 and >> 1.1.0-1.18 >> > > > > - flink-connector-opensearch (.jar, -javadoc.jar, -sources.jar, >> > > > > -tests.jar and .pom) >> > > > > - flink-sql-connector-opensearch (.jar, -sources.jar and .pom) >> > > > > - flink-connector-gcp-pubsub-parent (only .pom) >> > > > > >> > > > > All my best, Ryan >>
Re: [VOTE] Accept Flink CDC into Apache Flink
+1 (binding) Thanks, Danny On Tue, Jan 9, 2024 at 9:31 AM Feng Jin wrote: > +1 (non-binding) > > Best, > Feng Jin > > On Tue, Jan 9, 2024 at 5:29 PM Yuxin Tan wrote: > > > +1 (non-binding) > > > > Best, > > Yuxin > > > > > > Márton Balassi 于2024年1月9日周二 17:25写道： > > > > > +1 (binding) > > > > > > On Tue, Jan 9, 2024 at 10:15 AM Leonard Xu wrote: > > > > > > > +1(binding) > > > > > > > > Best, > > > > Leonard > > > > > > > > > 2024年1月9日 下午5:08，Yangze Guo 写道： > > > > > > > > > > +1 (non-binding) > > > > > > > > > > Best, > > > > > Yangze Guo > > > > > > > > > > On Tue, Jan 9, 2024 at 5:06 PM Robert Metzger > > > > > wrote: > > > > >> > > > > >> +1 (binding) > > > > >> > > > > >> > > > > >> On Tue, Jan 9, 2024 at 9:54 AM Guowei Ma > > > wrote: > > > > >> > > > > >>> +1 (binding) > > > > >>> Best, > > > > >>> Guowei > > > > >>> > > > > >>> > > > > >>> On Tue, Jan 9, 2024 at 4:49 PM Rui Fan <1996fan...@gmail.com> > > wrote: > > > > >>> > > > > +1 (non-binding) > > > > > > > > Best, > > > > Rui > > > > > > > > On Tue, Jan 9, 2024 at 4:41 PM Hang Ruan < > ruanhang1...@gmail.com> > > > > wrote: > > > > > > > > > +1 (non-binding) > > > > > > > > > > Best, > > > > > Hang > > > > > > > > > > gongzhongqiang 于2024年1月9日周二 > 16:25写道： > > > > > > > > > >> +1 non-binding > > > > >> > > > > >> Best, > > > > >> Zhongqiang > > > > >> > > > > >> Leonard Xu 于2024年1月9日周二 15:05写道： > > > > >> > > > > >>> Hello all, > > > > >>> > > > > >>> This is the official vote whether to accept the Flink CDC > code > > > > >> contribution > > > > >>> to Apache Flink. > > > > >>> > > > > >>> The current Flink CDC code, documentation, and website can be > > > > >>> found here: > > > > >>> code: https://github.com/ververica/flink-cdc-connectors < > > > > >>> https://github.com/ververica/flink-cdc-connectors> > > > > >>> docs: https://ververica.github.io/flink-cdc-connectors/ < > > > > >>> https://ververica.github.io/flink-cdc-connectors/> > > > > >>> > > > > >>> This vote should capture whether the Apache Flink community > is > > > > > interested > > > > >>> in accepting, maintaining, and evolving Flink CDC. > > > > >>> > > > > >>> Regarding my original proposal[1] in the dev mailing list, I > > > firmly > > > > >> believe > > > > >>> that this initiative aligns perfectly with Flink. For the > Flink > > > > >> community, > > > > >>> it represents an opportunity to bolster Flink's competitive > > edge > > > in > > > > >>> streaming > > > > >>> data integration, fostering the robust growth and prosperity > of > > > the > > > > >> Apache > > > > >>> Flink > > > > >>> ecosystem. For the Flink CDC project, becoming a sub-project > of > > > > Apache > > > > >>> Flink > > > > >>> means becoming an integral part of a neutral open-source > > > community, > > > > >>> capable of > > > > >>> attracting a more diverse pool of contributors. > > > > >>> > > > > >>> All Flink CDC maintainers are dedicated to continuously > > > > >>> contributing > > > > to > > > > >>> achieve > > > > >>> seamless integration with Flink. Additionally, PMC members > like > > > > >>> Jark, > > > > >>> Qingsheng, > > > > >>> and I are willing to infacilitate the expansion of > contributors > > > and > > > > >>> committers to > > > > >>> effectively maintain this new sub-project. > > > > >>> > > > > >>> This is a "Adoption of a new Codebase" vote as per the Flink > > > bylaws > > > > > [2]. > > > > >>> Only PMC votes are binding. The vote will be open at least 7 > > days > > > > >>> (excluding weekends), meaning until Thursday January 18 12:00 > > > UTC, > > > > >>> or > > > > >>> until we > > > > >>> achieve the 2/3rd majority. We will follow the instructions > in > > > the > > > > > Flink > > > > >>> Bylaws > > > > >>> in the case of insufficient active binding voters: > > > > >>> > > > > 1. Wait until the minimum length of the voting passes. > > > > 2. Publicly reach out via personal email to the remaining > > > binding > > > > >> voters > > > > >>> in the > > > > >>> voting mail thread for at least 2 attempts with at least 7 > days > > > > between > > > > >>> two attempts. > > > > 3. If the binding voter being contacted still failed to > > respond > > > > after > > > > >>> all the attempts, > > > > >>> the binding voter will be considered as inactive for the > > purpose > > > of > > > > > this > > > > >>> particular voting. > > > > >>> > > > > >>> Welcome voting ! > > > > >>> > > > > >>> Best, > > > > >>> Leonard > > > > >>> [1] > > > > >>> https://lists.apache.org/thread/o7klnbsotmmql999bnwmdgo56b6kxx9l > > > > >>> [2] > > > > >>> > > > > >> > > > > > > > > >
[DISCUSS] Externalized Python Connector Release/Dependency Process
Hello all, I have been working with Péter and Marton on externalizing python connectors [1] from the main repo to the connector repositories. We have the code moved and the CI running tests for Kafka and AWS Connectors. I am now looking into the release process. When we undertake a Flink release we perform the following steps [2], regarding Python: 1/ run python build on CI, 2/ download Wheels artifacts, 3/ upload artifacts to the dist and 4/ deploy to pypi. The plan is to follow the same steps for connectors, using Github actions instead of Azure pipeline. Today we have a single pypi project for pyflink that contains all the Flink libs, apache-flink [3]. I propose we create a new pypi project per connector using the existing connector version, and following naming convention: apache-, for example: apache-flink-connector-aws, apache-flink-connector-kafka. Therefore to use a DataStream API connector in python, users would need to first install the lib, for example "python -m pip install apache-flink-connector-aws". Once we have consensus I will update the release process and perform a release of the flink-connector-aws project to test it end-to-end. I look forward to any feedback. Thanks, Danny [1] https://issues.apache.org/jira/browse/FLINK-33528 [2] https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release [3] https://pypi.org/project/apache-flink/
[jira] [Created] (FLINK-34024) Update connector release process for Python connectors
Danny Cranmer created FLINK-34024: - Summary: Update connector release process for Python connectors Key: FLINK-34024 URL: https://issues.apache.org/jira/browse/FLINK-34024 Project: Flink Issue Type: Sub-task Reporter: Danny Cranmer Work out how to release the Python libs for Flink connectors. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [VOTE] Release flink-connector-opensearch v1.1.0, release candidate #1
Hey, Gordon, apologies for the delay. Yes this is the correct understanding, all connectors follow a similar pattern. Would appreciate some PMC eyes on this release. Thanks, Danny On Thu, 23 Nov 2023, 23:28 Tzu-Li (Gordon) Tai, wrote: > Hi Danny, > > Thanks for starting a RC for this. > > From the looks of the staged POMs for 1.1.0-1.18, the flink versions for > Flink dependencies still point to 1.17.1. > > My understanding is that this is fine, as those provided scope > dependencies (e.g. flink-streaming-java) will have their versions > overwritten by the user POM if they do intend to compile their jobs against > Flink 1.18.x. > Can you clarify if this is the correct understanding of how we intend the > externalized connector artifacts to be published? Related discussion on > [1]. > > Thanks, > Gordon > > [1] https://lists.apache.org/thread/x1pyrrrq7o1wv1lcdovhzpo4qhd4tvb4 > > On Thu, Nov 23, 2023 at 3:14 PM Sergey Nuyanzin > wrote: > > > +1 (non-binding) > > > > - downloaded artifacts > > - built from source > > - verified checksums and signatures > > - reviewed web pr > > > > > > On Mon, Nov 6, 2023 at 5:31 PM Ryan Skraba > > > wrote: > > > > > Hello! +1 (non-binding) Thanks for the release! > > > > > > I've validated the source for the RC1: > > > * flink-connector-opensearch-1.1.0-src.tgz at r64995 > > > * The sha512 checksum is OK. > > > * The source file is signed correctly. > > > * The signature 0F79F2AFB2351BC29678544591F9C1EC125FD8DB is found in > the > > > KEYS file, and on https://keyserver.ubuntu.com/ > > > * The source file is consistent with the GitHub tag v1.1.0-rc1, which > > > corresponds to commit 0f659cc65131c9ff7c8c35eb91f5189e80414ea1 > > > - The files explicitly excluded by create_pristine_sources (such as > > > .gitignore and the submodule tools/releasing/shared) are not present. > > > * Has a LICENSE file and a NOTICE file > > > * Does not contain any compiled binaries. > > > > > > * The sources can be compiled and unit tests pass with flink.version > > 1.17.1 > > > and flink.version 1.18.0 > > > > > > * Nexus has three staged artifact ids for 1.1.0-1.17 and 1.1.0-1.18 > > > - flink-connector-opensearch (.jar, -javadoc.jar, -sources.jar, > > > -tests.jar and .pom) > > > - flink-sql-connector-opensearch (.jar, -sources.jar and .pom) > > > - flink-connector-gcp-pubsub-parent (only .pom) > > > > > > All my best, Ryan > > > > > > On Fri, Nov 3, 2023 at 10:29 AM Danny Cranmer > > > > wrote: > > > > > > > > Hi everyone, > > > > > > > > Please review and vote on the release candidate #1 for the version > > 1.1.0 > > > of > > > > flink-connector-opensearch, as follows: > > > > [ ] +1, Approve the release > > > > [ ] -1, Do not approve the release (please provide specific comments) > > > > > > > > > > > > The complete staging area is available for your review, which > includes: > > > > * JIRA release notes [1], > > > > * the official Apache source release to be deployed to > dist.apache.org > > > [2], > > > > which are signed with the key with fingerprint > > > > 0F79F2AFB2351BC29678544591F9C1EC125FD8DB [3], > > > > * all artifacts to be deployed to the Maven Central Repository [4], > > > > * source code tag v1.1.0-rc1 [5], > > > > * website pull request listing the new release [6]. > > > > > > > > The vote will be open for at least 72 hours. It is adopted by > majority > > > > approval, with at least 3 PMC affirmative votes. > > > > > > > > Thanks, > > > > Danny > > > > > > > > [1] > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353141 > > > > [2] > > > > > > > > > > https://dist.apache.org/repos/dist/dev/flink/flink-connector-opensearch-1.1.0-rc1/ > > > > [3] https://dist.apache.org/repos/dist/release/flink/KEYS > > > > [4] > > > > https://repository.apache.org/content/repositories/orgapacheflink-1666/ > > > > [5] > > https://github.com/apache/flink-connector-opensearch/tree/v1.1.0-rc1 > > > > [6] https://github.com/apache/flink-web/pull/694 > > > > > > > > > -- > > Best regards, > > Sergey > > >
Re: [VOTE] Release flink-connector-pulsar 4.1.0, release candidate #1
Hello, Thanks for driving, Leonard, +1 (binding) - Verified signatures and checksums of source and binaries - Maven dist contains expected files - There are no binaries in the source archive - Release notes look good - Tag exists in Github - CI passes for v4.1 [1] (could not find a tag build, but this one is equivalent) - Sources build locally - Verified bundled dependencies are correctly reflected in NOTICE file Thanks, Danny [1] https://github.com/apache/flink-connector-pulsar/actions/runs/7164218129 On Wed, Dec 20, 2023 at 11:16 PM Sergey Nuyanzin wrote: > +1 (non-binding) > > - Downloaded artifacts > - Maven staging artifacts look good > - Verified checksum && keys > - Verified LICENSE and NOTICE files > - Built from source > > On Wed, Dec 20, 2023 at 5:13 AM tison wrote: > > > Hi Leonard, > > > > You are a PMC member also. Perhaps you can check the candidate and > > vote on what you do :D > > > > Best, > > tison. > > > > Leonard Xu 于2023年12月20日周三 11:35写道： > > > > > > Bubble up, I need more votes, especially from PMC members. > > > > > > Best, > > > Leonard > > > > > > > 2023年12月14日 下午11:03，Hang Ruan 写道： > > > > > > > > +1 (non-binding) > > > > > > > > - Validated checksum hash > > > > - Verified signature > > > > - Verified that no binaries exist in the source archive > > > > - Build the source with jdk8 > > > > - Verified web PR > > > > - Make sure flink-connector-base have the provided scope > > > > > > > > Best, > > > > Hang > > > > > > > > tison 于2023年12月14日周四 11:51写道： > > > > > > > >> Thanks Leonard for driving this release! > > > >> > > > >> +1 (non-binding) > > > >> > > > >> * Download link valid > > > >> * Maven staging artifacts look good. > > > >> * Checksum and gpg matches > > > >> * LICENSE and NOTICE exist > > > >> * Can build from source. > > > >> > > > >> Best, > > > >> tison. > > > >> > > > >> Rui Fan <1996fan...@gmail.com> 于2023年12月14日周四 09:23写道： > > > >>> > > > >>> Thanks Leonard for driving this release! > > > >>> > > > >>> +1 (non-binding) > > > >>> > > > >>> - Validated checksum hash > > > >>> - Verified signature > > > >>> - Verified that no binaries exist in the source archive > > > >>> - Build the source with Maven and jdk8 > > > >>> - Verified licenses > > > >>> - Verified web PRs, left a minor comment > > > >>> > > > >>> Best, > > > >>> Rui > > > >>> > > > >>> On Wed, Dec 13, 2023 at 7:15 PM Leonard Xu > > wrote: > > > > > > Hey all, > > > > > > Please review and vote on the release candidate #1 for the version > > > >> 4.1.0 of the Apache Flink Pulsar Connector as follows: > > > > > > [ ] +1, Approve the release > > > [ ] -1, Do not approve the release (please provide specific > > comments) > > > > > > The complete staging area is available for your review, which > > includes: > > > * JIRA release notes [1], > > > * The official Apache source release to be deployed to > > dist.apache.org > > > >> [2], which are signed with the key with fingerprint > > > 5B2F6608732389AEB67331F5B197E1F1108998AD [3], > > > * All artifacts to be deployed to the Maven Central Repository > [4], > > > * Source code tag v4.1.0-rc1 [5], > > > * Website pull request listing the new release [6]. > > > > > > The vote will be open for at least 72 hours. It is adopted by > > majority > > > >> approval, with at least 3 PMC affirmative votes. > > > > > > > > > Best, > > > Leonard > > > > > > [1] > > > >> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353431 > > > [2] > > > >> > > > https://dist.apache.org/repos/dist/dev/flink/flink-connector-pulsar-4.1.0-rc1/ > > > [3] https://dist.apache.org/repos/dist/release/flink/KEYS > > > [4] > > > >> > > https://repository.apache.org/content/repositories/orgapacheflink-1688/ > > > [5] > > https://github.com/apache/flink-connector-pulsar/tree/v4.1.0-rc1 > > > [6] https://github.com/apache/flink-web/pull/703 > > > >> > > > > > > > > -- > Best regards, > Sergey >
Re: [DISCUSS] Release Flink 1.18.1
+1 Thanks for driving this On Fri, 8 Dec 2023, 12:05 Timo Walther, wrote: > Thanks for taking care of this Jing. > > +1 to release 1.18.1 for this. > > Cheers, > Timo > > > On 08.12.23 10:00, Benchao Li wrote: > > I've merged FLINK-33313 to release-1.18 branch. > > > > Péter Váry 于2023年12月8日周五 16:56写道： > >> > >> Hi Jing, > >> Thanks for taking care of this! > >> +1 (non-binding) > >> Peter > >> > >> Sergey Nuyanzin ezt írta (időpont: 2023. dec. > 8., P, > >> 9:36): > >> > >>> Thanks Jing driving it > >>> +1 > >>> > >>> also +1 to include FLINK-33313 mentioned by Benchao Li > >>> > >>> On Fri, Dec 8, 2023 at 9:17 AM Benchao Li > wrote: > >>> > Thanks Jing for driving 1.18.1 releasing. > > I would like to include FLINK-33313[1] in 1.18.1, it's just a bugfix, > not a blocker, but it's already merged into master, I plan to merge it > to 1.8/1.7 branches today after the CI passes. > > [1] https://issues.apache.org/jira/browse/FLINK-33313 > > Jing Ge 于2023年12月8日周五 16:06写道： > > > > Hi all, > > > > I would like to discuss creating a new 1.18 patch release (1.18.1). > The > > last 1.18 release is nearly two months old, and since then, 37 > tickets > have > > been closed [1], of which 6 are blocker/critical [2]. Some of them > are > > quite important, such as FLINK-33598 [3] > > > > Most urgent and important one is FLINK-33523 [4] and according to the > > discussion thread[5] on the ML, 1.18.1 should/must be released asap > >>> after > > the breaking change commit has been reverted. > > > > I am not aware of any other unresolved blockers and there are no > in-progress > > tickets [6]. > > Please let me know if there are any issues you'd like to be included > in > > this release but still not merged. > > > > If the community agrees to create this new patch release, I could > > volunteer as the release manager. > > > > Best regards, > > Jing > > > > [1] > > > > >>> > https://issues.apache.org/jira/browse/FLINK-33567?jql=project%20%3D%20FLINK%20AND%20fixVersion%20%3D%201.18.1%20%20and%20resolution%20%20!%3D%20%20Unresolved%20order%20by%20priority%20DESC > > [2] > > > > >>> > https://issues.apache.org/jira/browse/FLINK-33693?jql=project%20%3D%20FLINK%20AND%20fixVersion%20%3D%201.18.1%20and%20resolution%20%20!%3D%20Unresolved%20%20and%20priority%20in%20(Blocker%2C%20Critical)%20ORDER%20by%20priority%20%20DESC > > [3] https://issues.apache.org/jira/browse/FLINK-33598 > > [4] https://issues.apache.org/jira/browse/FLINK-33523 > > [5] https://lists.apache.org/thread/m4c879y8mb7hbn2kkjh9h3d8g1jphh3j > > [6] https://issues.apache.org/jira/projects/FLINK/versions/12353640 > > Thanks, > > > > -- > > Best, > Benchao Li > > >>> > >>> > >>> -- > >>> Best regards, > >>> Sergey > >>> > > > > > > > >
[ANNOUNCE] Apache flink-connector-aws 4.2.0 released
The Apache Flink community is very happy to announce the release of Apache flink-connector-aws 4.2.0. This release supports Flink 1.17 and 1.18. Apache Flink® is an open-source stream processing framework for distributed, high-performing, always-available, and accurate data streaming applications. The release is available for download at: https://flink.apache.org/downloads.html The full release notes are available in Jira: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353011 We would like to thank all contributors of the Apache Flink community who made this release possible! Regards, Danny
[RESULT][VOTE] Release flink-connector-aws, v4.2.0 release candidate #1
I'm happy to announce that we have unanimously approved this release. There are 7 approving votes, 3 of which are binding: * Mystic Lama * Danny Cranmer (binding) * Jiabao Sun * Martijn Visser (binding) * Ahmed Hamdy * Leonard Xu (binding) * Samrat Deb There are no disapproving votes. Thanks everyone! Danny
Re: [VOTE] Release flink-connector-aws, v4.2.0 release candidate #1
Thanks everyone for the support. This vote is now closed, I will announce the results in a separate email. Danny. On Thu, Nov 30, 2023 at 5:20 AM Samrat Deb wrote: > Hi danny , > > +1 (non binding) > > Release notes look good > - Signatures and checksums verified > - pom versions checked > - Source build and tests verified > > Bests, > Samrat > > On Wed, 29 Nov 2023 at 12:11 PM, Leonard Xu wrote: > > > Thanks Danny for driving this, sorry for late verification. > > > > +1 (binding) > > > > - built from source code succeeded > > - verified signatures > > - verified hashsums > > - checked the contents contains jar and pom files in apache repo > > - checked Github release tag > > - reviewed the web PR with minor comment > > > > Best, > > Leonard > > > > > > > > > 2023年11月27日 上午1:13，Ahmed Hamdy 写道： > > > > > > Hi Danny > > > +1 (non-binding) > > > > > > > > > - Verified signatures and checksums > > > - verified no binaries exists in archive > > > - built source > > > - reviewed web PR > > > - Ran E2E example with Kinesis, Firehose & DynamoDB datastream > > connectors. > > > > > > Best Regards > > > Ahmed Hamdy > > > > > > > > > On Fri, 24 Nov 2023 at 08:38, Martijn Visser > > > > wrote: > > > > > >> Hi Danny, > > >> > > >> Thanks for driving this. > > >> > > >> +1 (binding) > > >> > > >> - Validated hashes > > >> - Verified signature > > >> - Verified that no binaries exist in the source archive > > >> - Build the source with Maven > > >> - Verified licenses > > >> - Verified web PRs > > >> > > >> On Mon, Nov 20, 2023 at 12:29 PM Jiabao Sun > > >> wrote: > > >>> > > >>> Thanks Danny for driving the release, > > >>> > > >>> +1 (non-binding) > > >>> > > >>> - built from source code succeeded > > >>> - verified signatures > > >>> - verified hashsums > > >>> - checked release notes > > >>> > > >>> Best, > > >>> Jiabao > > >>> > > >>> > > >>>> 2023年11月20日 19:11，Danny Cranmer 写道： > > >>>> > > >>>> Hello all, > > >>>> > > >>>> +1 (binding). > > >>>> > > >>>> - Release notes look good > > >>>> - Signatures and checksums match > > >>>> - There are no binaries in the source archive > > >>>> - pom versions are correct > > >>>> - Tag is present in Github > > >>>> - CI passes against FLink 1.17 and 1.18 > > >>>> - Source build and tests pass > > >>>> > > >>>> Thanks, > > >>>> Danny > > >>>> > > >>>> On Wed, Nov 1, 2023 at 1:15 AM mystic lama > > > >> wrote: > > >>>> > > >>>>> +1 (non-binding) > > >>>>> > > >>>>> - validated shasum > > >>>>> - verified build > > >>>>> - Java 8 - build good and all test cases pass > > >>>>> - Java 11 - build good and all test cases pass > > >>>>> > > >>>>> Observations: got test failures with Java 17, something to look for > > in > > >>>>> future > > >>>>> > > >>>>> On Tue, 31 Oct 2023 at 08:42, Danny Cranmer < > dannycran...@apache.org > > > > > >>>>> wrote: > > >>>>> > > >>>>>> Hi everyone, > > >>>>>> > > >>>>>> Please review and vote on release candidate #1 for the version > > >> 4.2.0, as > > >>>>>> follows: > > >>>>>> [ ] +1, Approve the release > > >>>>>> [ ] -1, Do not approve the release (please provide specific > > comments) > > >>>>>> > > >>>>>> The complete staging area is available for your review, which > > >> includes: > > >>>>>> * JIRA release notes [1], > > >>>>>> * the official Apache source release to be deployed to > > >> dist.apache.org > > >>>>>> [2], > > >>>>>> which are signed with the key with fingerprint > > >>>>>> 0F79F2AFB2351BC29678544591F9C1EC125FD8DB [3], > > >>>>>> * all artifacts to be deployed to the Maven Central Repository > [4], > > >>>>>> * source code tag v4.2.0-rc1 [5], > > >>>>>> * website pull request listing the new release [6]. > > >>>>>> * A link to the CI run on the release tag [7] > > >>>>>> > > >>>>>> The vote will be open for at least 72 hours. It is adopted by > > >> majority > > >>>>>> approval, with at least 3 PMC affirmative votes. > > >>>>>> > > >>>>>> Thanks, > > >>>>>> Danny > > >>>>>> > > >>>>>> [1] > > >>>>>> > > >>>>>> > > >>>>> > > >> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353011 > > >>>>>> [2] > > >>>>>> > > >>>>> > > >> > > > https://dist.apache.org/repos/dist/dev/flink/flink-connector-aws-4.2.0-rc1 > > >>>>>> [3] https://dist.apache.org/repos/dist/release/flink/KEYS > > >>>>>> [4] > > >>>>>> > > >> > https://repository.apache.org/content/repositories/orgapacheflink-1665/ > > >>>>>> [5] > > >>>>> > > https://github.com/apache/flink-connector-aws/releases/tag/v4.2.0-rc1 > > >>>>>> [6] https://github.com/apache/flink-web/pull/693 > > >>>>>> [7] > > >>>>> > > https://github.com/apache/flink-connector-aws/actions/runs/6707962074 > > >>>>>> > > >>>>> > > >>> > > >> > > > > >
