You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fluss.apache.org by Jark Wu <im...@gmail.com> on 2026/09/18 09:26:45 UTC
[VOTE] Release Apache Fluss 1.0.0 (RC3)
Hi everyone,
I'd like to start the community vote for Apache Fluss 1.0.0, release
candidate 3. The RC2 was cancelled because it uses a conflict version
(1.0.0) of pyfluss.
The candidate artifacts are available at the following locations:
Source and binary distributions, including Gateway binaries for Linux
amd64 and arm64:
https://dist.apache.org/repos/dist/dev/fluss/fluss-1.0.0-rc3/
Helm chart:
https://dist.apache.org/repos/dist/dev/fluss/helm-chart/1.0.0-rc3/
When testing the chart, please override the image tag with --set
image.tag=1.0.0-rc3.
Maven staging repository:
https://repository.apache.org/content/repositories/orgapachefluss-1016/
Python client (pyfluss 1.0.0rc3) on TestPyPI:
https://test.pypi.org/project/pyfluss/1.0.0rc3/
Git tag:
https://github.com/apache/fluss/releases/tag/v1.0.0-rc3
Git commit:
https://github.com/apache/fluss/commit/5c07f88e50a8ff41b0ebc214a0458e5dba60be37
Signing key fingerprint:
E2C45417BED5C104154F341085BACB5AEFAE3202
The public key is available in the KEYS file:
https://dist.apache.org/repos/dist/release/fluss/KEYS
The following Docker images are available for testing:
- apache/fluss:1.0.0-rc3
- apache/fluss-gateway:1.0.0-rc3
- apache/fluss-quickstart-flink:1.20-1.0.0-rc3
Release announcement draft:
https://github.com/apache/fluss-blog/pull/15
Download link update:
https://github.com/apache/fluss/pull/4418
Upgrade notes:
https://github.com/apache/fluss/blob/release-1.0/website/docs/maintenance/operations/upgrade-notes-1.0.md
Please try the candidate and include the checks you performed with
your vote. The verification guide covers signatures, checksums,
builds, licenses, and functional testing:
https://fluss.apache.org/community/how-to-release/verifying-a-fluss-release/
Please reply with your vote:
[ ] +1: Support releasing this candidate
[ ] -1: Oppose releasing this candidate (please explain the issues)
Voting will remain open for a minimum of 72 hours. Approval requires a
majority in favor, including at least three binding +1 votes from PMC
members. Votes and testing feedback from all community members are
welcome.
Thanks,
Jark & Keith
Re: [VOTE] Release Apache Fluss 1.0.0 (RC3)
Posted by Hongshun Wang <lo...@gmail.com>.
+1 bindings
Here's a polished English version of your sentence:
I have tested Flink batch read capabilities, including :
* KV table merge batch reads,
* KV table scan batch reads
* log table batch reads,
* stream bounded reads,
* virtual table batch reads,
* batch updates and deletes without primary keys.
Best,
Hongshun
On Sun, Sep 20, 2026 at 7:29 PM Yang Guo <gu...@gmail.com> wrote:
> +1 non-bindings
>
> I have verified the release candidate 3 as follows:
>
> - GPG signatures and SHA-512 for fluss-src, fluss-gataway, helm-charts and
> fluss binary.
>
> - Build successfully for maven and fluss rust cargo.
>
> - LICENSE and NOTICE files correct; all source files carry ASF headers
>
> - Gateway binary distribution (arm64, Debian bookworm container)
>
> - Staged Maven artifacts (orgapachefluss-1016): dependency resolution,
> compilation, and a functional Java client test (connect + list databases)
>
> - pyfluss 1.0.0rc3 from TestPyPI: create table, 10 upserts with server
> acks, delete, point lookups (hit / miss / after-delete), full bucket scan
> returns 10 rows
>
> - Quickstart Flink image: Flink 1.20 cluster with the bundled connector —
> created Fluss catalog/table via SQL, INSERT 3 rows, batch SELECT returned
> all rows
>
> Thanks Jark and Keith,
>
> Regards,
>
> Yang GUO
>
>
> On Sun, Sep 20, 2026 at 5:48 PM Junbo Wang <be...@gmail.com> wrote:
>
> > +1 (non-binding)
> >
> > I verified:
> > - Signatures and SHA-512 checksums for the source, Java binary, both
> > Gateway binaries, and Helm artifacts.
> > - Git tag signature and commit. Source files match the tag except that
> > CLAUDE.md is packaged as a regular file instead of a symlink.
> > - Java binary LICENSE/NOTICE, JDK 11 startup, read/write operations, and
> > data recovery after a clean cluster restart.
> > - Coordinator failover, KV full scans, column-statistics filtering, and
> > multi-table subscriptions.
> > - Maven source build with -DskipTests; Gateway Rust 1.88 build and 192
> > tests passed, with 1 ignored.
> > - Local arm64 RC3 images: Gateway smoke tests, plaintext/SASL writes, and
> > Flink 1.20 read-back and non-primary-key UPDATE/DELETE.
> > - Helm provenance, lint, and template rendering.
> >
> > Thanks, Jark and Keith, for driving the 1.0 release!
> >
> > Best regards,
> > Junbo Wang
> >
> > > On 20 Sep 2026, at 16:09, Zhe Wang <ja...@gmail.com> wrote:
> > >
> > > +1 (non-binding)
> > >
> > > Checks I ran against the Maven staging repository
> (orgapachefluss-1016),
> > > on the filesystem plugin uber-jars:
> > >
> > > - Signatures: fluss-fs-s3-1.0.0.jar and fluss-fs-gs-1.0.0.jar both
> > verify as
> > > Good signature from E2C45417BED5C104154F341085BACB5AEFAE3202 (Jark
> Wu),
> > > key imported from dist/release/fluss/KEYS.
> > > - Checksums: md5 matches for both jars; Content-Length and `unzip -t`
> > clean
> > > on all four (fs-s3, fs-hdfs, fs-azure, fs-gs).
> > > - Shaded-dependency check on the four uber-jars: each ships unshaded
> > > com/fasterxml (jackson, 1,073 entries) and unshaded com/google (guava:
> > > 2,102 s3 / 2,791 hdfs / 2,102 azure / 7,411 gs). fluss-fs-s3 and
> > > fluss-fs-gs contain no org.apache.fluss.fs.shaded.* package at all.
> > >
> > > The last point is not a blocker for RC3 — it is the known relocation
> gap
> > > already tracked for 1.1 (#3553 is on the v1.1 milestone; #4116 and
> #4073
> > > remain open against main). I'm recording it only so the state of the
> > > artifacts I checked is on the list.
> > >
> > > Thanks Jark and Keith for driving this.
> > >
> > > Best,
> > > Zhe Wang
> > >
> > > Jark Wu <im...@gmail.com> 于2026年9月18日周五 17:28写道：
> > >
> > >> Hi everyone,
> > >>
> > >> I'd like to start the community vote for Apache Fluss 1.0.0, release
> > >> candidate 3. The RC2 was cancelled because it uses a conflict version
> > >> (1.0.0) of pyfluss.
> > >>
> > >> The candidate artifacts are available at the following locations:
> > >>
> > >> Source and binary distributions, including Gateway binaries for Linux
> > >> amd64 and arm64:
> > >> https://dist.apache.org/repos/dist/dev/fluss/fluss-1.0.0-rc3/
> > >>
> > >> Helm chart:
> > >> https://dist.apache.org/repos/dist/dev/fluss/helm-chart/1.0.0-rc3/
> > >>
> > >> When testing the chart, please override the image tag with --set
> > >> image.tag=1.0.0-rc3.
> > >>
> > >> Maven staging repository:
> > >>
> https://repository.apache.org/content/repositories/orgapachefluss-1016/
> > >>
> > >> Python client (pyfluss 1.0.0rc3) on TestPyPI:
> > >> https://test.pypi.org/project/pyfluss/1.0.0rc3/
> > >>
> > >> Git tag:
> > >> https://github.com/apache/fluss/releases/tag/v1.0.0-rc3
> > >>
> > >> Git commit:
> > >>
> > >>
> >
> https://github.com/apache/fluss/commit/5c07f88e50a8ff41b0ebc214a0458e5dba60be37
> > >>
> > >> Signing key fingerprint:
> > >> E2C45417BED5C104154F341085BACB5AEFAE3202
> > >>
> > >> The public key is available in the KEYS file:
> > >> https://dist.apache.org/repos/dist/release/fluss/KEYS
> > >>
> > >> The following Docker images are available for testing:
> > >> - apache/fluss:1.0.0-rc3
> > >> - apache/fluss-gateway:1.0.0-rc3
> > >> - apache/fluss-quickstart-flink:1.20-1.0.0-rc3
> > >>
> > >> Release announcement draft:
> > >> https://github.com/apache/fluss-blog/pull/15
> > >>
> > >> Download link update:
> > >> https://github.com/apache/fluss/pull/4418
> > >>
> > >> Upgrade notes:
> > >>
> > >>
> >
> https://github.com/apache/fluss/blob/release-1.0/website/docs/maintenance/operations/upgrade-notes-1.0.md
> > >>
> > >> Please try the candidate and include the checks you performed with
> > >> your vote. The verification guide covers signatures, checksums,
> > >> builds, licenses, and functional testing:
> > >>
> > >>
> >
> https://fluss.apache.org/community/how-to-release/verifying-a-fluss-release/
> > >>
> > >> Please reply with your vote:
> > >>
> > >> [ ] +1: Support releasing this candidate
> > >> [ ] -1: Oppose releasing this candidate (please explain the issues)
> > >>
> > >> Voting will remain open for a minimum of 72 hours. Approval requires a
> > >> majority in favor, including at least three binding +1 votes from PMC
> > >> members. Votes and testing feedback from all community members are
> > >> welcome.
> > >>
> > >> Thanks,
> > >> Jark & Keith
> > >>
> >
> >
>
Re: [VOTE] Release Apache Fluss 1.0.0 (RC3)
Posted by Yang Guo <gu...@gmail.com>.
+1 non-bindings
I have verified the release candidate 3 as follows:
- GPG signatures and SHA-512 for fluss-src, fluss-gataway, helm-charts and
fluss binary.
- Build successfully for maven and fluss rust cargo.
- LICENSE and NOTICE files correct; all source files carry ASF headers
- Gateway binary distribution (arm64, Debian bookworm container)
- Staged Maven artifacts (orgapachefluss-1016): dependency resolution,
compilation, and a functional Java client test (connect + list databases)
- pyfluss 1.0.0rc3 from TestPyPI: create table, 10 upserts with server
acks, delete, point lookups (hit / miss / after-delete), full bucket scan
returns 10 rows
- Quickstart Flink image: Flink 1.20 cluster with the bundled connector —
created Fluss catalog/table via SQL, INSERT 3 rows, batch SELECT returned
all rows
Thanks Jark and Keith,
Regards,
Yang GUO
On Sun, Sep 20, 2026 at 5:48 PM Junbo Wang <be...@gmail.com> wrote:
> +1 (non-binding)
>
> I verified:
> - Signatures and SHA-512 checksums for the source, Java binary, both
> Gateway binaries, and Helm artifacts.
> - Git tag signature and commit. Source files match the tag except that
> CLAUDE.md is packaged as a regular file instead of a symlink.
> - Java binary LICENSE/NOTICE, JDK 11 startup, read/write operations, and
> data recovery after a clean cluster restart.
> - Coordinator failover, KV full scans, column-statistics filtering, and
> multi-table subscriptions.
> - Maven source build with -DskipTests; Gateway Rust 1.88 build and 192
> tests passed, with 1 ignored.
> - Local arm64 RC3 images: Gateway smoke tests, plaintext/SASL writes, and
> Flink 1.20 read-back and non-primary-key UPDATE/DELETE.
> - Helm provenance, lint, and template rendering.
>
> Thanks, Jark and Keith, for driving the 1.0 release!
>
> Best regards,
> Junbo Wang
>
> > On 20 Sep 2026, at 16:09, Zhe Wang <ja...@gmail.com> wrote:
> >
> > +1 (non-binding)
> >
> > Checks I ran against the Maven staging repository (orgapachefluss-1016),
> > on the filesystem plugin uber-jars:
> >
> > - Signatures: fluss-fs-s3-1.0.0.jar and fluss-fs-gs-1.0.0.jar both
> verify as
> > Good signature from E2C45417BED5C104154F341085BACB5AEFAE3202 (Jark Wu),
> > key imported from dist/release/fluss/KEYS.
> > - Checksums: md5 matches for both jars; Content-Length and `unzip -t`
> clean
> > on all four (fs-s3, fs-hdfs, fs-azure, fs-gs).
> > - Shaded-dependency check on the four uber-jars: each ships unshaded
> > com/fasterxml (jackson, 1,073 entries) and unshaded com/google (guava:
> > 2,102 s3 / 2,791 hdfs / 2,102 azure / 7,411 gs). fluss-fs-s3 and
> > fluss-fs-gs contain no org.apache.fluss.fs.shaded.* package at all.
> >
> > The last point is not a blocker for RC3 — it is the known relocation gap
> > already tracked for 1.1 (#3553 is on the v1.1 milestone; #4116 and #4073
> > remain open against main). I'm recording it only so the state of the
> > artifacts I checked is on the list.
> >
> > Thanks Jark and Keith for driving this.
> >
> > Best,
> > Zhe Wang
> >
> > Jark Wu <im...@gmail.com> 于2026年9月18日周五 17:28写道：
> >
> >> Hi everyone,
> >>
> >> I'd like to start the community vote for Apache Fluss 1.0.0, release
> >> candidate 3. The RC2 was cancelled because it uses a conflict version
> >> (1.0.0) of pyfluss.
> >>
> >> The candidate artifacts are available at the following locations:
> >>
> >> Source and binary distributions, including Gateway binaries for Linux
> >> amd64 and arm64:
> >> https://dist.apache.org/repos/dist/dev/fluss/fluss-1.0.0-rc3/
> >>
> >> Helm chart:
> >> https://dist.apache.org/repos/dist/dev/fluss/helm-chart/1.0.0-rc3/
> >>
> >> When testing the chart, please override the image tag with --set
> >> image.tag=1.0.0-rc3.
> >>
> >> Maven staging repository:
> >> https://repository.apache.org/content/repositories/orgapachefluss-1016/
> >>
> >> Python client (pyfluss 1.0.0rc3) on TestPyPI:
> >> https://test.pypi.org/project/pyfluss/1.0.0rc3/
> >>
> >> Git tag:
> >> https://github.com/apache/fluss/releases/tag/v1.0.0-rc3
> >>
> >> Git commit:
> >>
> >>
> https://github.com/apache/fluss/commit/5c07f88e50a8ff41b0ebc214a0458e5dba60be37
> >>
> >> Signing key fingerprint:
> >> E2C45417BED5C104154F341085BACB5AEFAE3202
> >>
> >> The public key is available in the KEYS file:
> >> https://dist.apache.org/repos/dist/release/fluss/KEYS
> >>
> >> The following Docker images are available for testing:
> >> - apache/fluss:1.0.0-rc3
> >> - apache/fluss-gateway:1.0.0-rc3
> >> - apache/fluss-quickstart-flink:1.20-1.0.0-rc3
> >>
> >> Release announcement draft:
> >> https://github.com/apache/fluss-blog/pull/15
> >>
> >> Download link update:
> >> https://github.com/apache/fluss/pull/4418
> >>
> >> Upgrade notes:
> >>
> >>
> https://github.com/apache/fluss/blob/release-1.0/website/docs/maintenance/operations/upgrade-notes-1.0.md
> >>
> >> Please try the candidate and include the checks you performed with
> >> your vote. The verification guide covers signatures, checksums,
> >> builds, licenses, and functional testing:
> >>
> >>
> https://fluss.apache.org/community/how-to-release/verifying-a-fluss-release/
> >>
> >> Please reply with your vote:
> >>
> >> [ ] +1: Support releasing this candidate
> >> [ ] -1: Oppose releasing this candidate (please explain the issues)
> >>
> >> Voting will remain open for a minimum of 72 hours. Approval requires a
> >> majority in favor, including at least three binding +1 votes from PMC
> >> members. Votes and testing feedback from all community members are
> >> welcome.
> >>
> >> Thanks,
> >> Jark & Keith
> >>
>
>
Re: [VOTE] Release Apache Fluss 1.0.0 (RC3)
Posted by Prajwal Banakar <pr...@gmail.com>.
+1 (non-binding)
I have verified the release candidate with the following environment and
checks:
Environment:
- System: Ubuntu 24.04 (WSL2)
- JDK: 11
Checks:
- [PASS] Verified GPG signatures for fluss-1.0.0-src.tgz and
fluss-1.0.0-bin.tgz against key E2C45417BED5C104154F341085BACB5AEFAE3202
(Jark Wu)
- [PASS] Verified SHA-512 checksums for both archives
- [PASS] Built successfully from source using ./mvnw clean package
-DskipTests
- [PASS] Ran the Real-Time Page User Profile quickstart end-to-end using
apache/fluss:1.0.0-rc3 and apache/fluss-quickstart-flink:1.20-1.0.0-rc3,
confirming all roll-up queries (by channel, city, and channel+date)
Thanks Jark and Keith for driving the 1.0.0 release!
Best regards,
Prajwal Banakar
On Sun, 20 Sept 2026 at 15:18, Junbo Wang <be...@gmail.com> wrote:
> +1 (non-binding)
>
> I verified:
> - Signatures and SHA-512 checksums for the source, Java binary, both
> Gateway binaries, and Helm artifacts.
> - Git tag signature and commit. Source files match the tag except that
> CLAUDE.md is packaged as a regular file instead of a symlink.
> - Java binary LICENSE/NOTICE, JDK 11 startup, read/write operations, and
> data recovery after a clean cluster restart.
> - Coordinator failover, KV full scans, column-statistics filtering, and
> multi-table subscriptions.
> - Maven source build with -DskipTests; Gateway Rust 1.88 build and 192
> tests passed, with 1 ignored.
> - Local arm64 RC3 images: Gateway smoke tests, plaintext/SASL writes, and
> Flink 1.20 read-back and non-primary-key UPDATE/DELETE.
> - Helm provenance, lint, and template rendering.
>
> Thanks, Jark and Keith, for driving the 1.0 release!
>
> Best regards,
> Junbo Wang
>
> > On 20 Sep 2026, at 16:09, Zhe Wang <ja...@gmail.com> wrote:
> >
> > +1 (non-binding)
> >
> > Checks I ran against the Maven staging repository (orgapachefluss-1016),
> > on the filesystem plugin uber-jars:
> >
> > - Signatures: fluss-fs-s3-1.0.0.jar and fluss-fs-gs-1.0.0.jar both
> verify as
> > Good signature from E2C45417BED5C104154F341085BACB5AEFAE3202 (Jark Wu),
> > key imported from dist/release/fluss/KEYS.
> > - Checksums: md5 matches for both jars; Content-Length and `unzip -t`
> clean
> > on all four (fs-s3, fs-hdfs, fs-azure, fs-gs).
> > - Shaded-dependency check on the four uber-jars: each ships unshaded
> > com/fasterxml (jackson, 1,073 entries) and unshaded com/google (guava:
> > 2,102 s3 / 2,791 hdfs / 2,102 azure / 7,411 gs). fluss-fs-s3 and
> > fluss-fs-gs contain no org.apache.fluss.fs.shaded.* package at all.
> >
> > The last point is not a blocker for RC3 — it is the known relocation gap
> > already tracked for 1.1 (#3553 is on the v1.1 milestone; #4116 and #4073
> > remain open against main). I'm recording it only so the state of the
> > artifacts I checked is on the list.
> >
> > Thanks Jark and Keith for driving this.
> >
> > Best,
> > Zhe Wang
> >
> > Jark Wu <im...@gmail.com> 于2026年9月18日周五 17:28写道：
> >
> >> Hi everyone,
> >>
> >> I'd like to start the community vote for Apache Fluss 1.0.0, release
> >> candidate 3. The RC2 was cancelled because it uses a conflict version
> >> (1.0.0) of pyfluss.
> >>
> >> The candidate artifacts are available at the following locations:
> >>
> >> Source and binary distributions, including Gateway binaries for Linux
> >> amd64 and arm64:
> >> https://dist.apache.org/repos/dist/dev/fluss/fluss-1.0.0-rc3/
> >>
> >> Helm chart:
> >> https://dist.apache.org/repos/dist/dev/fluss/helm-chart/1.0.0-rc3/
> >>
> >> When testing the chart, please override the image tag with --set
> >> image.tag=1.0.0-rc3.
> >>
> >> Maven staging repository:
> >> https://repository.apache.org/content/repositories/orgapachefluss-1016/
> >>
> >> Python client (pyfluss 1.0.0rc3) on TestPyPI:
> >> https://test.pypi.org/project/pyfluss/1.0.0rc3/
> >>
> >> Git tag:
> >> https://github.com/apache/fluss/releases/tag/v1.0.0-rc3
> >>
> >> Git commit:
> >>
> >>
> https://github.com/apache/fluss/commit/5c07f88e50a8ff41b0ebc214a0458e5dba60be37
> >>
> >> Signing key fingerprint:
> >> E2C45417BED5C104154F341085BACB5AEFAE3202
> >>
> >> The public key is available in the KEYS file:
> >> https://dist.apache.org/repos/dist/release/fluss/KEYS
> >>
> >> The following Docker images are available for testing:
> >> - apache/fluss:1.0.0-rc3
> >> - apache/fluss-gateway:1.0.0-rc3
> >> - apache/fluss-quickstart-flink:1.20-1.0.0-rc3
> >>
> >> Release announcement draft:
> >> https://github.com/apache/fluss-blog/pull/15
> >>
> >> Download link update:
> >> https://github.com/apache/fluss/pull/4418
> >>
> >> Upgrade notes:
> >>
> >>
> https://github.com/apache/fluss/blob/release-1.0/website/docs/maintenance/operations/upgrade-notes-1.0.md
> >>
> >> Please try the candidate and include the checks you performed with
> >> your vote. The verification guide covers signatures, checksums,
> >> builds, licenses, and functional testing:
> >>
> >>
> https://fluss.apache.org/community/how-to-release/verifying-a-fluss-release/
> >>
> >> Please reply with your vote:
> >>
> >> [ ] +1: Support releasing this candidate
> >> [ ] -1: Oppose releasing this candidate (please explain the issues)
> >>
> >> Voting will remain open for a minimum of 72 hours. Approval requires a
> >> majority in favor, including at least three binding +1 votes from PMC
> >> members. Votes and testing feedback from all community members are
> >> welcome.
> >>
> >> Thanks,
> >> Jark & Keith
> >>
>
>
Re: [VOTE] Release Apache Fluss 1.0.0 (RC3)
Posted by Junbo Wang <be...@gmail.com>.
+1 (non-binding)
I verified:
- Signatures and SHA-512 checksums for the source, Java binary, both Gateway binaries, and Helm artifacts.
- Git tag signature and commit. Source files match the tag except that CLAUDE.md is packaged as a regular file instead of a symlink.
- Java binary LICENSE/NOTICE, JDK 11 startup, read/write operations, and data recovery after a clean cluster restart.
- Coordinator failover, KV full scans, column-statistics filtering, and multi-table subscriptions.
- Maven source build with -DskipTests; Gateway Rust 1.88 build and 192 tests passed, with 1 ignored.
- Local arm64 RC3 images: Gateway smoke tests, plaintext/SASL writes, and Flink 1.20 read-back and non-primary-key UPDATE/DELETE.
- Helm provenance, lint, and template rendering.
Thanks, Jark and Keith, for driving the 1.0 release!
Best regards,
Junbo Wang
> On 20 Sep 2026, at 16:09, Zhe Wang <ja...@gmail.com> wrote:
>
> +1 (non-binding)
>
> Checks I ran against the Maven staging repository (orgapachefluss-1016),
> on the filesystem plugin uber-jars:
>
> - Signatures: fluss-fs-s3-1.0.0.jar and fluss-fs-gs-1.0.0.jar both verify as
> Good signature from E2C45417BED5C104154F341085BACB5AEFAE3202 (Jark Wu),
> key imported from dist/release/fluss/KEYS.
> - Checksums: md5 matches for both jars; Content-Length and `unzip -t` clean
> on all four (fs-s3, fs-hdfs, fs-azure, fs-gs).
> - Shaded-dependency check on the four uber-jars: each ships unshaded
> com/fasterxml (jackson, 1,073 entries) and unshaded com/google (guava:
> 2,102 s3 / 2,791 hdfs / 2,102 azure / 7,411 gs). fluss-fs-s3 and
> fluss-fs-gs contain no org.apache.fluss.fs.shaded.* package at all.
>
> The last point is not a blocker for RC3 — it is the known relocation gap
> already tracked for 1.1 (#3553 is on the v1.1 milestone; #4116 and #4073
> remain open against main). I'm recording it only so the state of the
> artifacts I checked is on the list.
>
> Thanks Jark and Keith for driving this.
>
> Best,
> Zhe Wang
>
> Jark Wu <im...@gmail.com> 于2026年9月18日周五 17:28写道：
>
>> Hi everyone,
>>
>> I'd like to start the community vote for Apache Fluss 1.0.0, release
>> candidate 3. The RC2 was cancelled because it uses a conflict version
>> (1.0.0) of pyfluss.
>>
>> The candidate artifacts are available at the following locations:
>>
>> Source and binary distributions, including Gateway binaries for Linux
>> amd64 and arm64:
>> https://dist.apache.org/repos/dist/dev/fluss/fluss-1.0.0-rc3/
>>
>> Helm chart:
>> https://dist.apache.org/repos/dist/dev/fluss/helm-chart/1.0.0-rc3/
>>
>> When testing the chart, please override the image tag with --set
>> image.tag=1.0.0-rc3.
>>
>> Maven staging repository:
>> https://repository.apache.org/content/repositories/orgapachefluss-1016/
>>
>> Python client (pyfluss 1.0.0rc3) on TestPyPI:
>> https://test.pypi.org/project/pyfluss/1.0.0rc3/
>>
>> Git tag:
>> https://github.com/apache/fluss/releases/tag/v1.0.0-rc3
>>
>> Git commit:
>>
>> https://github.com/apache/fluss/commit/5c07f88e50a8ff41b0ebc214a0458e5dba60be37
>>
>> Signing key fingerprint:
>> E2C45417BED5C104154F341085BACB5AEFAE3202
>>
>> The public key is available in the KEYS file:
>> https://dist.apache.org/repos/dist/release/fluss/KEYS
>>
>> The following Docker images are available for testing:
>> - apache/fluss:1.0.0-rc3
>> - apache/fluss-gateway:1.0.0-rc3
>> - apache/fluss-quickstart-flink:1.20-1.0.0-rc3
>>
>> Release announcement draft:
>> https://github.com/apache/fluss-blog/pull/15
>>
>> Download link update:
>> https://github.com/apache/fluss/pull/4418
>>
>> Upgrade notes:
>>
>> https://github.com/apache/fluss/blob/release-1.0/website/docs/maintenance/operations/upgrade-notes-1.0.md
>>
>> Please try the candidate and include the checks you performed with
>> your vote. The verification guide covers signatures, checksums,
>> builds, licenses, and functional testing:
>>
>> https://fluss.apache.org/community/how-to-release/verifying-a-fluss-release/
>>
>> Please reply with your vote:
>>
>> [ ] +1: Support releasing this candidate
>> [ ] -1: Oppose releasing this candidate (please explain the issues)
>>
>> Voting will remain open for a minimum of 72 hours. Approval requires a
>> majority in favor, including at least three binding +1 votes from PMC
>> members. Votes and testing feedback from all community members are
>> welcome.
>>
>> Thanks,
>> Jark & Keith
>>
Re: [VOTE] Release Apache Fluss 1.0.0 (RC3)
Posted by Jark Wu <im...@gmail.com>.
Hi everyone,
The 72-hour voting period has ended, and the vote is now closed.
I will send the vote result in a separate email shortly.
Thanks everyone for reviewing and testing RC3!
Best,
Jark
On Mon, 21 Sept 2026 at 17:55, Zhe Wang <ja...@gmail.com> wrote:
>
> A small correction to one line in my +1 yesterday, so the permanent record
> is right.
>
> I wrote that "fluss-fs-s3 and fluss-fs-gs contain no
> org.apache.fluss.fs.shaded.* package at all".
> The count is literally 0, but the implication I left sitting there — that
> those two modules have
> no relocation configured — is wrong. All four fs plugin poms (s3 / gs /
> hdfs / azure) currently
> carry one and the same relocation, org.apache.commons ->
> org.apache.fluss.shaded.org.apache.commons
> (added in #3960), and it is doing its job: each of the four jars has
> 2,794-2,804 entries under
> org/apache/fluss/shaded/ and zero entries left unshaded under
> org/apache/commons/. The
> org.apache.fluss.fs.shaded.hadoop3.* prefix I grepped for comes from the
> pre-shaded
> fluss-fs-hadoop-shaded artifact that these plugins depend on, which is why
> it only shows up in
> fs-hdfs and fs-azure.
>
> Nothing else changes: com.fasterxml (1,073 entries per jar) and com.google
> are
> still bundled unrelocated in all four jars, which is what #4116 tracks and
> what
> #4073 is scoped to fix. My +1 stands unchanged.
>
> Sorry for the noise.
>
> Best regards,
> Zhe Wang
>
>
> Zhe Wang <ja...@gmail.com> 于2026年9月20日周日 16:09写道：
>
> > +1 (non-binding)
> >
> > Checks I ran against the Maven staging repository (orgapachefluss-1016),
> > on the filesystem plugin uber-jars:
> >
> > - Signatures: fluss-fs-s3-1.0.0.jar and fluss-fs-gs-1.0.0.jar both verify
> > as
> > Good signature from E2C45417BED5C104154F341085BACB5AEFAE3202 (Jark Wu),
> > key imported from dist/release/fluss/KEYS.
> > - Checksums: md5 matches for both jars; Content-Length and `unzip -t` clean
> > on all four (fs-s3, fs-hdfs, fs-azure, fs-gs).
> > - Shaded-dependency check on the four uber-jars: each ships unshaded
> > com/fasterxml (jackson, 1,073 entries) and unshaded com/google (guava:
> > 2,102 s3 / 2,791 hdfs / 2,102 azure / 7,411 gs). fluss-fs-s3 and
> > fluss-fs-gs contain no org.apache.fluss.fs.shaded.* package at all.
> >
> > The last point is not a blocker for RC3 — it is the known relocation gap
> > already tracked for 1.1 (#3553 is on the v1.1 milestone; #4116 and #4073
> > remain open against main). I'm recording it only so the state of the
> > artifacts I checked is on the list.
> >
> > Thanks Jark and Keith for driving this.
> >
> > Best,
> > Zhe Wang
> >
> > Jark Wu <im...@gmail.com> 于2026年9月18日周五 17:28写道：
> >
> >> Hi everyone,
> >>
> >> I'd like to start the community vote for Apache Fluss 1.0.0, release
> >> candidate 3. The RC2 was cancelled because it uses a conflict version
> >> (1.0.0) of pyfluss.
> >>
> >> The candidate artifacts are available at the following locations:
> >>
> >> Source and binary distributions, including Gateway binaries for Linux
> >> amd64 and arm64:
> >> https://dist.apache.org/repos/dist/dev/fluss/fluss-1.0.0-rc3/
> >>
> >> Helm chart:
> >> https://dist.apache.org/repos/dist/dev/fluss/helm-chart/1.0.0-rc3/
> >>
> >> When testing the chart, please override the image tag with --set
> >> image.tag=1.0.0-rc3.
> >>
> >> Maven staging repository:
> >> https://repository.apache.org/content/repositories/orgapachefluss-1016/
> >>
> >> Python client (pyfluss 1.0.0rc3) on TestPyPI:
> >> https://test.pypi.org/project/pyfluss/1.0.0rc3/
> >>
> >> Git tag:
> >> https://github.com/apache/fluss/releases/tag/v1.0.0-rc3
> >>
> >> Git commit:
> >>
> >> https://github.com/apache/fluss/commit/5c07f88e50a8ff41b0ebc214a0458e5dba60be37
> >>
> >> Signing key fingerprint:
> >> E2C45417BED5C104154F341085BACB5AEFAE3202
> >>
> >> The public key is available in the KEYS file:
> >> https://dist.apache.org/repos/dist/release/fluss/KEYS
> >>
> >> The following Docker images are available for testing:
> >> - apache/fluss:1.0.0-rc3
> >> - apache/fluss-gateway:1.0.0-rc3
> >> - apache/fluss-quickstart-flink:1.20-1.0.0-rc3
> >>
> >> Release announcement draft:
> >> https://github.com/apache/fluss-blog/pull/15
> >>
> >> Download link update:
> >> https://github.com/apache/fluss/pull/4418
> >>
> >> Upgrade notes:
> >>
> >> https://github.com/apache/fluss/blob/release-1.0/website/docs/maintenance/operations/upgrade-notes-1.0.md
> >>
> >> Please try the candidate and include the checks you performed with
> >> your vote. The verification guide covers signatures, checksums,
> >> builds, licenses, and functional testing:
> >>
> >> https://fluss.apache.org/community/how-to-release/verifying-a-fluss-release/
> >>
> >> Please reply with your vote:
> >>
> >> [ ] +1: Support releasing this candidate
> >> [ ] -1: Oppose releasing this candidate (please explain the issues)
> >>
> >> Voting will remain open for a minimum of 72 hours. Approval requires a
> >> majority in favor, including at least three binding +1 votes from PMC
> >> members. Votes and testing feedback from all community members are
> >> welcome.
> >>
> >> Thanks,
> >> Jark & Keith
> >>
> >
Re: [VOTE] Release Apache Fluss 1.0.0 (RC3)
Posted by Zhe Wang <ja...@gmail.com>.
A small correction to one line in my +1 yesterday, so the permanent record
is right.
I wrote that "fluss-fs-s3 and fluss-fs-gs contain no
org.apache.fluss.fs.shaded.* package at all".
The count is literally 0, but the implication I left sitting there — that
those two modules have
no relocation configured — is wrong. All four fs plugin poms (s3 / gs /
hdfs / azure) currently
carry one and the same relocation, org.apache.commons ->
org.apache.fluss.shaded.org.apache.commons
(added in #3960), and it is doing its job: each of the four jars has
2,794-2,804 entries under
org/apache/fluss/shaded/ and zero entries left unshaded under
org/apache/commons/. The
org.apache.fluss.fs.shaded.hadoop3.* prefix I grepped for comes from the
pre-shaded
fluss-fs-hadoop-shaded artifact that these plugins depend on, which is why
it only shows up in
fs-hdfs and fs-azure.
Nothing else changes: com.fasterxml (1,073 entries per jar) and com.google
are
still bundled unrelocated in all four jars, which is what #4116 tracks and
what
#4073 is scoped to fix. My +1 stands unchanged.
Sorry for the noise.
Best regards,
Zhe Wang
Zhe Wang <ja...@gmail.com> 于2026年9月20日周日 16:09写道：
> +1 (non-binding)
>
> Checks I ran against the Maven staging repository (orgapachefluss-1016),
> on the filesystem plugin uber-jars:
>
> - Signatures: fluss-fs-s3-1.0.0.jar and fluss-fs-gs-1.0.0.jar both verify
> as
> Good signature from E2C45417BED5C104154F341085BACB5AEFAE3202 (Jark Wu),
> key imported from dist/release/fluss/KEYS.
> - Checksums: md5 matches for both jars; Content-Length and `unzip -t` clean
> on all four (fs-s3, fs-hdfs, fs-azure, fs-gs).
> - Shaded-dependency check on the four uber-jars: each ships unshaded
> com/fasterxml (jackson, 1,073 entries) and unshaded com/google (guava:
> 2,102 s3 / 2,791 hdfs / 2,102 azure / 7,411 gs). fluss-fs-s3 and
> fluss-fs-gs contain no org.apache.fluss.fs.shaded.* package at all.
>
> The last point is not a blocker for RC3 — it is the known relocation gap
> already tracked for 1.1 (#3553 is on the v1.1 milestone; #4116 and #4073
> remain open against main). I'm recording it only so the state of the
> artifacts I checked is on the list.
>
> Thanks Jark and Keith for driving this.
>
> Best,
> Zhe Wang
>
> Jark Wu <im...@gmail.com> 于2026年9月18日周五 17:28写道：
>
>> Hi everyone,
>>
>> I'd like to start the community vote for Apache Fluss 1.0.0, release
>> candidate 3. The RC2 was cancelled because it uses a conflict version
>> (1.0.0) of pyfluss.
>>
>> The candidate artifacts are available at the following locations:
>>
>> Source and binary distributions, including Gateway binaries for Linux
>> amd64 and arm64:
>> https://dist.apache.org/repos/dist/dev/fluss/fluss-1.0.0-rc3/
>>
>> Helm chart:
>> https://dist.apache.org/repos/dist/dev/fluss/helm-chart/1.0.0-rc3/
>>
>> When testing the chart, please override the image tag with --set
>> image.tag=1.0.0-rc3.
>>
>> Maven staging repository:
>> https://repository.apache.org/content/repositories/orgapachefluss-1016/
>>
>> Python client (pyfluss 1.0.0rc3) on TestPyPI:
>> https://test.pypi.org/project/pyfluss/1.0.0rc3/
>>
>> Git tag:
>> https://github.com/apache/fluss/releases/tag/v1.0.0-rc3
>>
>> Git commit:
>>
>> https://github.com/apache/fluss/commit/5c07f88e50a8ff41b0ebc214a0458e5dba60be37
>>
>> Signing key fingerprint:
>> E2C45417BED5C104154F341085BACB5AEFAE3202
>>
>> The public key is available in the KEYS file:
>> https://dist.apache.org/repos/dist/release/fluss/KEYS
>>
>> The following Docker images are available for testing:
>> - apache/fluss:1.0.0-rc3
>> - apache/fluss-gateway:1.0.0-rc3
>> - apache/fluss-quickstart-flink:1.20-1.0.0-rc3
>>
>> Release announcement draft:
>> https://github.com/apache/fluss-blog/pull/15
>>
>> Download link update:
>> https://github.com/apache/fluss/pull/4418
>>
>> Upgrade notes:
>>
>> https://github.com/apache/fluss/blob/release-1.0/website/docs/maintenance/operations/upgrade-notes-1.0.md
>>
>> Please try the candidate and include the checks you performed with
>> your vote. The verification guide covers signatures, checksums,
>> builds, licenses, and functional testing:
>>
>> https://fluss.apache.org/community/how-to-release/verifying-a-fluss-release/
>>
>> Please reply with your vote:
>>
>> [ ] +1: Support releasing this candidate
>> [ ] -1: Oppose releasing this candidate (please explain the issues)
>>
>> Voting will remain open for a minimum of 72 hours. Approval requires a
>> majority in favor, including at least three binding +1 votes from PMC
>> members. Votes and testing feedback from all community members are
>> welcome.
>>
>> Thanks,
>> Jark & Keith
>>
>
Re: [VOTE] Release Apache Fluss 1.0.0 (RC3)
Posted by Zhe Wang <ja...@gmail.com>.
+1 (non-binding)
Checks I ran against the Maven staging repository (orgapachefluss-1016),
on the filesystem plugin uber-jars:
- Signatures: fluss-fs-s3-1.0.0.jar and fluss-fs-gs-1.0.0.jar both verify as
Good signature from E2C45417BED5C104154F341085BACB5AEFAE3202 (Jark Wu),
key imported from dist/release/fluss/KEYS.
- Checksums: md5 matches for both jars; Content-Length and `unzip -t` clean
on all four (fs-s3, fs-hdfs, fs-azure, fs-gs).
- Shaded-dependency check on the four uber-jars: each ships unshaded
com/fasterxml (jackson, 1,073 entries) and unshaded com/google (guava:
2,102 s3 / 2,791 hdfs / 2,102 azure / 7,411 gs). fluss-fs-s3 and
fluss-fs-gs contain no org.apache.fluss.fs.shaded.* package at all.
The last point is not a blocker for RC3 — it is the known relocation gap
already tracked for 1.1 (#3553 is on the v1.1 milestone; #4116 and #4073
remain open against main). I'm recording it only so the state of the
artifacts I checked is on the list.
Thanks Jark and Keith for driving this.
Best,
Zhe Wang
Jark Wu <im...@gmail.com> 于2026年9月18日周五 17:28写道：
> Hi everyone,
>
> I'd like to start the community vote for Apache Fluss 1.0.0, release
> candidate 3. The RC2 was cancelled because it uses a conflict version
> (1.0.0) of pyfluss.
>
> The candidate artifacts are available at the following locations:
>
> Source and binary distributions, including Gateway binaries for Linux
> amd64 and arm64:
> https://dist.apache.org/repos/dist/dev/fluss/fluss-1.0.0-rc3/
>
> Helm chart:
> https://dist.apache.org/repos/dist/dev/fluss/helm-chart/1.0.0-rc3/
>
> When testing the chart, please override the image tag with --set
> image.tag=1.0.0-rc3.
>
> Maven staging repository:
> https://repository.apache.org/content/repositories/orgapachefluss-1016/
>
> Python client (pyfluss 1.0.0rc3) on TestPyPI:
> https://test.pypi.org/project/pyfluss/1.0.0rc3/
>
> Git tag:
> https://github.com/apache/fluss/releases/tag/v1.0.0-rc3
>
> Git commit:
>
> https://github.com/apache/fluss/commit/5c07f88e50a8ff41b0ebc214a0458e5dba60be37
>
> Signing key fingerprint:
> E2C45417BED5C104154F341085BACB5AEFAE3202
>
> The public key is available in the KEYS file:
> https://dist.apache.org/repos/dist/release/fluss/KEYS
>
> The following Docker images are available for testing:
> - apache/fluss:1.0.0-rc3
> - apache/fluss-gateway:1.0.0-rc3
> - apache/fluss-quickstart-flink:1.20-1.0.0-rc3
>
> Release announcement draft:
> https://github.com/apache/fluss-blog/pull/15
>
> Download link update:
> https://github.com/apache/fluss/pull/4418
>
> Upgrade notes:
>
> https://github.com/apache/fluss/blob/release-1.0/website/docs/maintenance/operations/upgrade-notes-1.0.md
>
> Please try the candidate and include the checks you performed with
> your vote. The verification guide covers signatures, checksums,
> builds, licenses, and functional testing:
>
> https://fluss.apache.org/community/how-to-release/verifying-a-fluss-release/
>
> Please reply with your vote:
>
> [ ] +1: Support releasing this candidate
> [ ] -1: Oppose releasing this candidate (please explain the issues)
>
> Voting will remain open for a minimum of 72 hours. Approval requires a
> majority in favor, including at least three binding +1 votes from PMC
> members. Votes and testing feedback from all community members are
> welcome.
>
> Thanks,
> Jark & Keith
>
Re: [VOTE] Release Apache Fluss 1.0.0 (RC3)
Posted by yuxia <lu...@alumni.sjtu.edu.cn>.
Hi Jark and Keith,
Thanks for your work on the 1.0.0 release!
+1 (binding)
I completed the following checks for RC3:
- [PASS] Built and compiled Java with Temurin 11.0.26 and Maven 3.9.9,
Rust with rustc/Cargo 1.96.0
- [PASS] Verified the SHA-512 checksums, GPG signatures, and release tag
- [PASS] Verified the source archive contents against the release tag
- [PASS] Verified the staged Maven client and TestPyPI package
- [PASS] Completed the official Docker Compose quickstarts: lakehouse-paimon, lakehouse-iceberg, gateway
- [PASS] Verified the feature of historical partition write & lookup with local fluss-1.0.0-rc3 cluster
- [PASS] Verified rust client write/read data with local fluss-1.0.0-rc3 cluster
- [PASS] Reviewed Upgrade notes and Release announcement draft
Best regards,
Yuxia
----- 原始邮件 -----
发件人: "Nicholas Jiang" <ni...@apache.org>
收件人: "dev" <de...@fluss.apache.org>
发送时间: 星期日, 2026年 9 月 20日 下午 1:37:33
主题: Re: [VOTE] Release Apache Fluss 1.0.0 (RC3)
Hi Jark and Keith,
Thanks for your work on the 1.0.0 release!
+1 (binding)
I completed the following checks for RC3:
- [PASS] Checked that all expected artifacts are present in Maven staging.
- [PASS] Checked the Gateway distributions, Docker image manifests, and Helm chart.
- [PASS] Confirmed that the source distribution matches the tagged source.
- [PASS] Reviewed the relevant LICENSE and NOTICE files.
- [PASS] Successfully built the Java components using Temurin 11.0.28, and Maven 3.8.5, the Rust components using rustc/Cargo 1.98.1, and the C++ client using Bazel 9.2.0.
- [PASS] Successfully ran the Docker Compose examples for Flink analytics, Paimon and Iceberg lakehouses, Gateway, and real-time user profiles.
- [PASS] Tested the Maven client from the staging repository and the Python package from TestPyPI.
- [PASS] Validated the artifact checksums and signatures, and checked the release tag.
- [PASS] Walked through the quickstart and exercised client reads and writes.
I did not encounter any additional release-blocking issues during testing.
Best,
Nicholas Jiang
On 2026/09/20 03:02:09 Jark Wu wrote:
> +1 (binding)
>
> - [PASS] Built and compiled Java with Temurin 11.0.28 and Maven 3.8.6,
> Rust with rustc/Cargo 1.98.1, and C++ with Bazel 9.2.0
> - [PASS] Verified the SHA-512 checksums, GPG signatures, and release tag
> - [PASS] Verified the source archive contents against the release tag
> - [PASS] Confirmed that no Maven staging artifacts were missing
> - [PASS] Verified the staged Maven client and TestPyPI package
> - [PASS] Completed the quick start and client read/write workflow
> - [PASS] Completed the official Docker Compose quickstarts:
> real-time-analytics-flink, lakehouse-paimon, lakehouse-iceberg,
> gateway, and real-time-user-profile
> - [PASS] Verified the Gateway artifacts, Docker manifests, and Helm chart
> - [PASS] Checked the applicable LICENSE and NOTICE files
>
> Non-blocking documentation issue:
>
> - The real-time-user-profile quickstart may produce UV = PV because
> its Faker email expression generates a much larger user population
> than documented: https://github.com/apache/fluss/issues/4429
>
> Best,
> Jark
>
> On Fri, 18 Sept 2026 at 19:58, Muhammet Orazov via dev
> <de...@fluss.apache.org> wrote:
> >
> > Hello all,
> >
> > +1 (non-binding)
> >
> > - Signatures:
> >
> > The tarball artifacts and both Helm files are signed by
> > E2C45417BED5C104154F341085BACB5AEFAE3202 (Jark Wu). All .sha512 OK.
> >
> > - Source Release
> >
> > The tarball does not .github, .gitignore, .idea, website/ and any
> > bundled binaries. The pom file declares 1.0.0.
> >
> > - Build
> >
> > I run `mvn clean package -DskipTests` command with JDK 11, it builds
> > successfully.
> >
> > - Helm Chart
> >
> > Looks fine, packages of the source helm/, the version and appVersion
> > 1.0.0, and it references apache/fluss:1.0.0-rc3.
> >
> > - Maven Staging
> >
> > I built local project against orgapachefluss-1016 and ran write/read
> > cycles with it.
> >
> > - Test
> >
> > I run fluss clients against a local cluster from the binary
> > distribution: Java (5000 rows through both a primary-key and a log
> > table), Rust (example-table and example-upsert-lookup), and pyfluss
> > 1.0.0rc3 from TestPyPI (upsert, lookup, delete, bucket scan, 500-row
> > append and log scan).
> >
> > **Again question on LICENSE / NOTICE files in docker images**:
> >
> > - The `apache/fluss:1.0.0-rc3` docker image has no LICENSE or NOTICE
> > under /opt/fluss
> > - But `apache/fluss-gateway:1.0.0-rc3` docker image contains
> > /opt/fluss/LICENSE and /opt/fluss/NOTICE files
> >
> > Should also the `apache/fluss:1.0.0-rc` image add LICENSE and NOTICE
> > files under `/opt/fluss` ?
> >
> > Best,
> > Muhammet Orazov
>
Re: [VOTE] Release Apache Fluss 1.0.0 (RC3)
Posted by Nicholas Jiang <ni...@apache.org>.
Hi Jark and Keith,
Thanks for your work on the 1.0.0 release!
+1 (binding)
I completed the following checks for RC3:
- [PASS] Checked that all expected artifacts are present in Maven staging.
- [PASS] Checked the Gateway distributions, Docker image manifests, and Helm chart.
- [PASS] Confirmed that the source distribution matches the tagged source.
- [PASS] Reviewed the relevant LICENSE and NOTICE files.
- [PASS] Successfully built the Java components using Temurin 11.0.28, and Maven 3.8.5, the Rust components using rustc/Cargo 1.98.1, and the C++ client using Bazel 9.2.0.
- [PASS] Successfully ran the Docker Compose examples for Flink analytics, Paimon and Iceberg lakehouses, Gateway, and real-time user profiles.
- [PASS] Tested the Maven client from the staging repository and the Python package from TestPyPI.
- [PASS] Validated the artifact checksums and signatures, and checked the release tag.
- [PASS] Walked through the quickstart and exercised client reads and writes.
I did not encounter any additional release-blocking issues during testing.
Best,
Nicholas Jiang
On 2026/09/20 03:02:09 Jark Wu wrote:
> +1 (binding)
>
> - [PASS] Built and compiled Java with Temurin 11.0.28 and Maven 3.8.6,
> Rust with rustc/Cargo 1.98.1, and C++ with Bazel 9.2.0
> - [PASS] Verified the SHA-512 checksums, GPG signatures, and release tag
> - [PASS] Verified the source archive contents against the release tag
> - [PASS] Confirmed that no Maven staging artifacts were missing
> - [PASS] Verified the staged Maven client and TestPyPI package
> - [PASS] Completed the quick start and client read/write workflow
> - [PASS] Completed the official Docker Compose quickstarts:
> real-time-analytics-flink, lakehouse-paimon, lakehouse-iceberg,
> gateway, and real-time-user-profile
> - [PASS] Verified the Gateway artifacts, Docker manifests, and Helm chart
> - [PASS] Checked the applicable LICENSE and NOTICE files
>
> Non-blocking documentation issue:
>
> - The real-time-user-profile quickstart may produce UV = PV because
> its Faker email expression generates a much larger user population
> than documented: https://github.com/apache/fluss/issues/4429
>
> Best,
> Jark
>
> On Fri, 18 Sept 2026 at 19:58, Muhammet Orazov via dev
> <de...@fluss.apache.org> wrote:
> >
> > Hello all,
> >
> > +1 (non-binding)
> >
> > - Signatures:
> >
> > The tarball artifacts and both Helm files are signed by
> > E2C45417BED5C104154F341085BACB5AEFAE3202 (Jark Wu). All .sha512 OK.
> >
> > - Source Release
> >
> > The tarball does not .github, .gitignore, .idea, website/ and any
> > bundled binaries. The pom file declares 1.0.0.
> >
> > - Build
> >
> > I run `mvn clean package -DskipTests` command with JDK 11, it builds
> > successfully.
> >
> > - Helm Chart
> >
> > Looks fine, packages of the source helm/, the version and appVersion
> > 1.0.0, and it references apache/fluss:1.0.0-rc3.
> >
> > - Maven Staging
> >
> > I built local project against orgapachefluss-1016 and ran write/read
> > cycles with it.
> >
> > - Test
> >
> > I run fluss clients against a local cluster from the binary
> > distribution: Java (5000 rows through both a primary-key and a log
> > table), Rust (example-table and example-upsert-lookup), and pyfluss
> > 1.0.0rc3 from TestPyPI (upsert, lookup, delete, bucket scan, 500-row
> > append and log scan).
> >
> > **Again question on LICENSE / NOTICE files in docker images**:
> >
> > - The `apache/fluss:1.0.0-rc3` docker image has no LICENSE or NOTICE
> > under /opt/fluss
> > - But `apache/fluss-gateway:1.0.0-rc3` docker image contains
> > /opt/fluss/LICENSE and /opt/fluss/NOTICE files
> >
> > Should also the `apache/fluss:1.0.0-rc` image add LICENSE and NOTICE
> > files under `/opt/fluss` ?
> >
> > Best,
> > Muhammet Orazov
>
Re: [VOTE] Release Apache Fluss 1.0.0 (RC3)
Posted by Giannis Polyzos <ip...@gmail.com>.
Hi Jark, Keith, and all
Thank you for all the work on the release
+1 (binding)
- [PASS] Built and compiled Java 11
- [PASS] Verified the checksums and signatures, and the release tag
- [PASS] Verified the source archive contents against the release tag
- [PASS] Checked the applicable LICENSE and NOTICE files
- [PASS] Verified Full KV Scan - Both with Flink SQL and Java Client
- [PASS] Verified Multi-Subscriptions
- [PASS] Predicate Pushdowns - Both with Flink SQL and Java Client
Best,
Giannis
On Mon, Sep 21, 2026 at 10:38 AM Muhammet Orazov via dev <
dev@fluss.apache.org> wrote:
> Hello Jark,
>
> All good! Thanks, yes definitely it doesn't block the 1.0 release.
>
> Best,
> Muhammet Orazov
>
Re: [VOTE] Release Apache Fluss 1.0.0 (RC3)
Posted by Muhammet Orazov via dev <de...@fluss.apache.org>.
Hello Jark,
All good! Thanks, yes definitely it doesn't block the 1.0 release.
Best,
Muhammet Orazov
Re: [VOTE] Release Apache Fluss 1.0.0 (RC3)
Posted by Jark Wu <im...@gmail.com>.
Hi Muhammet,
I think we should also include the LICENSE and NOTICE files in the
`apache/fluss` images. However, I do not consider this a blocker, as
the previous 0.9.0 and 0.9.1 images also lacked these files. I have
already created an issue and PRs to address this
(https://github.com/apache/fluss/issues/4426,
https://github.com/apache/fluss/pull/4427), so that future images will
include them.
Best,
Jark
On Sun, 20 Sept 2026 at 11:02, Jark Wu <im...@gmail.com> wrote:
>
> +1 (binding)
>
> - [PASS] Built and compiled Java with Temurin 11.0.28 and Maven 3.8.6,
> Rust with rustc/Cargo 1.98.1, and C++ with Bazel 9.2.0
> - [PASS] Verified the SHA-512 checksums, GPG signatures, and release tag
> - [PASS] Verified the source archive contents against the release tag
> - [PASS] Confirmed that no Maven staging artifacts were missing
> - [PASS] Verified the staged Maven client and TestPyPI package
> - [PASS] Completed the quick start and client read/write workflow
> - [PASS] Completed the official Docker Compose quickstarts:
> real-time-analytics-flink, lakehouse-paimon, lakehouse-iceberg,
> gateway, and real-time-user-profile
> - [PASS] Verified the Gateway artifacts, Docker manifests, and Helm chart
> - [PASS] Checked the applicable LICENSE and NOTICE files
>
> Non-blocking documentation issue:
>
> - The real-time-user-profile quickstart may produce UV = PV because
> its Faker email expression generates a much larger user population
> than documented: https://github.com/apache/fluss/issues/4429
>
> Best,
> Jark
>
> On Fri, 18 Sept 2026 at 19:58, Muhammet Orazov via dev
> <de...@fluss.apache.org> wrote:
> >
> > Hello all,
> >
> > +1 (non-binding)
> >
> > - Signatures:
> >
> > The tarball artifacts and both Helm files are signed by
> > E2C45417BED5C104154F341085BACB5AEFAE3202 (Jark Wu). All .sha512 OK.
> >
> > - Source Release
> >
> > The tarball does not .github, .gitignore, .idea, website/ and any
> > bundled binaries. The pom file declares 1.0.0.
> >
> > - Build
> >
> > I run `mvn clean package -DskipTests` command with JDK 11, it builds
> > successfully.
> >
> > - Helm Chart
> >
> > Looks fine, packages of the source helm/, the version and appVersion
> > 1.0.0, and it references apache/fluss:1.0.0-rc3.
> >
> > - Maven Staging
> >
> > I built local project against orgapachefluss-1016 and ran write/read
> > cycles with it.
> >
> > - Test
> >
> > I run fluss clients against a local cluster from the binary
> > distribution: Java (5000 rows through both a primary-key and a log
> > table), Rust (example-table and example-upsert-lookup), and pyfluss
> > 1.0.0rc3 from TestPyPI (upsert, lookup, delete, bucket scan, 500-row
> > append and log scan).
> >
> > **Again question on LICENSE / NOTICE files in docker images**:
> >
> > - The `apache/fluss:1.0.0-rc3` docker image has no LICENSE or NOTICE
> > under /opt/fluss
> > - But `apache/fluss-gateway:1.0.0-rc3` docker image contains
> > /opt/fluss/LICENSE and /opt/fluss/NOTICE files
> >
> > Should also the `apache/fluss:1.0.0-rc` image add LICENSE and NOTICE
> > files under `/opt/fluss` ?
> >
> > Best,
> > Muhammet Orazov
Re: [VOTE] Release Apache Fluss 1.0.0 (RC3)
Posted by Jark Wu <im...@gmail.com>.
+1 (binding)
- [PASS] Built and compiled Java with Temurin 11.0.28 and Maven 3.8.6,
Rust with rustc/Cargo 1.98.1, and C++ with Bazel 9.2.0
- [PASS] Verified the SHA-512 checksums, GPG signatures, and release tag
- [PASS] Verified the source archive contents against the release tag
- [PASS] Confirmed that no Maven staging artifacts were missing
- [PASS] Verified the staged Maven client and TestPyPI package
- [PASS] Completed the quick start and client read/write workflow
- [PASS] Completed the official Docker Compose quickstarts:
real-time-analytics-flink, lakehouse-paimon, lakehouse-iceberg,
gateway, and real-time-user-profile
- [PASS] Verified the Gateway artifacts, Docker manifests, and Helm chart
- [PASS] Checked the applicable LICENSE and NOTICE files
Non-blocking documentation issue:
- The real-time-user-profile quickstart may produce UV = PV because
its Faker email expression generates a much larger user population
than documented: https://github.com/apache/fluss/issues/4429
Best,
Jark
On Fri, 18 Sept 2026 at 19:58, Muhammet Orazov via dev
<de...@fluss.apache.org> wrote:
>
> Hello all,
>
> +1 (non-binding)
>
> - Signatures:
>
> The tarball artifacts and both Helm files are signed by
> E2C45417BED5C104154F341085BACB5AEFAE3202 (Jark Wu). All .sha512 OK.
>
> - Source Release
>
> The tarball does not .github, .gitignore, .idea, website/ and any
> bundled binaries. The pom file declares 1.0.0.
>
> - Build
>
> I run `mvn clean package -DskipTests` command with JDK 11, it builds
> successfully.
>
> - Helm Chart
>
> Looks fine, packages of the source helm/, the version and appVersion
> 1.0.0, and it references apache/fluss:1.0.0-rc3.
>
> - Maven Staging
>
> I built local project against orgapachefluss-1016 and ran write/read
> cycles with it.
>
> - Test
>
> I run fluss clients against a local cluster from the binary
> distribution: Java (5000 rows through both a primary-key and a log
> table), Rust (example-table and example-upsert-lookup), and pyfluss
> 1.0.0rc3 from TestPyPI (upsert, lookup, delete, bucket scan, 500-row
> append and log scan).
>
> **Again question on LICENSE / NOTICE files in docker images**:
>
> - The `apache/fluss:1.0.0-rc3` docker image has no LICENSE or NOTICE
> under /opt/fluss
> - But `apache/fluss-gateway:1.0.0-rc3` docker image contains
> /opt/fluss/LICENSE and /opt/fluss/NOTICE files
>
> Should also the `apache/fluss:1.0.0-rc` image add LICENSE and NOTICE
> files under `/opt/fluss` ?
>
> Best,
> Muhammet Orazov
Re: [VOTE] Release Apache Fluss 1.0.0 (RC3)
Posted by Muhammet Orazov via dev <de...@fluss.apache.org>.
Hello all,
+1 (non-binding)
- Signatures:
The tarball artifacts and both Helm files are signed by
E2C45417BED5C104154F341085BACB5AEFAE3202 (Jark Wu). All .sha512 OK.
- Source Release
The tarball does not .github, .gitignore, .idea, website/ and any
bundled binaries. The pom file declares 1.0.0.
- Build
I run `mvn clean package -DskipTests` command with JDK 11, it builds
successfully.
- Helm Chart
Looks fine, packages of the source helm/, the version and appVersion
1.0.0, and it references apache/fluss:1.0.0-rc3.
- Maven Staging
I built local project against orgapachefluss-1016 and ran write/read
cycles with it.
- Test
I run fluss clients against a local cluster from the binary
distribution: Java (5000 rows through both a primary-key and a log
table), Rust (example-table and example-upsert-lookup), and pyfluss
1.0.0rc3 from TestPyPI (upsert, lookup, delete, bucket scan, 500-row
append and log scan).
**Again question on LICENSE / NOTICE files in docker images**:
- The `apache/fluss:1.0.0-rc3` docker image has no LICENSE or NOTICE
under /opt/fluss
- But `apache/fluss-gateway:1.0.0-rc3` docker image contains
/opt/fluss/LICENSE and /opt/fluss/NOTICE files
Should also the `apache/fluss:1.0.0-rc` image add LICENSE and NOTICE
files under `/opt/fluss` ?
Best,
Muhammet Orazov
Re: [VOTE] Release Apache Fluss 1.0.0 (RC3)
Posted by Yunhong Zheng <yu...@apache.org>.
+1 (binding)
- [PASS] Built and compiled Java with Maven 3.8.6
- [PASS] Verified the checksums and signatures, and release tag
- [PASS] Verified the source archive contents against the release tag
- [PASS] Completed the official Docker Compose quickstarts: real-time-analytics-flink
- [PASS] Checked the applicable LICENSE and NOTICE files
- [PASS] Verified the cluster upgrade and readiness check
- [PASS] Verfied the disk protected
Yours,
Yunhong Zheng
On 2026/09/20 13:20:10 Leonard Xu wrote:
> +1 (non-binding)
>
> - verified signatures and checksums for the source distribution
> - checked GitHub release tag v1.0.0-rc3 matches commit 5c07f88
> - checked LICENSE and NOTICE files are present in the verified distributions
> - checked the Gateway release commit matches the GitHub release tag
> - checked pyfluss 1.0.0rc3 artifacts are available on TestPyPI
> - reviewed the changes from RC2 to RC3 and verified the Python RC version conversion
>
> Best,
> Leonard
>
> > 2026 9月 18 5:26 下午，Jark Wu <im...@gmail.com> 写道：
> >
> > Hi everyone,
> >
> > I'd like to start the community vote for Apache Fluss 1.0.0, release
> > candidate 3. The RC2 was cancelled because it uses a conflict version
> > (1.0.0) of pyfluss.
> >
> > The candidate artifacts are available at the following locations:
> >
> > Source and binary distributions, including Gateway binaries for Linux
> > amd64 and arm64:
> > https://dist.apache.org/repos/dist/dev/fluss/fluss-1.0.0-rc3/
> >
> > Helm chart:
> > https://dist.apache.org/repos/dist/dev/fluss/helm-chart/1.0.0-rc3/
> >
> > When testing the chart, please override the image tag with --set
> > image.tag=1.0.0-rc3.
> >
> > Maven staging repository:
> > https://repository.apache.org/content/repositories/orgapachefluss-1016/
> >
> > Python client (pyfluss 1.0.0rc3) on TestPyPI:
> > https://test.pypi.org/project/pyfluss/1.0.0rc3/
> >
> > Git tag:
> > https://github.com/apache/fluss/releases/tag/v1.0.0-rc3
> >
> > Git commit:
> > https://github.com/apache/fluss/commit/5c07f88e50a8ff41b0ebc214a0458e5dba60be37
> >
> > Signing key fingerprint:
> > E2C45417BED5C104154F341085BACB5AEFAE3202
> >
> > The public key is available in the KEYS file:
> > https://dist.apache.org/repos/dist/release/fluss/KEYS
> >
> > The following Docker images are available for testing:
> > - apache/fluss:1.0.0-rc3
> > - apache/fluss-gateway:1.0.0-rc3
> > - apache/fluss-quickstart-flink:1.20-1.0.0-rc3
> >
> > Release announcement draft:
> > https://github.com/apache/fluss-blog/pull/15
> >
> > Download link update:
> > https://github.com/apache/fluss/pull/4418
> >
> > Upgrade notes:
> > https://github.com/apache/fluss/blob/release-1.0/website/docs/maintenance/operations/upgrade-notes-1.0.md
> >
> > Please try the candidate and include the checks you performed with
> > your vote. The verification guide covers signatures, checksums,
> > builds, licenses, and functional testing:
> > https://fluss.apache.org/community/how-to-release/verifying-a-fluss-release/
> >
> > Please reply with your vote:
> >
> > [ ] +1: Support releasing this candidate
> > [ ] -1: Oppose releasing this candidate (please explain the issues)
> >
> > Voting will remain open for a minimum of 72 hours. Approval requires a
> > majority in favor, including at least three binding +1 votes from PMC
> > members. Votes and testing feedback from all community members are
> > welcome.
> >
> > Thanks,
> > Jark & Keith
>
>
Re: [VOTE] Release Apache Fluss 1.0.0 (RC3)
Posted by Leonard Xu <xb...@gmail.com>.
+1 (non-binding)
- verified signatures and checksums for the source distribution
- checked GitHub release tag v1.0.0-rc3 matches commit 5c07f88
- checked LICENSE and NOTICE files are present in the verified distributions
- checked the Gateway release commit matches the GitHub release tag
- checked pyfluss 1.0.0rc3 artifacts are available on TestPyPI
- reviewed the changes from RC2 to RC3 and verified the Python RC version conversion
Best,
Leonard
> 2026 9月 18 5:26 下午，Jark Wu <im...@gmail.com> 写道：
>
> Hi everyone,
>
> I'd like to start the community vote for Apache Fluss 1.0.0, release
> candidate 3. The RC2 was cancelled because it uses a conflict version
> (1.0.0) of pyfluss.
>
> The candidate artifacts are available at the following locations:
>
> Source and binary distributions, including Gateway binaries for Linux
> amd64 and arm64:
> https://dist.apache.org/repos/dist/dev/fluss/fluss-1.0.0-rc3/
>
> Helm chart:
> https://dist.apache.org/repos/dist/dev/fluss/helm-chart/1.0.0-rc3/
>
> When testing the chart, please override the image tag with --set
> image.tag=1.0.0-rc3.
>
> Maven staging repository:
> https://repository.apache.org/content/repositories/orgapachefluss-1016/
>
> Python client (pyfluss 1.0.0rc3) on TestPyPI:
> https://test.pypi.org/project/pyfluss/1.0.0rc3/
>
> Git tag:
> https://github.com/apache/fluss/releases/tag/v1.0.0-rc3
>
> Git commit:
> https://github.com/apache/fluss/commit/5c07f88e50a8ff41b0ebc214a0458e5dba60be37
>
> Signing key fingerprint:
> E2C45417BED5C104154F341085BACB5AEFAE3202
>
> The public key is available in the KEYS file:
> https://dist.apache.org/repos/dist/release/fluss/KEYS
>
> The following Docker images are available for testing:
> - apache/fluss:1.0.0-rc3
> - apache/fluss-gateway:1.0.0-rc3
> - apache/fluss-quickstart-flink:1.20-1.0.0-rc3
>
> Release announcement draft:
> https://github.com/apache/fluss-blog/pull/15
>
> Download link update:
> https://github.com/apache/fluss/pull/4418
>
> Upgrade notes:
> https://github.com/apache/fluss/blob/release-1.0/website/docs/maintenance/operations/upgrade-notes-1.0.md
>
> Please try the candidate and include the checks you performed with
> your vote. The verification guide covers signatures, checksums,
> builds, licenses, and functional testing:
> https://fluss.apache.org/community/how-to-release/verifying-a-fluss-release/
>
> Please reply with your vote:
>
> [ ] +1: Support releasing this candidate
> [ ] -1: Oppose releasing this candidate (please explain the issues)
>
> Voting will remain open for a minimum of 72 hours. Approval requires a
> majority in favor, including at least three binding +1 votes from PMC
> members. Votes and testing feedback from all community members are
> welcome.
>
> Thanks,
> Jark & Keith