[DISCUSS] Creating Kubernetes Operator release 1.6.1
Hi All! I would like to propose to release the 1.6.1 patch version for the Kubernetes operator. The release branch currently contains 2-3 critical fixes for issues that many users have hit over time. Making this release now would allow us more time to wrap up and finalize the 1.7.0 release changes (some of which are quite big regarding the autoscaler) If there are no objections I will prepare the release candidate. The changeset is minimal but very important. Cheers, Gyula
Re: [VOTE] FLIP-329: Add operator attribute to specify support for object-reuse
Thanks for the FLIP! +1 (binding) Xuannan Su 于2023年10月19日 周四10:30写道： > Hi all, > > We would like to start the vote for FLIP-329: Add operator attribute > to specify support for object-reuse[1]. This FLIP was discussed in > this thread [2]. > > The vote will be open until at least Oct 22nd (at least 72 hours), > following the consensus voting process. > > Cheers, > Xuannan > > [1] > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=255073749 > [2] https://lists.apache.org/thread/2h2r68m7bwsnvd8w1m50rktd7w6mr5n4 >
[VOTE] FLIP-329: Add operator attribute to specify support for object-reuse
Hi all, We would like to start the vote for FLIP-329: Add operator attribute to specify support for object-reuse[1]. This FLIP was discussed in this thread [2]. The vote will be open until at least Oct 22nd (at least 72 hours), following the consensus voting process. Cheers, Xuannan [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=255073749 [2] https://lists.apache.org/thread/2h2r68m7bwsnvd8w1m50rktd7w6mr5n4
[VOTE] Release 1.18.0, release candidate #3
Hi everyone, Please review and vote on the release candidate #3 for the version 1.18.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], and the pull request adding release note for users [2] * the official Apache source release and binary convenience releases to be deployed to dist.apache.org [3], which are signed with the key with fingerprint 96AE0E32CBE6E0753CE6 [4], * all artifacts to be deployed to the Maven Central Repository [5], * source code tag "release-1.18.0-rc3" [6], * website pull request listing the new release and adding announcement blog post [7]. The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Best regards, Konstantin, Sergey, Qingsheng, and Jing [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12352885 [2] https://github.com/apache/flink/pull/23527 [3] https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc3/ [4] https://dist.apache.org/repos/dist/release/flink/KEYS [5] https://repository.apache.org/content/repositories/orgapacheflink-1662 [6] https://github.com/apache/flink/releases/tag/release-1.18.0-rc3 [7] https://github.com/apache/flink-web/pull/680
[jira] [Created] (FLINK-33312) StreamingFileWriterTest.testCommitFileWhenPartitionIsCommittableByPartitionTime fails on java 21
Sergey Nuyanzin created FLINK-33312:
---
Summary:
StreamingFileWriterTest.testCommitFileWhenPartitionIsCommittableByPartitionTime
fails on java 21
Key: FLINK-33312
URL: https://issues.apache.org/jira/browse/FLINK-33312
Project: Flink
Issue Type: Sub-task
Reporter: Sergey Nuyanzin
it fails as
{noformat}
[ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.222 s
<<< FAILURE! - in
org.apache.flink.connector.file.table.stream.StreamingFileWriterTest
[ERROR]
org.apache.flink.connector.file.table.stream.StreamingFileWriterTest.testCommitFileWhenPartitionIsCommittableByPartitionTime
Time elapsed: 0.043 s <<< FAILURE!
org.opentest4j.AssertionFailedError:
Expecting value to be true but was false
at
java.base/jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(DirectConstructorHandleAccessor.java:62)
at
java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:502)
at
org.apache.flink.connector.file.table.stream.StreamingFileWriterTest.testCommitFileWhenPartitionIsCommittableByPartitionTime(StreamingFileWriterTest.java:276)
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-33311) FlinkSecurityManagerITCase fails on java 21
Sergey Nuyanzin created FLINK-33311:
---
Summary: FlinkSecurityManagerITCase fails on java 21
Key: FLINK-33311
URL: https://issues.apache.org/jira/browse/FLINK-33311
Project: Flink
Issue Type: Sub-task
Reporter: Sergey Nuyanzin
There are 2 tests {{testForcedJVMExit}} and {{testIgnoredJVMExit}} failing like
{noformat}
expected: 222
but was: 1
at
java.base/jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(DirectConstructorHandleAccessor.java:62)
at
java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:502)
at
org.apache.flink.runtime.util.FlinkSecurityManagerITCase.testForcedJVMExit(FlinkSecurityManagerITCase.java:51)
at
java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
{noformat}
and
{noformat}
expected: 0
but was: 1
at
java.base/jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(DirectConstructorHandleAccessor.java:62)
at
java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:502)
at
org.apache.flink.runtime.util.FlinkSecurityManagerITCase.testIgnoredJVMExit(FlinkSecurityManagerITCase.java:65)
at
java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-33310) Scala before 2.12.18 doesn't compile on Java 21
Sergey Nuyanzin created FLINK-33310:
---
Summary: Scala before 2.12.18 doesn't compile on Java 21
Key: FLINK-33310
URL: https://issues.apache.org/jira/browse/FLINK-33310
Project: Flink
Issue Type: Sub-task
Reporter: Sergey Nuyanzin
It fails with
{noformat}
[ERROR] error:
[INFO] bad constant pool index: 0 at pos: 48445
[INFO] while compiling:
[INFO] during phase: globalPhase=, enteringPhase=
[INFO] library version: version 2.12.15
[INFO] compiler version: version 2.12.15
...
[INFO] last tree to typer: EmptyTree
[INFO]tree position:
[INFO] tree tpe:
[INFO] symbol: null
[INFO]call site: in
[INFO]
[INFO] == Source file context for tree position ==
{noformat}
based on release notes 2.12.18 - the first 2.12.x supporting jdk21
https://github.com/scala/scala/releases/tag/v2.12.18
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-33309) java.security.manager is desallow by default starting in java18
Sergey Nuyanzin created FLINK-33309:
---
Summary: java.security.manager is desallow by default starting in
java18
Key: FLINK-33309
URL: https://issues.apache.org/jira/browse/FLINK-33309
Project: Flink
Issue Type: Sub-task
Reporter: Sergey Nuyanzin
The change was done within [https://openjdk.org/jeps/411]
{quote}
Starting in Java 18, the default value of java.security.manager will be
disallow if not otherwise set via java -D As a result, applications and
libraries that call System::setSecurityManager may fail due to an unexpected
UnsupportedOperationException. In order for System::setSecurityManager to work
as before, the end user will have to set java.security.manager to allow on the
command line (java -Djava.security.manager=allow ...).
{quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-33308) Upgrade lombok to 1.8.30
Sergey Nuyanzin created FLINK-33308: --- Summary: Upgrade lombok to 1.8.30 Key: FLINK-33308 URL: https://issues.apache.org/jira/browse/FLINK-33308 Project: Flink Issue Type: Sub-task Reporter: Sergey Nuyanzin Current lombok version is incompatible with jdk21 this issue was solved within [https://github.com/projectlombok/lombok/issues/3393] and fix is available since 1.8.30 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-33307) Disable spotless on Java 21
Sergey Nuyanzin created FLINK-33307: --- Summary: Disable spotless on Java 21 Key: FLINK-33307 URL: https://issues.apache.org/jira/browse/FLINK-33307 Project: Flink Issue Type: Sub-task Components: Build System Reporter: Sergey Nuyanzin The current spotless version doesn't run on Java 21. An upgrade is at this time impossible because compatible versions no longer run on Java 8. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [VOTE] FLIP-375: Built-in cross-platform powerful java profiler
+1 (non-binding) Best, Mason On Wed, Oct 18, 2023 at 12:47 AM Yangze Guo wrote: > +1 (binding) > > Best, > Yangze Guo > > On Wed, Oct 18, 2023 at 2:15 AM Alexander Fedulov > wrote: > > > > +1 (non-binding) > > > > Thanks for explicitly addressing my concerns from the previous attempt of > > integrating the async-profiler ( FLIP-213 [1] ). > > > > Best, > > Alexander Fedulov > > > > [1] https://lists.apache.org/thread/b5dpk4g6xgx0ysgnjphlnsvxftl17lqj > > > > On Tue, 17 Oct 2023 at 12:57, Jing Ge > wrote: > > > > > +1(binding) > > > > > > Best regards, > > > Jing > > > > > > On Tue, Oct 17, 2023 at 10:01 AM Yuepeng Pan > > > wrote: > > > > > > > +1 (non-binding) > > > > > > > > Best,Yuepeng Pan > > > > > > > > > > > > At 2023-10-17 15:51:59, "Yu Chen" wrote: > > > > >Hi all, > > > > > > > > > >Thank you to everyone for the feedback and detailed comments on > > > > FLIP-375[1]. > > > > >Based on the discussion thread [2], I think we are ready to take a > vote > > > to > > > > >contribute this to Flink. > > > > >I'd like to start a vote for it. > > > > >The vote will be open for at least 72 hours (excluding weekends, > unless > > > > >there is an objection or an insufficient number of votes). > > > > > > > > > >Thanks, > > > > >Yu Chen > > > > > > > > > >[1] > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-375%3A+Built-in+cross-platform+powerful+java+profiler > > > > >[2] > https://lists.apache.org/thread/tp5vqgspsdko66dr6vm7cgtod9k2pct7 > > > > > > > >
Re: [DISCUSS] Remove legacy Paimon (TableStore) doc link from Flink web navigation
+1 On Wed, Oct 18, 2023, 09:33 Yu Li wrote: > +1 > > Best Regards, > Yu > > > On Tue, 17 Oct 2023 at 18:59, Jing Ge wrote: > > > +1 > > > > On Tue, Oct 17, 2023 at 11:13 AM Yong Fang wrote: > > > > > +1 > > > > > > On Tue, Oct 17, 2023 at 4:52 PM Leonard Xu wrote: > > > > > > > +1 > > > > > > > > > > > > > 2023年10月17日 下午4:50，Martijn Visser 写道： > > > > > > > > > > +1 > > > > > > > > > > On Tue, Oct 17, 2023 at 10:34 AM Jingsong Li < > jingsongl...@gmail.com > > > > > > > wrote: > > > > >> > > > > >> Hi marton, > > > > >> > > > > >> Thanks for driving. +1 > > > > >> > > > > >> There is a PR to remove legacy Paimon > > > > >> https://github.com/apache/flink-web/pull/665 , but it hasn't been > > > > >> updated for a long time. > > > > >> > > > > >> Best, > > > > >> Jingsong > > > > >> > > > > >> On Tue, Oct 17, 2023 at 4:28 PM Márton Balassi < > mbala...@apache.org > > > > > > > wrote: > > > > >>> > > > > >>> Hi Flink & Paimon devs, > > > > >>> > > > > >>> The Flink webpage documentation navigation section still lists > the > > > > outdated TableStore 0.3 and master docs as subproject docs (see > > > > attachment). I am all for advertising Paimon as a sister project of > > > Flink, > > > > but the current state is misleading in multiple ways. > > > > >>> > > > > >>> I would like to remove these obsolete links if the communities > > agree. > > > > >>> > > > > >>> Best, > > > > >>> Marton > > > > > > > > > > > > > >
[jira] [Created] (FLINK-33306) Use observed true processing rate when source metrics are incorrect
Gyula Fora created FLINK-33306: -- Summary: Use observed true processing rate when source metrics are incorrect Key: FLINK-33306 URL: https://issues.apache.org/jira/browse/FLINK-33306 Project: Flink Issue Type: Improvement Components: Kubernetes Operator Reporter: Gyula Fora Assignee: Gyula Fora Fix For: kubernetes-operator-1.7.0 The aim is to address the cases when Flink incorrectly reports low busy time (high idleness) for sources that are in fact cannot keep up due to the slowness of the reader/fetchers. As the metrics cannot be generally fixed on the Flink - connector side we have to detect this and handle it when collecting the metrics. The main symptom of this problem is overestimation of the true processing rate and not triggering scaling even if lag is building up as the autoscaler thinks it will be able to keep up. To tackle this we differentiate two different methods of TPR measurement: # *Busy-time based TPR* (this is the current approach in the autoscaler) : computed from incoming records and busy time # *Observed TPR* : computed from incoming records and back pressure, measurable only when we assume full processing throughput (i.e during catch-up) h3. Current behaviour The operator currently always uses a busy-time based TPR calculation which is very flexible and allows for scaling up / down but is susceptible to overestimation due to the broken metrics. h3. Suggested new behaviour Instead of using the busy-time based TPR we detect when TPR is overestimated (busy-time too low) and switch to observed TPR. To do this, whenever we there is lag for a source (during catchup, or lag-buildup) we measure both busy-time and observed TPR. If the avg busy-time based TPR is off by a configured amount we switch to observed TPR for this source during metric evaluation. *Why not use observed TPR all the time?* Observed TPR can only be measured when we are catching up (during stabilization) or when cannot keep up. This makes it harder to scale down or to detect changes in source throughput over time (before lag starts to build up). Instead of using observed TPR we switch to it only when we detect a problem with the busy-time (this is a rare case overall), to hopefully get the best of both worlds. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-33305) Allow to customize arg line for connector's surefire plugin
Sergey Nuyanzin created FLINK-33305:
---
Summary: Allow to customize arg line for connector's surefire
plugin
Key: FLINK-33305
URL: https://issues.apache.org/jira/browse/FLINK-33305
Project: Flink
Issue Type: Technical Debt
Components: Build System, Connectors / Parent
Reporter: Sergey Nuyanzin
Assignee: Sergey Nuyanzin
Currently in case there is a need to add {{add opens}} {{add exports}} it is
impossible to do without complete rewriting of surefire configuration...
The idea is to apply same approach as for flink and it's modules to allow
customization via {{surefire.module.config}} property
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-33304) Atomicity of RowMutations would broken when Delete and Put on same columnFamily/column/row
tanjialiang created FLINK-33304: --- Summary: Atomicity of RowMutations would broken when Delete and Put on same columnFamily/column/row Key: FLINK-33304 URL: https://issues.apache.org/jira/browse/FLINK-33304 Project: Flink Issue Type: Bug Components: Connectors / HBase Affects Versions: hbase-3.0.1 Reporter: tanjialiang Current we put the mutations into BufferedMutator directly, when RowMutations have a Delete followed by Put to same column family or columns or rows, only the Delete is happening while the Put is ignored so atomicity of RowMutations is broken for such cases. See https://issues.apache.org/jira/browse/HBASE-8626. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-33303) [flink-avro] Union type not inheriting type conversions
Andrei Leib created FLINK-33303: --- Summary: [flink-avro] Union type not inheriting type conversions Key: FLINK-33303 URL: https://issues.apache.org/jira/browse/FLINK-33303 Project: Flink Issue Type: Improvement Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile) Reporter: Andrei Leib Avro version bump is required to address [AVRO-3536|https://issues.apache.org/jira/browse/AVRO-3536] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-33302) Allow to customize jdk version for connectors
Sergey Nuyanzin created FLINK-33302: --- Summary: Allow to customize jdk version for connectors Key: FLINK-33302 URL: https://issues.apache.org/jira/browse/FLINK-33302 Project: Flink Issue Type: Technical Debt Components: Build System Reporter: Sergey Nuyanzin Assignee: Sergey Nuyanzin This will allow to enable jdk 17 per connector once it's ready to compile and run with jdk17 for instance -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [VOTE] Release 1.18.0, release candidate #2
Hi Matthias, Beyond the control in the maven build, I think it makes sense to check Java and Maven versions in the release bash script to make it fail faster. New ticket FLINK-33301[1] has been created. Best regards, Jing [1] https://issues.apache.org/jira/browse/FLINK-33301 On Tue, Oct 17, 2023 at 2:39 PM Matthias Pohl wrote: > Great catch, Yun Tang. I created FLINK-33291 [1] to cover the issue of > enforcing the JDK (and Maven) version in the release profile. > > [1] https://issues.apache.org/jira/browse/FLINK-33291 > > On Tue, Oct 17, 2023 at 1:28 PM Jing Ge > wrote: > > > Hi Folks, > > > > I have rebuilt Flink with Java 8 and replaced all binary artifacts at[3]. > > @Yun > > Tang Would you please check it again? Thanks! > > > > BTW, there was a typo in the voting mail: > > > > >> * source code tag "release-1.17.0-rc2" [6] > > it should be: > > source code tag "release-1.18.0-rc2" [6] > > > > Sorry for the inconvenience caused. > > > > Special thanks for @sergey.nuyan...@aiven.io > > who > > helps double check the new binary files and found the typo. > > > > Best regards, > > Jing > > > > [3] https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc2 > > < > > > https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc2/flink-1.18.0-bin-scala_2.12.tgz > > > > > > > [6] https://github.com/apache/flink/releases/tag/release-1.18.0-rc2 > > > > On Tue, Oct 17, 2023 at 12:27 PM Jing Ge wrote: > > > > > Thanks Chesnay for the hint! Appreciate it! > > > > > > > > Best regards, > > > Jing > > > > > > On Tue, Oct 17, 2023 at 11:21 AM Chesnay Schepler > > > wrote: > > > > > >> IIRC releases MUST be built with JDK 8. > > >> > > >> @Yun Tang how did you discover this? > > >> > > >> There is supposed to be a check to enforce this, but weirdly enough it > > >> isn't rejecting my JDK 11 installation :/ > > >> Ah, we didn't set up the enforcer plugin correctly; while we do set a > > >> required JDK version by default this is interpreted as ">=", so > anything > > >> above or equal 8 is currently accepted... > > >> > > >> On 17/10/2023 07:55, Yun Tang wrote: > > >> > Hi Jing, > > >> > > > >> > I found the pre-built Flink binary release is built with JDK17[1]. > > >> Since the default target version is still 1.8 [2] and we did not > mention > > >> that building with java17 is supported [3], do we really need to make > > the > > >> default binary release built with JDK17? > > >> > > > >> > > > >> > [1] > > >> > > > https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc2/flink-1.18.0-bin-scala_2.12.tgz > > >> > [2] > > >> > > > https://github.com/apache/flink/blob/f978a77e2b9ade1e89dfb681d4b99fc13c72d2ed/pom.xml#L128 > > >> > [3] > > >> > > > https://nightlies.apache.org/flink/flink-docs-release-1.18/docs/flinkdev/building/#build-flink > > >> > > > >> > Best, > > >> > Yun Tang > > >> > > > >> > From: Lijie Wang > > >> > Sent: Tuesday, October 17, 2023 12:42 > > >> > To: dev@flink.apache.org > > >> > Subject: Re: [VOTE] Release 1.18.0, release candidate #2 > > >> > > > >> > +1 (non-binding) > > >> > > > >> > - Verified the signature and checksum > > >> > - Built from the source code > > >> > - Ran an example job on yarn cluster > > >> > - Checked the website PR > > >> > > > >> > Best, > > >> > Lijie > > >> > > > >> > Jing Ge 于2023年10月16日周一 18:43写道： > > >> > > > >> >> Hi everyone, > > >> >> > > >> >> Please review and vote on the release candidate #2 for the version > > >> >> 1.18.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], and the pull request adding release note > > for > > >> >> users [2] > > >> >> * the official Apache source release and binary convenience > releases > > >> to be > > >> >> deployed to dist.apache.org [3], which are signed with the key > with > > >> >> fingerprint 96AE0E32CBE6E0753CE6 [4], > > >> >> * all artifacts to be deployed to the Maven Central Repository [5], > > >> >> * source code tag "release-1.17.0-rc2" [6], > > >> >> * website pull request listing the new release and adding > > announcement > > >> blog > > >> >> post [7]. > > >> >> > > >> >> The vote will be open for at least 72 hours. It is adopted by > > majority > > >> >> approval, with at least 3 PMC affirmative votes. > > >> >> > > >> >> Best regards, > > >> >> Konstantin, Qingsheng, Sergey, and Jing > > >> >> > > >> >> [1] > > >> >> > > >> >> > > >> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12352885 > > >> >> [2] https://github.com/apache/flink/pull/23527 > > >> >> [3] https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc2/ > > >> >> [4] https://dist.apache.org/repos/dist/release/flink/KEYS > > >> >> [5] > > >> > https://repository.apache.org/content/repositories/orgapacheflink-1658 > > >> >>
[jira] [Created] (FLINK-33301) Add Java and Maven version checks in the bash script of Flink release process
Jing Ge created FLINK-33301: --- Summary: Add Java and Maven version checks in the bash script of Flink release process Key: FLINK-33301 URL: https://issues.apache.org/jira/browse/FLINK-33301 Project: Flink Issue Type: Bug Components: Release System Affects Versions: 1.18.0 Reporter: Jing Ge Assignee: Jing Ge Fix For: 1.19.0 During the release, Flink requires specific version of Java and Maven. It makes sense to check those versions at the very beginning of some bash scripts to let it fail fast and therefore improve the efficiency. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [VOTE] Release 1.18.0, release candidate #2
Hi Xianxun,
Gotcha, thanks for your feedback!
Best regards,
Jing
On Wed, Oct 18, 2023 at 10:51 AM Xianxun Ye wrote:
> Hi Jing,
>
> Thanks for your response.
>
> I just confirmed the new binary release works good for me in this case.
>
> I downloaded it before you update the new one.
>
>
> Best regards,
> Xianxun
>
> > 2023年10月18日 15:50，Jing Ge 写道：
> >
> > Hi Martijn,
> >
> > Fair enough! Thanks for sharing the reference!
> >
> > Best regards,
> > Jing
> >
> > On Wed, Oct 18, 2023 at 9:43 AM Martijn Visser >
> > wrote:
> >
> >> Hi Jing,
> >>
> >> Given that we as a Flink project decided to include compiled packages
> >> in a release, they are part of the same release [1] and we vote on
> >> both of them at the same time.
> >>
> >> Best regards,
> >>
> >> Martijn
> >>
> >> [1] https://www.apache.org/legal/release-policy.html#release-approval
> >>
> >> On Wed, Oct 18, 2023 at 9:21 AM Jing Ge
> >> wrote:
> >>>
> >>> Hi Xianxun,
> >>>
> >>> Thanks for the feedback. May I know when you tested it? Could you
> please
> >>> check which Java version is used to build the Flink you use? There was
> an
> >>> update on 17th Oct. at 1:30pm.
> >>>
> >>> Best regards,
> >>> Jing
> >>>
> >>> On Wed, Oct 18, 2023 at 4:32 AM Xianxun Ye
> >> wrote:
> >>>
> Hi Jing,
>
> I also found the exception about the java.lang.NoSuchMethodError when
> I
> ran the Kyuubi Flink Tests on Flink1.18-rc2.
>
> These are the steps, ran the below sql in the Flink SQL Client:
>
> create table tbl_src (a int) with ('connector' = 'datagen',
> 'number-of-rows' = '100’);
>
> select count(a) from tbl_src;
>
> Could you also update flink1.18-rc2 bianry release[1]
>
> [1] https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc2/
>
> Best regards,
> Xianxun
>
> > 2023年10月18日 10:24，Yun Tang 写道：
> >
> > Hi Jing,
> >
> > Thanks for the update, I checked the new maven repo, and the
> >> artifacts
> were built with JDK8 correctly.
> >
> >
> > Best
> > Yun Tang
> >
> > From: Jing Ge
> > Sent: Tuesday, October 17, 2023 23:31
> > To: dev@flink.apache.org
> > Cc: Matthias Pohl ; sergey.nuyan...@aiven.io
> >> <
> sergey.nuyan...@aiven.io>
> > Subject: Re: [VOTE] Release 1.18.0, release candidate #2
> >
> > Hi Yun,
> >
> > I have created a new maven repo[5]. Would you like to check it out?
> Thanks
> > for your support! Once I get your confirmation, I will start the
> >> second
> > voting thread with the title "[VOTE][2] Release 1.18.0, release
> >> candidate
> > #2", because the source code is not changed.
> >
> > All Devs: please ignore this thread. I will start a new one as I
> > mentioned above.
> >
> > Best regards,
> > Jing
> >
> > [5]
>
> https://repository.apache.org/content/repositories/orgapacheflink-1659
> >
> > On Tue, Oct 17, 2023 at 3:53 PM Jing Ge wrote:
> >
> >> Hi Yun,
> >>
> >> Thanks for the feedback. Appreciate it! I will update them
> >> accordingly
> and
> >> then ask you for double checking. Thanks in advance.
> >>
> >> Best regards,
> >> Jing
> >>
> >> On Tue, Oct 17, 2023 at 2:42 PM Yun Tang wrote:
> >>
> >>> Hi Jing,
> >>>
> >>> Thanks for the update. I checked the new pre-built binary release,
> >> and
> it
> >>> works fine now. However, I then checked the pre-built jar packages
> >> and
> >>> found they are also built with JDK17, e.g., flink-runtime.jar [1].
> >>>
> >>> I think we also need to update all artifacts to be deployed.
> >>>
> >>>
> >>> [1]
> >>>
>
> >>
> https://repository.apache.org/content/repositories/orgapacheflink-1658/org/apache/flink/flink-runtime/1.18.0/flink-runtime-1.18.0.jar
> >>>
> >>> Best,
> >>> Yun Tang
> >>>
> >>>
> >>>
> >>> From: Matthias Pohl
> >>> Sent: Tuesday, October 17, 2023 20:38
> >>> To: dev@flink.apache.org
> >>> Cc: Yun Tang ; sergey.nuyan...@aiven.io <
> >>> sergey.nuyan...@aiven.io>
> >>> Subject: Re: [VOTE] Release 1.18.0, release candidate #2
> >>>
> >>> Great catch, Yun Tang. I created FLINK-33291 [1] to cover the
> >> issue of
> >>> enforcing the JDK (and Maven) version in the release profile.
> >>>
> >>> [1] https://issues.apache.org/jira/browse/FLINK-33291
> >>>
> >>> On Tue, Oct 17, 2023 at 1:28 PM Jing Ge >>>
> >>> wrote:
> >>> Hi Folks,
> >>>
> >>> I have rebuilt Flink with Java 8 and replaced all binary artifacts
> at[3].
> >>> @Yun
> >>> Tang mailto:myas...@live.com>> Would you please
> check
> >>> it again? Thanks!
> >>>
> >>> BTW, there was a typo in the voting mail:
> >>>
> > * source code tag "release-1.17.0-rc2" [6]
>
Re: [VOTE] Release 1.18.0, release candidate #2
Hi Jing,
Thanks for your response.
I just confirmed the new binary release works good for me in this case.
I downloaded it before you update the new one.
Best regards,
Xianxun
> 2023年10月18日 15:50，Jing Ge 写道：
>
> Hi Martijn,
>
> Fair enough! Thanks for sharing the reference!
>
> Best regards,
> Jing
>
> On Wed, Oct 18, 2023 at 9:43 AM Martijn Visser
> wrote:
>
>> Hi Jing,
>>
>> Given that we as a Flink project decided to include compiled packages
>> in a release, they are part of the same release [1] and we vote on
>> both of them at the same time.
>>
>> Best regards,
>>
>> Martijn
>>
>> [1] https://www.apache.org/legal/release-policy.html#release-approval
>>
>> On Wed, Oct 18, 2023 at 9:21 AM Jing Ge
>> wrote:
>>>
>>> Hi Xianxun,
>>>
>>> Thanks for the feedback. May I know when you tested it? Could you please
>>> check which Java version is used to build the Flink you use? There was an
>>> update on 17th Oct. at 1:30pm.
>>>
>>> Best regards,
>>> Jing
>>>
>>> On Wed, Oct 18, 2023 at 4:32 AM Xianxun Ye
>> wrote:
>>>
Hi Jing,
I also found the exception about the java.lang.NoSuchMethodError when I
ran the Kyuubi Flink Tests on Flink1.18-rc2.
These are the steps, ran the below sql in the Flink SQL Client:
create table tbl_src (a int) with ('connector' = 'datagen',
'number-of-rows' = '100’);
select count(a) from tbl_src;
Could you also update flink1.18-rc2 bianry release[1]
[1] https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc2/
Best regards,
Xianxun
> 2023年10月18日 10:24，Yun Tang 写道：
>
> Hi Jing,
>
> Thanks for the update, I checked the new maven repo, and the
>> artifacts
were built with JDK8 correctly.
>
>
> Best
> Yun Tang
>
> From: Jing Ge
> Sent: Tuesday, October 17, 2023 23:31
> To: dev@flink.apache.org
> Cc: Matthias Pohl ; sergey.nuyan...@aiven.io
>> <
sergey.nuyan...@aiven.io>
> Subject: Re: [VOTE] Release 1.18.0, release candidate #2
>
> Hi Yun,
>
> I have created a new maven repo[5]. Would you like to check it out?
Thanks
> for your support! Once I get your confirmation, I will start the
>> second
> voting thread with the title "[VOTE][2] Release 1.18.0, release
>> candidate
> #2", because the source code is not changed.
>
> All Devs: please ignore this thread. I will start a new one as I
> mentioned above.
>
> Best regards,
> Jing
>
> [5]
https://repository.apache.org/content/repositories/orgapacheflink-1659
>
> On Tue, Oct 17, 2023 at 3:53 PM Jing Ge wrote:
>
>> Hi Yun,
>>
>> Thanks for the feedback. Appreciate it! I will update them
>> accordingly
and
>> then ask you for double checking. Thanks in advance.
>>
>> Best regards,
>> Jing
>>
>> On Tue, Oct 17, 2023 at 2:42 PM Yun Tang wrote:
>>
>>> Hi Jing,
>>>
>>> Thanks for the update. I checked the new pre-built binary release,
>> and
it
>>> works fine now. However, I then checked the pre-built jar packages
>> and
>>> found they are also built with JDK17, e.g., flink-runtime.jar [1].
>>>
>>> I think we also need to update all artifacts to be deployed.
>>>
>>>
>>> [1]
>>>
>> https://repository.apache.org/content/repositories/orgapacheflink-1658/org/apache/flink/flink-runtime/1.18.0/flink-runtime-1.18.0.jar
>>>
>>> Best,
>>> Yun Tang
>>>
>>>
>>>
>>> From: Matthias Pohl
>>> Sent: Tuesday, October 17, 2023 20:38
>>> To: dev@flink.apache.org
>>> Cc: Yun Tang ; sergey.nuyan...@aiven.io <
>>> sergey.nuyan...@aiven.io>
>>> Subject: Re: [VOTE] Release 1.18.0, release candidate #2
>>>
>>> Great catch, Yun Tang. I created FLINK-33291 [1] to cover the
>> issue of
>>> enforcing the JDK (and Maven) version in the release profile.
>>>
>>> [1] https://issues.apache.org/jira/browse/FLINK-33291
>>>
>>> On Tue, Oct 17, 2023 at 1:28 PM Jing Ge >>
>>> wrote:
>>> Hi Folks,
>>>
>>> I have rebuilt Flink with Java 8 and replaced all binary artifacts
at[3].
>>> @Yun
>>> Tang mailto:myas...@live.com>> Would you please
check
>>> it again? Thanks!
>>>
>>> BTW, there was a typo in the voting mail:
>>>
> * source code tag "release-1.17.0-rc2" [6]
>>> it should be:
>>> source code tag "release-1.18.0-rc2" [6]
>>>
>>> Sorry for the inconvenience caused.
>>>
>>> Special thanks for @sergey.nuyan...@aiven.io>> sergey.nuyan...@aiven.io> >> sergey.nuyan...@aiven.io>> who
>>> helps double check the new binary files and found the typo.
>>>
>>> Best regards,
>>> Jing
>>>
>>> [3]
[jira] [Created] (FLINK-33300) Update testcontainers dependency to v1.19.1
Sergey Nuyanzin created FLINK-33300: --- Summary: Update testcontainers dependency to v1.19.1 Key: FLINK-33300 URL: https://issues.apache.org/jira/browse/FLINK-33300 Project: Flink Issue Type: Technical Debt Components: Test Infrastructure Reporter: Sergey Nuyanzin One of the main features is life simplification for SELinux users (I'm one of those) https://github.com/testcontainers/testcontainers-java/pull/6294 https://github.com/testcontainers/testcontainers-java/pull/7187 Also more release notes are at https://github.com/testcontainers/testcontainers-java/releases/tag/1.19.1 https://github.com/testcontainers/testcontainers-java/releases/tag/1.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [VOTE] Release 1.18.0, release candidate #2
Hi Martijn,
Fair enough! Thanks for sharing the reference!
Best regards,
Jing
On Wed, Oct 18, 2023 at 9:43 AM Martijn Visser
wrote:
> Hi Jing,
>
> Given that we as a Flink project decided to include compiled packages
> in a release, they are part of the same release [1] and we vote on
> both of them at the same time.
>
> Best regards,
>
> Martijn
>
> [1] https://www.apache.org/legal/release-policy.html#release-approval
>
> On Wed, Oct 18, 2023 at 9:21 AM Jing Ge
> wrote:
> >
> > Hi Xianxun,
> >
> > Thanks for the feedback. May I know when you tested it? Could you please
> > check which Java version is used to build the Flink you use? There was an
> > update on 17th Oct. at 1:30pm.
> >
> > Best regards,
> > Jing
> >
> > On Wed, Oct 18, 2023 at 4:32 AM Xianxun Ye
> wrote:
> >
> > > Hi Jing,
> > >
> > > I also found the exception about the java.lang.NoSuchMethodError when I
> > > ran the Kyuubi Flink Tests on Flink1.18-rc2.
> > >
> > > These are the steps, ran the below sql in the Flink SQL Client:
> > >
> > > create table tbl_src (a int) with ('connector' = 'datagen',
> > > 'number-of-rows' = '100’);
> > >
> > > select count(a) from tbl_src;
> > >
> > > Could you also update flink1.18-rc2 bianry release[1]
> > >
> > > [1] https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc2/
> > >
> > > Best regards,
> > > Xianxun
> > >
> > > > 2023年10月18日 10:24，Yun Tang 写道：
> > > >
> > > > Hi Jing,
> > > >
> > > > Thanks for the update, I checked the new maven repo, and the
> artifacts
> > > were built with JDK8 correctly.
> > > >
> > > >
> > > > Best
> > > > Yun Tang
> > > >
> > > > From: Jing Ge
> > > > Sent: Tuesday, October 17, 2023 23:31
> > > > To: dev@flink.apache.org
> > > > Cc: Matthias Pohl ; sergey.nuyan...@aiven.io
> <
> > > sergey.nuyan...@aiven.io>
> > > > Subject: Re: [VOTE] Release 1.18.0, release candidate #2
> > > >
> > > > Hi Yun,
> > > >
> > > > I have created a new maven repo[5]. Would you like to check it out?
> > > Thanks
> > > > for your support! Once I get your confirmation, I will start the
> second
> > > > voting thread with the title "[VOTE][2] Release 1.18.0, release
> candidate
> > > > #2", because the source code is not changed.
> > > >
> > > > All Devs: please ignore this thread. I will start a new one as I
> > > > mentioned above.
> > > >
> > > > Best regards,
> > > > Jing
> > > >
> > > > [5]
> > > https://repository.apache.org/content/repositories/orgapacheflink-1659
> > > >
> > > > On Tue, Oct 17, 2023 at 3:53 PM Jing Ge wrote:
> > > >
> > > >> Hi Yun,
> > > >>
> > > >> Thanks for the feedback. Appreciate it! I will update them
> accordingly
> > > and
> > > >> then ask you for double checking. Thanks in advance.
> > > >>
> > > >> Best regards,
> > > >> Jing
> > > >>
> > > >> On Tue, Oct 17, 2023 at 2:42 PM Yun Tang wrote:
> > > >>
> > > >>> Hi Jing,
> > > >>>
> > > >>> Thanks for the update. I checked the new pre-built binary release,
> and
> > > it
> > > >>> works fine now. However, I then checked the pre-built jar packages
> and
> > > >>> found they are also built with JDK17, e.g., flink-runtime.jar [1].
> > > >>>
> > > >>> I think we also need to update all artifacts to be deployed.
> > > >>>
> > > >>>
> > > >>> [1]
> > > >>>
> > >
> https://repository.apache.org/content/repositories/orgapacheflink-1658/org/apache/flink/flink-runtime/1.18.0/flink-runtime-1.18.0.jar
> > > >>>
> > > >>> Best,
> > > >>> Yun Tang
> > > >>>
> > > >>>
> > > >>>
> > > >>> From: Matthias Pohl
> > > >>> Sent: Tuesday, October 17, 2023 20:38
> > > >>> To: dev@flink.apache.org
> > > >>> Cc: Yun Tang ; sergey.nuyan...@aiven.io <
> > > >>> sergey.nuyan...@aiven.io>
> > > >>> Subject: Re: [VOTE] Release 1.18.0, release candidate #2
> > > >>>
> > > >>> Great catch, Yun Tang. I created FLINK-33291 [1] to cover the
> issue of
> > > >>> enforcing the JDK (and Maven) version in the release profile.
> > > >>>
> > > >>> [1] https://issues.apache.org/jira/browse/FLINK-33291
> > > >>>
> > > >>> On Tue, Oct 17, 2023 at 1:28 PM Jing Ge >
> > > >>> wrote:
> > > >>> Hi Folks,
> > > >>>
> > > >>> I have rebuilt Flink with Java 8 and replaced all binary artifacts
> > > at[3].
> > > >>> @Yun
> > > >>> Tang mailto:myas...@live.com>> Would you please
> > > check
> > > >>> it again? Thanks!
> > > >>>
> > > >>> BTW, there was a typo in the voting mail:
> > > >>>
> > > > * source code tag "release-1.17.0-rc2" [6]
> > > >>> it should be:
> > > >>> source code tag "release-1.18.0-rc2" [6]
> > > >>>
> > > >>> Sorry for the inconvenience caused.
> > > >>>
> > > >>> Special thanks for @sergey.nuyan...@aiven.io > > >>> sergey.nuyan...@aiven.io> > > >>> sergey.nuyan...@aiven.io>> who
> > > >>> helps double check the new binary files and found the typo.
> > > >>>
> > > >>> Best regards,
> > > >>> Jing
> > > >>>
> > > >>> [3] https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc2
> > > >>> <
> > > >>>
> > >
>
Re: [VOTE] FLIP-375: Built-in cross-platform powerful java profiler
+1 (binding) Best, Yangze Guo On Wed, Oct 18, 2023 at 2:15 AM Alexander Fedulov wrote: > > +1 (non-binding) > > Thanks for explicitly addressing my concerns from the previous attempt of > integrating the async-profiler ( FLIP-213 [1] ). > > Best, > Alexander Fedulov > > [1] https://lists.apache.org/thread/b5dpk4g6xgx0ysgnjphlnsvxftl17lqj > > On Tue, 17 Oct 2023 at 12:57, Jing Ge wrote: > > > +1(binding) > > > > Best regards, > > Jing > > > > On Tue, Oct 17, 2023 at 10:01 AM Yuepeng Pan > > wrote: > > > > > +1 (non-binding) > > > > > > Best,Yuepeng Pan > > > > > > > > > At 2023-10-17 15:51:59, "Yu Chen" wrote: > > > >Hi all, > > > > > > > >Thank you to everyone for the feedback and detailed comments on > > > FLIP-375[1]. > > > >Based on the discussion thread [2], I think we are ready to take a vote > > to > > > >contribute this to Flink. > > > >I'd like to start a vote for it. > > > >The vote will be open for at least 72 hours (excluding weekends, unless > > > >there is an objection or an insufficient number of votes). > > > > > > > >Thanks, > > > >Yu Chen > > > > > > > >[1] > > > > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-375%3A+Built-in+cross-platform+powerful+java+profiler > > > >[2] https://lists.apache.org/thread/tp5vqgspsdko66dr6vm7cgtod9k2pct7 > > > > >
Re: [VOTE] Release 1.18.0, release candidate #2
Hi Folks,
After talking with other release managers, RC2 is canceled because of the
Java 17/8 issue mentioned above. I am waiting for the feedback from
Xianxun, once I get confirmation that the issue is gone with the Flink
built with Java 8, I will start RC3 vote. Thank you all for your feedback!
@xianxun Would you like to share the feedback asap? This will help us to
start RC3 vote at a fast pace. Thanks!
@Matthias Pohl @Martijn Visser
FYI, thanks again for your suggestions!
Best regards,
Jing
On Wed, Oct 18, 2023 at 9:20 AM Jing Ge wrote:
> Hi Xianxun,
>
> Thanks for the feedback. May I know when you tested it? Could you please
> check which Java version is used to build the Flink you use? There was an
> update on 17th Oct. at 1:30pm.
>
> Best regards,
> Jing
>
> On Wed, Oct 18, 2023 at 4:32 AM Xianxun Ye
> wrote:
>
>> Hi Jing,
>>
>> I also found the exception about the java.lang.NoSuchMethodError when I
>> ran the Kyuubi Flink Tests on Flink1.18-rc2.
>>
>> These are the steps, ran the below sql in the Flink SQL Client:
>>
>> create table tbl_src (a int) with ('connector' = 'datagen',
>> 'number-of-rows' = '100’);
>>
>> select count(a) from tbl_src;
>>
>> Could you also update flink1.18-rc2 bianry release[1]
>>
>> [1] https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc2/
>>
>> Best regards,
>> Xianxun
>>
>> > 2023年10月18日 10:24，Yun Tang 写道：
>> >
>> > Hi Jing,
>> >
>> > Thanks for the update, I checked the new maven repo, and the artifacts
>> were built with JDK8 correctly.
>> >
>> >
>> > Best
>> > Yun Tang
>> >
>> > From: Jing Ge
>> > Sent: Tuesday, October 17, 2023 23:31
>> > To: dev@flink.apache.org
>> > Cc: Matthias Pohl ; sergey.nuyan...@aiven.io <
>> sergey.nuyan...@aiven.io>
>> > Subject: Re: [VOTE] Release 1.18.0, release candidate #2
>> >
>> > Hi Yun,
>> >
>> > I have created a new maven repo[5]. Would you like to check it out?
>> Thanks
>> > for your support! Once I get your confirmation, I will start the second
>> > voting thread with the title "[VOTE][2] Release 1.18.0, release
>> candidate
>> > #2", because the source code is not changed.
>> >
>> > All Devs: please ignore this thread. I will start a new one as I
>> > mentioned above.
>> >
>> > Best regards,
>> > Jing
>> >
>> > [5]
>> https://repository.apache.org/content/repositories/orgapacheflink-1659
>> >
>> > On Tue, Oct 17, 2023 at 3:53 PM Jing Ge wrote:
>> >
>> >> Hi Yun,
>> >>
>> >> Thanks for the feedback. Appreciate it! I will update them accordingly
>> and
>> >> then ask you for double checking. Thanks in advance.
>> >>
>> >> Best regards,
>> >> Jing
>> >>
>> >> On Tue, Oct 17, 2023 at 2:42 PM Yun Tang wrote:
>> >>
>> >>> Hi Jing,
>> >>>
>> >>> Thanks for the update. I checked the new pre-built binary release,
>> and it
>> >>> works fine now. However, I then checked the pre-built jar packages and
>> >>> found they are also built with JDK17, e.g., flink-runtime.jar [1].
>> >>>
>> >>> I think we also need to update all artifacts to be deployed.
>> >>>
>> >>>
>> >>> [1]
>> >>>
>> https://repository.apache.org/content/repositories/orgapacheflink-1658/org/apache/flink/flink-runtime/1.18.0/flink-runtime-1.18.0.jar
>> >>>
>> >>> Best,
>> >>> Yun Tang
>> >>>
>> >>>
>> >>>
>> >>> From: Matthias Pohl
>> >>> Sent: Tuesday, October 17, 2023 20:38
>> >>> To: dev@flink.apache.org
>> >>> Cc: Yun Tang ; sergey.nuyan...@aiven.io <
>> >>> sergey.nuyan...@aiven.io>
>> >>> Subject: Re: [VOTE] Release 1.18.0, release candidate #2
>> >>>
>> >>> Great catch, Yun Tang. I created FLINK-33291 [1] to cover the issue of
>> >>> enforcing the JDK (and Maven) version in the release profile.
>> >>>
>> >>> [1] https://issues.apache.org/jira/browse/FLINK-33291
>> >>>
>> >>> On Tue, Oct 17, 2023 at 1:28 PM Jing Ge
>> >>> wrote:
>> >>> Hi Folks,
>> >>>
>> >>> I have rebuilt Flink with Java 8 and replaced all binary artifacts
>> at[3].
>> >>> @Yun
>> >>> Tang mailto:myas...@live.com>> Would you please
>> check
>> >>> it again? Thanks!
>> >>>
>> >>> BTW, there was a typo in the voting mail:
>> >>>
>> > * source code tag "release-1.17.0-rc2" [6]
>> >>> it should be:
>> >>> source code tag "release-1.18.0-rc2" [6]
>> >>>
>> >>> Sorry for the inconvenience caused.
>> >>>
>> >>> Special thanks for @sergey.nuyan...@aiven.io> >>> sergey.nuyan...@aiven.io> > >>> sergey.nuyan...@aiven.io>> who
>> >>> helps double check the new binary files and found the typo.
>> >>>
>> >>> Best regards,
>> >>> Jing
>> >>>
>> >>> [3] https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc2
>> >>> <
>> >>>
>> https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc2/flink-1.18.0-bin-scala_2.12.tgz
>>
>> >>>
>> >>> [6] https://github.com/apache/flink/releases/tag/release-1.18.0-rc2
>> >>>
>> >>> On Tue, Oct 17, 2023 at 12:27 PM Jing Ge > >>> j...@ververica.com>> wrote:
>> >>>
>> Thanks Chesnay for the hint! Appreciate it!
>>
>>
>> >>> Best regards,
>> Jing
>>
>>
Re: [VOTE] Release 1.18.0, release candidate #2
Hi Jing,
Given that we as a Flink project decided to include compiled packages
in a release, they are part of the same release [1] and we vote on
both of them at the same time.
Best regards,
Martijn
[1] https://www.apache.org/legal/release-policy.html#release-approval
On Wed, Oct 18, 2023 at 9:21 AM Jing Ge wrote:
>
> Hi Xianxun,
>
> Thanks for the feedback. May I know when you tested it? Could you please
> check which Java version is used to build the Flink you use? There was an
> update on 17th Oct. at 1:30pm.
>
> Best regards,
> Jing
>
> On Wed, Oct 18, 2023 at 4:32 AM Xianxun Ye wrote:
>
> > Hi Jing,
> >
> > I also found the exception about the java.lang.NoSuchMethodError when I
> > ran the Kyuubi Flink Tests on Flink1.18-rc2.
> >
> > These are the steps, ran the below sql in the Flink SQL Client:
> >
> > create table tbl_src (a int) with ('connector' = 'datagen',
> > 'number-of-rows' = '100’);
> >
> > select count(a) from tbl_src;
> >
> > Could you also update flink1.18-rc2 bianry release[1]
> >
> > [1] https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc2/
> >
> > Best regards,
> > Xianxun
> >
> > > 2023年10月18日 10:24，Yun Tang 写道：
> > >
> > > Hi Jing,
> > >
> > > Thanks for the update, I checked the new maven repo, and the artifacts
> > were built with JDK8 correctly.
> > >
> > >
> > > Best
> > > Yun Tang
> > >
> > > From: Jing Ge
> > > Sent: Tuesday, October 17, 2023 23:31
> > > To: dev@flink.apache.org
> > > Cc: Matthias Pohl ; sergey.nuyan...@aiven.io <
> > sergey.nuyan...@aiven.io>
> > > Subject: Re: [VOTE] Release 1.18.0, release candidate #2
> > >
> > > Hi Yun,
> > >
> > > I have created a new maven repo[5]. Would you like to check it out?
> > Thanks
> > > for your support! Once I get your confirmation, I will start the second
> > > voting thread with the title "[VOTE][2] Release 1.18.0, release candidate
> > > #2", because the source code is not changed.
> > >
> > > All Devs: please ignore this thread. I will start a new one as I
> > > mentioned above.
> > >
> > > Best regards,
> > > Jing
> > >
> > > [5]
> > https://repository.apache.org/content/repositories/orgapacheflink-1659
> > >
> > > On Tue, Oct 17, 2023 at 3:53 PM Jing Ge wrote:
> > >
> > >> Hi Yun,
> > >>
> > >> Thanks for the feedback. Appreciate it! I will update them accordingly
> > and
> > >> then ask you for double checking. Thanks in advance.
> > >>
> > >> Best regards,
> > >> Jing
> > >>
> > >> On Tue, Oct 17, 2023 at 2:42 PM Yun Tang wrote:
> > >>
> > >>> Hi Jing,
> > >>>
> > >>> Thanks for the update. I checked the new pre-built binary release, and
> > it
> > >>> works fine now. However, I then checked the pre-built jar packages and
> > >>> found they are also built with JDK17, e.g., flink-runtime.jar [1].
> > >>>
> > >>> I think we also need to update all artifacts to be deployed.
> > >>>
> > >>>
> > >>> [1]
> > >>>
> > https://repository.apache.org/content/repositories/orgapacheflink-1658/org/apache/flink/flink-runtime/1.18.0/flink-runtime-1.18.0.jar
> > >>>
> > >>> Best,
> > >>> Yun Tang
> > >>>
> > >>>
> > >>>
> > >>> From: Matthias Pohl
> > >>> Sent: Tuesday, October 17, 2023 20:38
> > >>> To: dev@flink.apache.org
> > >>> Cc: Yun Tang ; sergey.nuyan...@aiven.io <
> > >>> sergey.nuyan...@aiven.io>
> > >>> Subject: Re: [VOTE] Release 1.18.0, release candidate #2
> > >>>
> > >>> Great catch, Yun Tang. I created FLINK-33291 [1] to cover the issue of
> > >>> enforcing the JDK (and Maven) version in the release profile.
> > >>>
> > >>> [1] https://issues.apache.org/jira/browse/FLINK-33291
> > >>>
> > >>> On Tue, Oct 17, 2023 at 1:28 PM Jing Ge
> > >>> wrote:
> > >>> Hi Folks,
> > >>>
> > >>> I have rebuilt Flink with Java 8 and replaced all binary artifacts
> > at[3].
> > >>> @Yun
> > >>> Tang mailto:myas...@live.com>> Would you please
> > check
> > >>> it again? Thanks!
> > >>>
> > >>> BTW, there was a typo in the voting mail:
> > >>>
> > > * source code tag "release-1.17.0-rc2" [6]
> > >>> it should be:
> > >>> source code tag "release-1.18.0-rc2" [6]
> > >>>
> > >>> Sorry for the inconvenience caused.
> > >>>
> > >>> Special thanks for @sergey.nuyan...@aiven.io > >>> sergey.nuyan...@aiven.io> > >>> sergey.nuyan...@aiven.io>> who
> > >>> helps double check the new binary files and found the typo.
> > >>>
> > >>> Best regards,
> > >>> Jing
> > >>>
> > >>> [3] https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc2
> > >>> <
> > >>>
> > https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc2/flink-1.18.0-bin-scala_2.12.tgz
> >
> > >>>
> > >>> [6] https://github.com/apache/flink/releases/tag/release-1.18.0-rc2
> > >>>
> > >>> On Tue, Oct 17, 2023 at 12:27 PM Jing Ge > >>> j...@ververica.com>> wrote:
> > >>>
> > Thanks Chesnay for the hint! Appreciate it!
> >
> >
> > >>> Best regards,
> > Jing
> >
> > On Tue, Oct 17, 2023 at 11:21 AM Chesnay Schepler > >>> >
> >
Re: [DISCUSS] Remove legacy Paimon (TableStore) doc link from Flink web navigation
+1 Best Regards, Yu On Tue, 17 Oct 2023 at 18:59, Jing Ge wrote: > +1 > > On Tue, Oct 17, 2023 at 11:13 AM Yong Fang wrote: > > > +1 > > > > On Tue, Oct 17, 2023 at 4:52 PM Leonard Xu wrote: > > > > > +1 > > > > > > > > > > 2023年10月17日 下午4:50，Martijn Visser 写道： > > > > > > > > +1 > > > > > > > > On Tue, Oct 17, 2023 at 10:34 AM Jingsong Li > > > > wrote: > > > >> > > > >> Hi marton, > > > >> > > > >> Thanks for driving. +1 > > > >> > > > >> There is a PR to remove legacy Paimon > > > >> https://github.com/apache/flink-web/pull/665 , but it hasn't been > > > >> updated for a long time. > > > >> > > > >> Best, > > > >> Jingsong > > > >> > > > >> On Tue, Oct 17, 2023 at 4:28 PM Márton Balassi > > > > wrote: > > > >>> > > > >>> Hi Flink & Paimon devs, > > > >>> > > > >>> The Flink webpage documentation navigation section still lists the > > > outdated TableStore 0.3 and master docs as subproject docs (see > > > attachment). I am all for advertising Paimon as a sister project of > > Flink, > > > but the current state is misleading in multiple ways. > > > >>> > > > >>> I would like to remove these obsolete links if the communities > agree. > > > >>> > > > >>> Best, > > > >>> Marton > > > > > > > > >
Re: [VOTE] Release 1.18.0, release candidate #2
Hi Xianxun,
Thanks for the feedback. May I know when you tested it? Could you please
check which Java version is used to build the Flink you use? There was an
update on 17th Oct. at 1:30pm.
Best regards,
Jing
On Wed, Oct 18, 2023 at 4:32 AM Xianxun Ye wrote:
> Hi Jing,
>
> I also found the exception about the java.lang.NoSuchMethodError when I
> ran the Kyuubi Flink Tests on Flink1.18-rc2.
>
> These are the steps, ran the below sql in the Flink SQL Client:
>
> create table tbl_src (a int) with ('connector' = 'datagen',
> 'number-of-rows' = '100’);
>
> select count(a) from tbl_src;
>
> Could you also update flink1.18-rc2 bianry release[1]
>
> [1] https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc2/
>
> Best regards,
> Xianxun
>
> > 2023年10月18日 10:24，Yun Tang 写道：
> >
> > Hi Jing,
> >
> > Thanks for the update, I checked the new maven repo, and the artifacts
> were built with JDK8 correctly.
> >
> >
> > Best
> > Yun Tang
> >
> > From: Jing Ge
> > Sent: Tuesday, October 17, 2023 23:31
> > To: dev@flink.apache.org
> > Cc: Matthias Pohl ; sergey.nuyan...@aiven.io <
> sergey.nuyan...@aiven.io>
> > Subject: Re: [VOTE] Release 1.18.0, release candidate #2
> >
> > Hi Yun,
> >
> > I have created a new maven repo[5]. Would you like to check it out?
> Thanks
> > for your support! Once I get your confirmation, I will start the second
> > voting thread with the title "[VOTE][2] Release 1.18.0, release candidate
> > #2", because the source code is not changed.
> >
> > All Devs: please ignore this thread. I will start a new one as I
> > mentioned above.
> >
> > Best regards,
> > Jing
> >
> > [5]
> https://repository.apache.org/content/repositories/orgapacheflink-1659
> >
> > On Tue, Oct 17, 2023 at 3:53 PM Jing Ge wrote:
> >
> >> Hi Yun,
> >>
> >> Thanks for the feedback. Appreciate it! I will update them accordingly
> and
> >> then ask you for double checking. Thanks in advance.
> >>
> >> Best regards,
> >> Jing
> >>
> >> On Tue, Oct 17, 2023 at 2:42 PM Yun Tang wrote:
> >>
> >>> Hi Jing,
> >>>
> >>> Thanks for the update. I checked the new pre-built binary release, and
> it
> >>> works fine now. However, I then checked the pre-built jar packages and
> >>> found they are also built with JDK17, e.g., flink-runtime.jar [1].
> >>>
> >>> I think we also need to update all artifacts to be deployed.
> >>>
> >>>
> >>> [1]
> >>>
> https://repository.apache.org/content/repositories/orgapacheflink-1658/org/apache/flink/flink-runtime/1.18.0/flink-runtime-1.18.0.jar
> >>>
> >>> Best,
> >>> Yun Tang
> >>>
> >>>
> >>>
> >>> From: Matthias Pohl
> >>> Sent: Tuesday, October 17, 2023 20:38
> >>> To: dev@flink.apache.org
> >>> Cc: Yun Tang ; sergey.nuyan...@aiven.io <
> >>> sergey.nuyan...@aiven.io>
> >>> Subject: Re: [VOTE] Release 1.18.0, release candidate #2
> >>>
> >>> Great catch, Yun Tang. I created FLINK-33291 [1] to cover the issue of
> >>> enforcing the JDK (and Maven) version in the release profile.
> >>>
> >>> [1] https://issues.apache.org/jira/browse/FLINK-33291
> >>>
> >>> On Tue, Oct 17, 2023 at 1:28 PM Jing Ge
> >>> wrote:
> >>> Hi Folks,
> >>>
> >>> I have rebuilt Flink with Java 8 and replaced all binary artifacts
> at[3].
> >>> @Yun
> >>> Tang mailto:myas...@live.com>> Would you please
> check
> >>> it again? Thanks!
> >>>
> >>> BTW, there was a typo in the voting mail:
> >>>
> > * source code tag "release-1.17.0-rc2" [6]
> >>> it should be:
> >>> source code tag "release-1.18.0-rc2" [6]
> >>>
> >>> Sorry for the inconvenience caused.
> >>>
> >>> Special thanks for @sergey.nuyan...@aiven.io >>> sergey.nuyan...@aiven.io> >>> sergey.nuyan...@aiven.io>> who
> >>> helps double check the new binary files and found the typo.
> >>>
> >>> Best regards,
> >>> Jing
> >>>
> >>> [3] https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc2
> >>> <
> >>>
> https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc2/flink-1.18.0-bin-scala_2.12.tgz
>
> >>>
> >>> [6] https://github.com/apache/flink/releases/tag/release-1.18.0-rc2
> >>>
> >>> On Tue, Oct 17, 2023 at 12:27 PM Jing Ge >>> j...@ververica.com>> wrote:
> >>>
> Thanks Chesnay for the hint! Appreciate it!
>
>
> >>> Best regards,
> Jing
>
> On Tue, Oct 17, 2023 at 11:21 AM Chesnay Schepler >>> >
> wrote:
>
> > IIRC releases MUST be built with JDK 8.
> >
> > @Yun Tang how did you discover this?
> >
> > There is supposed to be a check to enforce this, but weirdly enough
> it
> > isn't rejecting my JDK 11 installation :/
> > Ah, we didn't set up the enforcer plugin correctly; while we do set a
> > required JDK version by default this is interpreted as ">=", so
> >>> anything
> > above or equal 8 is currently accepted...
> >
> > On 17/10/2023 07:55, Yun Tang wrote:
> >> Hi Jing,
> >>
> >> I found the pre-built Flink binary release is built with JDK17[1].
>
Re: [VOTE] Release 1.18.0, release candidate #2
Hi Martijn,
Thanks for the hint. I am totally fine to cancel this RC and start a new
one. One thing I'd like to point out is that right after the sentence you
mentioned there is a "However":
"However, some issues don’t require cancellation. For example, if an issue
is found in the website pull request, just correct it on the spot and the
vote can continue as-is."[1]
The website pr is used as "an example", the issue we have now falls into
this "however" category, since no source code has been changed. WDYT?
Best regards,
Jing
[1]
https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release
On Wed, Oct 18, 2023 at 8:42 AM Martijn Visser
wrote:
> Hi Jing,
>
> Looking at the defined process for Creating A Flink Release [1], it
> states "If there are any issues found in the release candidate, reply
> on the vote thread to cancel the vote". With emphasis on the "any
> issues", I think we should cancel this RC and create a new one.
>
> Best regards,
>
> Martijn
>
> [1]
> https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release
>
> On Wed, Oct 18, 2023 at 4:32 AM Xianxun Ye
> wrote:
> >
> > Hi Jing,
> >
> > I also found the exception about the java.lang.NoSuchMethodError when I
> ran the Kyuubi Flink Tests on Flink1.18-rc2.
> >
> > These are the steps, ran the below sql in the Flink SQL Client:
> >
> > create table tbl_src (a int) with ('connector' = 'datagen',
> 'number-of-rows' = '100’);
> >
> > select count(a) from tbl_src;
> >
> > Could you also update flink1.18-rc2 bianry release[1]
> >
> > [1] https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc2/
> >
> > Best regards,
> > Xianxun
> >
> > > 2023年10月18日 10:24，Yun Tang 写道：
> > >
> > > Hi Jing,
> > >
> > > Thanks for the update, I checked the new maven repo, and the artifacts
> were built with JDK8 correctly.
> > >
> > >
> > > Best
> > > Yun Tang
> > >
> > > From: Jing Ge
> > > Sent: Tuesday, October 17, 2023 23:31
> > > To: dev@flink.apache.org
> > > Cc: Matthias Pohl ; sergey.nuyan...@aiven.io <
> sergey.nuyan...@aiven.io>
> > > Subject: Re: [VOTE] Release 1.18.0, release candidate #2
> > >
> > > Hi Yun,
> > >
> > > I have created a new maven repo[5]. Would you like to check it out?
> Thanks
> > > for your support! Once I get your confirmation, I will start the second
> > > voting thread with the title "[VOTE][2] Release 1.18.0, release
> candidate
> > > #2", because the source code is not changed.
> > >
> > > All Devs: please ignore this thread. I will start a new one as I
> > > mentioned above.
> > >
> > > Best regards,
> > > Jing
> > >
> > > [5]
> https://repository.apache.org/content/repositories/orgapacheflink-1659
> > >
> > > On Tue, Oct 17, 2023 at 3:53 PM Jing Ge wrote:
> > >
> > >> Hi Yun,
> > >>
> > >> Thanks for the feedback. Appreciate it! I will update them
> accordingly and
> > >> then ask you for double checking. Thanks in advance.
> > >>
> > >> Best regards,
> > >> Jing
> > >>
> > >> On Tue, Oct 17, 2023 at 2:42 PM Yun Tang wrote:
> > >>
> > >>> Hi Jing,
> > >>>
> > >>> Thanks for the update. I checked the new pre-built binary release,
> and it
> > >>> works fine now. However, I then checked the pre-built jar packages
> and
> > >>> found they are also built with JDK17, e.g., flink-runtime.jar [1].
> > >>>
> > >>> I think we also need to update all artifacts to be deployed.
> > >>>
> > >>>
> > >>> [1]
> > >>>
> https://repository.apache.org/content/repositories/orgapacheflink-1658/org/apache/flink/flink-runtime/1.18.0/flink-runtime-1.18.0.jar
> > >>>
> > >>> Best,
> > >>> Yun Tang
> > >>>
> > >>>
> > >>>
> > >>> From: Matthias Pohl
> > >>> Sent: Tuesday, October 17, 2023 20:38
> > >>> To: dev@flink.apache.org
> > >>> Cc: Yun Tang ; sergey.nuyan...@aiven.io <
> > >>> sergey.nuyan...@aiven.io>
> > >>> Subject: Re: [VOTE] Release 1.18.0, release candidate #2
> > >>>
> > >>> Great catch, Yun Tang. I created FLINK-33291 [1] to cover the issue
> of
> > >>> enforcing the JDK (and Maven) version in the release profile.
> > >>>
> > >>> [1] https://issues.apache.org/jira/browse/FLINK-33291
> > >>>
> > >>> On Tue, Oct 17, 2023 at 1:28 PM Jing Ge
> > >>> wrote:
> > >>> Hi Folks,
> > >>>
> > >>> I have rebuilt Flink with Java 8 and replaced all binary artifacts
> at[3].
> > >>> @Yun
> > >>> Tang mailto:myas...@live.com>> Would you please
> check
> > >>> it again? Thanks!
> > >>>
> > >>> BTW, there was a typo in the voting mail:
> > >>>
> > > * source code tag "release-1.17.0-rc2" [6]
> > >>> it should be:
> > >>> source code tag "release-1.18.0-rc2" [6]
> > >>>
> > >>> Sorry for the inconvenience caused.
> > >>>
> > >>> Special thanks for @sergey.nuyan...@aiven.io > >>> sergey.nuyan...@aiven.io> > >>> sergey.nuyan...@aiven.io>> who
> > >>> helps double check the new binary files and found the typo.
> > >>>
> > >>> Best regards,
> > >>> Jing
> > >>>
> > >>> [3] https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc2
> > >>> <
Re: [VOTE] Release 1.18.0, release candidate #2
Hi Jing,
Looking at the defined process for Creating A Flink Release [1], it
states "If there are any issues found in the release candidate, reply
on the vote thread to cancel the vote". With emphasis on the "any
issues", I think we should cancel this RC and create a new one.
Best regards,
Martijn
[1] https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release
On Wed, Oct 18, 2023 at 4:32 AM Xianxun Ye wrote:
>
> Hi Jing,
>
> I also found the exception about the java.lang.NoSuchMethodError when I ran
> the Kyuubi Flink Tests on Flink1.18-rc2.
>
> These are the steps, ran the below sql in the Flink SQL Client:
>
> create table tbl_src (a int) with ('connector' = 'datagen', 'number-of-rows'
> = '100’);
>
> select count(a) from tbl_src;
>
> Could you also update flink1.18-rc2 bianry release[1]
>
> [1] https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc2/
>
> Best regards,
> Xianxun
>
> > 2023年10月18日 10:24，Yun Tang 写道：
> >
> > Hi Jing,
> >
> > Thanks for the update, I checked the new maven repo, and the artifacts were
> > built with JDK8 correctly.
> >
> >
> > Best
> > Yun Tang
> >
> > From: Jing Ge
> > Sent: Tuesday, October 17, 2023 23:31
> > To: dev@flink.apache.org
> > Cc: Matthias Pohl ; sergey.nuyan...@aiven.io
> >
> > Subject: Re: [VOTE] Release 1.18.0, release candidate #2
> >
> > Hi Yun,
> >
> > I have created a new maven repo[5]. Would you like to check it out? Thanks
> > for your support! Once I get your confirmation, I will start the second
> > voting thread with the title "[VOTE][2] Release 1.18.0, release candidate
> > #2", because the source code is not changed.
> >
> > All Devs: please ignore this thread. I will start a new one as I
> > mentioned above.
> >
> > Best regards,
> > Jing
> >
> > [5] https://repository.apache.org/content/repositories/orgapacheflink-1659
> >
> > On Tue, Oct 17, 2023 at 3:53 PM Jing Ge wrote:
> >
> >> Hi Yun,
> >>
> >> Thanks for the feedback. Appreciate it! I will update them accordingly and
> >> then ask you for double checking. Thanks in advance.
> >>
> >> Best regards,
> >> Jing
> >>
> >> On Tue, Oct 17, 2023 at 2:42 PM Yun Tang wrote:
> >>
> >>> Hi Jing,
> >>>
> >>> Thanks for the update. I checked the new pre-built binary release, and it
> >>> works fine now. However, I then checked the pre-built jar packages and
> >>> found they are also built with JDK17, e.g., flink-runtime.jar [1].
> >>>
> >>> I think we also need to update all artifacts to be deployed.
> >>>
> >>>
> >>> [1]
> >>> https://repository.apache.org/content/repositories/orgapacheflink-1658/org/apache/flink/flink-runtime/1.18.0/flink-runtime-1.18.0.jar
> >>>
> >>> Best,
> >>> Yun Tang
> >>>
> >>>
> >>>
> >>> From: Matthias Pohl
> >>> Sent: Tuesday, October 17, 2023 20:38
> >>> To: dev@flink.apache.org
> >>> Cc: Yun Tang ; sergey.nuyan...@aiven.io <
> >>> sergey.nuyan...@aiven.io>
> >>> Subject: Re: [VOTE] Release 1.18.0, release candidate #2
> >>>
> >>> Great catch, Yun Tang. I created FLINK-33291 [1] to cover the issue of
> >>> enforcing the JDK (and Maven) version in the release profile.
> >>>
> >>> [1] https://issues.apache.org/jira/browse/FLINK-33291
> >>>
> >>> On Tue, Oct 17, 2023 at 1:28 PM Jing Ge
> >>> wrote:
> >>> Hi Folks,
> >>>
> >>> I have rebuilt Flink with Java 8 and replaced all binary artifacts at[3].
> >>> @Yun
> >>> Tang mailto:myas...@live.com>> Would you please check
> >>> it again? Thanks!
> >>>
> >>> BTW, there was a typo in the voting mail:
> >>>
> > * source code tag "release-1.17.0-rc2" [6]
> >>> it should be:
> >>> source code tag "release-1.18.0-rc2" [6]
> >>>
> >>> Sorry for the inconvenience caused.
> >>>
> >>> Special thanks for @sergey.nuyan...@aiven.io >>> sergey.nuyan...@aiven.io> >>> sergey.nuyan...@aiven.io>> who
> >>> helps double check the new binary files and found the typo.
> >>>
> >>> Best regards,
> >>> Jing
> >>>
> >>> [3] https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc2
> >>> <
> >>> https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc2/flink-1.18.0-bin-scala_2.12.tgz
>
> >>>
> >>> [6] https://github.com/apache/flink/releases/tag/release-1.18.0-rc2
> >>>
> >>> On Tue, Oct 17, 2023 at 12:27 PM Jing Ge >>> j...@ververica.com>> wrote:
> >>>
> Thanks Chesnay for the hint! Appreciate it!
>
>
> >>> Best regards,
> Jing
>
> On Tue, Oct 17, 2023 at 11:21 AM Chesnay Schepler >>> >
> wrote:
>
> > IIRC releases MUST be built with JDK 8.
> >
> > @Yun Tang how did you discover this?
> >
> > There is supposed to be a check to enforce this, but weirdly enough it
> > isn't rejecting my JDK 11 installation :/
> > Ah, we didn't set up the enforcer plugin correctly; while we do set a
> > required JDK version by default this is interpreted as ">=", so
> >>> anything
> > above or equal 8 is currently accepted...
> >
> > On
