[jira] [Created] (FLINK-25917) Share RpcSystem aross tests

Chesnay Schepler created FLINK-25917: Summary: Share RpcSystem aross tests Key: FLINK-25917 URL: https://issues.apache.org/jira/browse/FLINK-25917 Project: Flink Issue Type: Technical

[jira] [Created] (FLINK-25913) Disable japicmp binary compatibility check

Chesnay Schepler created FLINK-25913: Summary: Disable japicmp binary compatibility check Key: FLINK-25913 URL: https://issues.apache.org/jira/browse/FLINK-25913 Project: Flink Issue

[jira] [Created] (FLINK-25905) Promoting Experimental methods is marked as a violation

Chesnay Schepler created FLINK-25905: Summary: Promoting Experimental methods is marked as a violation Key: FLINK-25905 URL: https://issues.apache.org/jira/browse/FLINK-25905 Project: Flink

[jira] [Created] (FLINK-25894) Explicitly configure japicmp oldVersion for flink-streaming-java

Chesnay Schepler created FLINK-25894: Summary: Explicitly configure japicmp oldVersion for flink-streaming-java Key: FLINK-25894 URL: https://issues.apache.org/jira/browse/FLINK-25894 Project

Re: [DISCUSS] FLIP-211: Kerberos delegation token framework

You should have permissions now. Note that I saw 2 accounts matching your name, and I picked gaborgsomogyi. On 31/01/2022 11:28, Gabor Somogyi wrote: Not sure if the mentioned write right already given or not but I still don't see any edit button. G On Fri, Jan 28, 2022 at 5:08 PM Gabor

[jira] [Created] (FLINK-25888) Capture time that the job spends on deploying tasks

Chesnay Schepler created FLINK-25888: Summary: Capture time that the job spends on deploying tasks Key: FLINK-25888 URL: https://issues.apache.org/jira/browse/FLINK-25888 Project: Flink

[jira] [Created] (FLINK-25886) Hard-coded ZK version in FlinkContainersBuilder#buildZookeeperContainer

Chesnay Schepler created FLINK-25886: Summary: Hard-coded ZK version in FlinkContainersBuilder#buildZookeeperContainer Key: FLINK-25886 URL: https://issues.apache.org/jira/browse/FLINK-25886

[jira] [Created] (FLINK-25868) Enable japicmp for all modules

Chesnay Schepler created FLINK-25868: Summary: Enable japicmp for all modules Key: FLINK-25868 URL: https://issues.apache.org/jira/browse/FLINK-25868 Project: Flink Issue Type: Technical

[jira] [Created] (FLINK-25808) JsonTypeInfo property should be valid java identifier

Chesnay Schepler created FLINK-25808: Summary: JsonTypeInfo property should be valid java identifier Key: FLINK-25808 URL: https://issues.apache.org/jira/browse/FLINK-25808 Project: Flink

[jira] [Created] (FLINK-25807) Generated SubtaskExecutionAttemptDetailsInfo contains duplicate property

Chesnay Schepler created FLINK-25807: Summary: Generated SubtaskExecutionAttemptDetailsInfo contains duplicate property Key: FLINK-25807 URL: https://issues.apache.org/jira/browse/FLINK-25807

Re: [DISCUSS] Host StatefulFunction JavaScript SDK on npm

not. Cheers, Till On Mon, Jan 24, 2022 at 4:14 PM Chesnay Schepler wrote: What is your explanation for the comment in the ticket then? On 24/01/2022 16:07, Till Rohrmann wrote: I am not sure whether this is really a problem. There are other Apache projects that publish their artifacts on npm

Re: [DISCUSS] Host StatefulFunction JavaScript SDK on npm

/release-policy.html#release-distribution Cheers, Till On Mon, Jan 24, 2022 at 3:54 PM Chesnay Schepler wrote: I'm concerned about a comment in https://issues.apache.org/jira/browse/INFRA-19733 stating that npm is not an approved release channel. I don't really know what to make

Re: [DISCUSS] Host StatefulFunction JavaScript SDK on npm

I'm concerned about a comment in https://issues.apache.org/jira/browse/INFRA-19733 stating that npm is not an approved release channel. I don't really know what to make of it and neither the current nor past versions of the linked legal page shed some light on it. As such it would be a good

[jira] [Created] (FLINK-25784) SerializedThrowable(De)Serializer out of sync

Chesnay Schepler created FLINK-25784: Summary: SerializedThrowable(De)Serializer out of sync Key: FLINK-25784 URL: https://issues.apache.org/jira/browse/FLINK-25784 Project: Flink Issue

[jira] [Created] (FLINK-25776) Sync netty bugfix version across the project

Chesnay Schepler created FLINK-25776: Summary: Sync netty bugfix version across the project Key: FLINK-25776 URL: https://issues.apache.org/jira/browse/FLINK-25776 Project: Flink Issue

[jira] [Created] (FLINK-25773) Upgrade to flink-shaded 15.0

Chesnay Schepler created FLINK-25773: Summary: Upgrade to flink-shaded 15.0 Key: FLINK-25773 URL: https://issues.apache.org/jira/browse/FLINK-25773 Project: Flink Issue Type: Technical

[ANNOUNCE] flink-shaded 15.0 released

Hello everyone, we got a new flink-shaded release, with several nifty things: * updated version for ASM, required for Java 17 * jackson extensions for optionals/datetime, which will be used by the Table API (and maybe REST API) * a relocated version of swagger, finally unblocking the

[jira] [Created] (FLINK-25759) Upgrade to flink-shaded 15.0

Chesnay Schepler created FLINK-25759: Summary: Upgrade to flink-shaded 15.0 Key: FLINK-25759 URL: https://issues.apache.org/jira/browse/FLINK-25759 Project: Flink Issue Type: Technical

Re: [VOTE] Release flink-shaded 15.0, release candidate #2

The vote time has passed and we have unanimously approved this release. binding votes: * piotr * till * chesnay On 21/01/2022 15:30, Chesnay Schepler wrote: +1 (binding) On 19/01/2022 17:03, Till Rohrmann wrote: +1 (binding) * Checked checksums and signatures * Looked at the diff between

Re: [VOTE] Release flink-shaded 15.0, release candidate #2

..15.0-rc2, and 15.0-rc1..15.0-rc2, and didn't find anything suspicious. Best, Piotrek wt., 18 sty 2022 o 14:37 Chesnay Schepler napisał(a): Hi everyone, Please review and vote on the release candidate #2 for the version 15.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve

[jira] [Created] (FLINK-25732) Dispatcher#requestMultipleJobDetails returns non-serialiable collection

Chesnay Schepler created FLINK-25732: Summary: Dispatcher#requestMultipleJobDetails returns non-serialiable collection Key: FLINK-25732 URL: https://issues.apache.org/jira/browse/FLINK-25732

Re: [VOTE] FLIP-201: Persist local state in working directory

+1 (binding) On 19/01/2022 17:23, Matthias Pohl wrote: +1 (binding) Best, Matthias On Mon, Jan 10, 2022 at 2:53 PM Till Rohrmann wrote: +1 (binding) Cheers, Till On Mon, Jan 10, 2022 at 2:30 PM Etienne Chauchot wrote: +1 Best Etienne Chauchot Le 10/01/2022 à 10:22, Till Rohrmann a

[jira] [Created] (FLINK-25707) AdaptiveScheduler never transitions executions into SCHEDULED state

Chesnay Schepler created FLINK-25707: Summary: AdaptiveScheduler never transitions executions into SCHEDULED state Key: FLINK-25707 URL: https://issues.apache.org/jira/browse/FLINK-25707 Project

[VOTE] Release flink-shaded 15.0, release candidate #2

Hi everyone, Please review and vote on the release candidate #2 for the version 15.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], *

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

+1 (binding) Went over the pom changes and double-checked licensing. On 17/01/2022 10:44, Timo Walther wrote: +1 (binding) I had an offline chat with Fabian Paul about the mentioned changes. The serializer changes should be acceptable as the migration would have failed/stuck otherwise. At

[jira] [Created] (FLINK-25658) Setup Nexus npm cache

Chesnay Schepler created FLINK-25658: Summary: Setup Nexus npm cache Key: FLINK-25658 URL: https://issues.apache.org/jira/browse/FLINK-25658 Project: Flink Issue Type: Technical Debt

Re: [DISCUSS] Move Flink website to privacy friendly Analytics solution

+1 On 14/01/2022 14:47, Till Rohrmann wrote: Hi Martijn, big +1 for this effort. Thanks a lot for pushing this initiative forward! Cheers, Till On Fri, Jan 14, 2022 at 11:49 AM Konstantin Knauf wrote: Hi Martijn, I think this is a great initiative. Thank you for pursuing this. It allows

Re: Could not find any factory for identifier 'jdbc'

: Chesnay Schepler mailto:ches...@apache.org>> Date: Tuesday, 11 January 2022 at 7:45 PM To: Ronak Beejawat (rbeejawa) mailto:rbeej...@cisco.com.INVALID>>, u...@flink.apache.org<mailto:u...@flink.apache.org> mailto:u...@flink.apache.org>> Cc: Hang Ruan mailto:ruanhang1...@gmai

Re: what is efficient way to write Left join in flink

Your best bet is to try out both approaches with some representative data. On 12/01/2022 08:11, Ronak Beejawat (rbeejawa) wrote: Hi Team, Can you please help me with the below query, I wanted to know which approach will be better and efficient for multiple left join within one min tumbling

[jira] [Created] (FLINK-25613) Remove excessive surefire-plugin versions

Chesnay Schepler created FLINK-25613: Summary: Remove excessive surefire-plugin versions Key: FLINK-25613 URL: https://issues.apache.org/jira/browse/FLINK-25613 Project: Flink Issue Type

Re: [DISCUSS] Releasing Flink 1.14.3

le of days before this is merged. * https://issues.apache.org/jira/browse/FLINK-25022 - ClassLoader leak with ThreadLocals on the JM when submitting a job through the REST API -> @Chesnay Schepler has provided a PR, so I suspect it would also just take a couple of days b

Re: [VOTE][CANCELED] Release flink-shaded 15.0, release candidate #1

FLINK-25588 has been put onto the agenda for the next flink-shaded release, so we might as well cancel this vote to cover everything at once. On 14/12/2021 09:57, Chesnay Schepler wrote: Hi everyone, Please review and vote on the release candidate #1 for the version 15.0, as follows: [ ] +1

[jira] [Created] (FLINK-25611) Remove CoordinatorExecutorThreadFactory thread creation guards

Chesnay Schepler created FLINK-25611: Summary: Remove CoordinatorExecutorThreadFactory thread creation guards Key: FLINK-25611 URL: https://issues.apache.org/jira/browse/FLINK-25611 Project

Re: [DISCUSS] FLIP-210: Change logging level dynamically at runtime

become quite an effort. (by Chesnay Schepler) I tried to design the API of the logging backend to stay away from the details of implementations but I did not find any slf4j-specific API that is available to change the log level of a logger. So what I did is to introduce another kind of abstraction

Re: [DISCUSS] Slimmed down docker images.

There could be a problem with the fat image actually depending on the slim version; I'm not sure if the official-images repo supports that. We should however be able to generate 2 separate standalone dockerfiles. On 23/12/2021 11:16, Till Rohrmann wrote: Hi David, Thanks for starting this

Re: [DISCUSS] Creating an external connector repository

repository into ASF after ensuring Flink coding standards. Then we retain git history and Github issues. Is there any point that I'm missing? On Fri, Nov 26, 2021 at 1:32 PM Chesnay Schepler < ches...@apache.org> wrote: For sharing workflows we should be able to use composite acti

Re: [ANNOUNCE] Apache Flink 1.14.2 / 1.13.5 / 1.12.7 / 1.11.6 released

Please see the blogpost. On 17/12/2021 06:59, casel.chen wrote: I can NOT find flink 1.13.5 related jar in maven central repository, did you upload them onto there already? Thanks! At 2021-12-17 01:26:19, "Chesnay Schepler" wrote: >The Apache Flink community has relea

Re: [ANNOUNCE] Apache Flink 1.14.2 / 1.13.5 / 1.12.7 / 1.11.6 released

We are aware of that; it was also mentioned in the blogpost. On 17/12/2021 07:17, wenlong.lwl wrote: Hi, @Chesnay Schepler I want to forward a feedback from the user mailing list, the jars of the new patch releases are not available at the central maven repo. example: https

Re: [DISCUSS] Immediate dedicated StateFun releases for log4j vulnerability

+1 On 16/12/2021 19:30, Igal Shilman wrote: Hi All, Following the recent Apache Flink releases due to the log4j vulnerability, I'd like to propose an immediate StateFun release - 3.1.1. This release is basically the same as 3.1 but updates the Flink dependency to 1.13.3. Please raise your

[ANNOUNCE] Apache Flink 1.14.2 / 1.13.5 / 1.12.7 / 1.11.6 released

The Apache Flink community has released emergency bugfix versions of Apache Flink for the 1.11, 1.12, 1.13 and 1.14 series. These releases include a version upgrade for Log4j to address [CVE-2021-44228](https://nvd.nist.gov/vuln/detail/CVE-2021-44228) and

Re: [VOTE] FLIP-198: Working directory for Flink processes

+1 On 16/12/2021 14:42, Till Rohrmann wrote: Hi everyone, I'd like to start a vote on FLIP-198: Working directory for Flink processes [1] which has been discussed in this thread [2]. The vote will be open for at least 72 hours unless there is an objection or not enough votes. [1]

Re: [DISCUSS] GHA migration roadmap

We will not use Apache resources, but install self-hosted runners on our current CI machines, similar to what we have done with Azure. On 16/12/2021 16:07, Fabian Paul wrote: Hi Nico, Thanks a lot for drafting the proposal. I really like the fully-fledged phasing model. All in all, I am +1 to

Re: [VOTE] Release 1.11.6/1.12.7/1.13.5/1.14.2, release candidate #1

-1.11.6 Tagger: Chesnay Schepler Date:   Thu Dec 16 04:12:44 2021 +0100 Release Flink 1.11.6 <...> commit 88d9950bb2c912772c46c676fc0988026ce0a529 (tag: release-1.12.7-rc1, tag: release-1.12.7, tag: release-1.11.6) Author: Chesnay Schepler Date:   Tue Dec 14 23:39:33 2021 +0100    

Re: [VOTE] Release 1.11.6/1.12.7/1.13.5/1.14.2, release candidate #1

The vote duration has passed and we have approved the releases. Binding votes: * Till * Yu * Stephan I will now finalize the release. Let's hope this time no new CVE pops up... On 15/12/2021 03:55, Chesnay Schepler wrote: Hi everyone, This vote is for the emergency patch releases for 1.11

Re: [VOTE] Release 1.11.6/1.12.7/1.13.5/1.14.2, release candidate #1

Ah actually we may have to merge another commit into the release branches for that to be the case for 1.11/1.12. Anyway, I still wouldn't block the release on that. On 16/12/2021 02:03, Chesnay Schepler wrote: That's not a problem as far as I'm concerned, because the documentation

Re: [VOTE] Release 1.11.6/1.12.7/1.13.5/1.14.2, release candidate #1

for driving these releases Chesnay! Best Regards, Yu On Wed, 15 Dec 2021 at 21:29, Chesnay Schepler wrote: FYI; the publication of the python release for 1.11/1.12 will be delayed because we hit the project size limit on pypi again, and increasing that limit may take a while. On the positiv

[jira] [Created] (FLINK-25331) Allow testcontainer tests to run on Java 11

Chesnay Schepler created FLINK-25331: Summary: Allow testcontainer tests to run on Java 11 Key: FLINK-25331 URL: https://issues.apache.org/jira/browse/FLINK-25331 Project: Flink Issue

Re: [VOTE] Release 1.11.6/1.12.7/1.13.5/1.14.2, release candidate #1

FYI; the publication of the python release for 1.11/1.12 will be delayed because we hit the project size limit on pypi again, and increasing that limit may take a while. On the positive side, this gives us more time to fix the mac builds. On 15/12/2021 03:55, Chesnay Schepler wrote: Hi

Re: [CANCELLED] Release 1.11.5/1.12.6/1.13.4/1.14.1, release candidate #1

, 2021 at 11:18 PM Seth Wiesman wrote: Thank you for managing these updates Chesnay! On Tue, Dec 14, 2021 at 3:51 PM Chesnay Schepler wrote: Since the maven artifacts have already been published we will use the next patch version for each release, i.e.: 1.11.6 1.12.7 1.13.5 1.14.2 (We could

Re: [DISCUSS] FLIP-198: Working directory for Flink processes

their own disk schedule strategy. Chesnay Schepler 于2021年12月12日周日 19:59写道： How do you intend to handle corrupted files, in particular due to process crashes during a write? Will all writes to a cached directory append some suffix (e.g., ".pending") and do a rename? On 10/12/2021 1

Re: [VOTE] Release 1.11.6/1.12.7/1.13.5/1.14.2, release candidate #1

the JIRA release notes and found that FLINK-25317 [1] was tagged as 1.14.2 version to resolve by mistake. [1] https://issues.apache.org/jira/browse/FLINK-25317 Best Yun Tang From: Chesnay Schepler Sent: Wednesday, December 15, 2021 10:55 To: dev@flink.apache.org

[VOTE] Release 1.11.6/1.12.7/1.13.5/1.14.2, release candidate #1

Hi everyone, This vote is for the emergency patch releases for 1.11, 1.12, 1.13 and 1.14 to address CVE-2021-44228/CVE-2021-45046. It covers all 4 releases as they contain the same changes (upgrading Log4j to 2.16.0) and were prepared simultaneously by the same person. (Hence, if something is

Re: [CANCELLED] Release 1.11.5/1.12.6/1.13.4/1.14.1, release candidate #1

Since the maven artifacts have already been published we will use the next patch version for each release, i.e.: 1.11.6 1.12.7 1.13.5 1.14.2 (We could technically just update the source/binaries, but that seems fishy). On 14/12/2021 22:38, Chesnay Schepler wrote: I'm canceling the release

[CANCELLED] Release 1.11.5/1.12.6/1.13.4/1.14.1, release candidate #1

I'm canceling the release because the issue was not fully fixed in Log4j 2.15.0; see CVE-2021-45046. I will start preparing new release candidates that use Log4j 2.16.0 . On 14/12/2021 21:28, Chesnay Schepler wrote: The vote duration has passed and we have approved the releases. Binding

Re: [VOTE] Release 1.11.5/1.12.6/1.13.4/1.14.1, release candidate #1

The vote duration has passed and we have approved the releases. Binding votes: * Stephan * Till * Xintong * Zhu * Gordon I will not finalize the release. On 13/12/2021 20:28, Chesnay Schepler wrote: Hi everyone, This vote is for the emergency patch releases for 1.11, 1.12, 1.13 and 1.14

[jira] [Created] (FLINK-25302) Find a way to keep release guides for previous releases

Chesnay Schepler created FLINK-25302: Summary: Find a way to keep release guides for previous releases Key: FLINK-25302 URL: https://issues.apache.org/jira/browse/FLINK-25302 Project: Flink

[jira] [Created] (FLINK-25301) Add a separate script for signing binaries

Chesnay Schepler created FLINK-25301: Summary: Add a separate script for signing binaries Key: FLINK-25301 URL: https://issues.apache.org/jira/browse/FLINK-25301 Project: Flink Issue

[jira] [Created] (FLINK-25298) Create docker image for release environment

Chesnay Schepler created FLINK-25298: Summary: Create docker image for release environment Key: FLINK-25298 URL: https://issues.apache.org/jira/browse/FLINK-25298 Project: Flink Issue

Re: [VOTE] Release 1.11.5/1.12.6/1.13.4/1.14.1, release candidate #1

patch releases, Chesnay! Thank you~ Xintong Song On Tue, Dec 14, 2021 at 7:45 AM Chesnay Schepler wrote: I forgot to mention something important: The 1.11/1.12 releases do *NOT* contain flink-python releases for *mac* due to compile problems. On 13/12/2021 20:28, Chesnay Schepler wrote: Hi

[VOTE] Release flink-shaded 15.0, release candidate #1

Hi everyone, Please review and vote on the release candidate #1 for the version 15.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],

[jira] [Created] (FLINK-25297) Publich flink-shaded-swagger

Chesnay Schepler created FLINK-25297: Summary: Publich flink-shaded-swagger Key: FLINK-25297 URL: https://issues.apache.org/jira/browse/FLINK-25297 Project: Flink Issue Type: Improvement

Re: [VOTE] Release 1.11.5/1.12.6/1.13.4/1.14.1, release candidate #1

I forgot to mention something important: The 1.11/1.12 releases do *NOT* contain flink-python releases for *mac* due to compile problems. On 13/12/2021 20:28, Chesnay Schepler wrote: Hi everyone, This vote is for the emergency patch releases for 1.11, 1.12, 1.13 and 1.14 to address CVE

Re: [VOTE] Release 1.11.5/1.12.6/1.13.4/1.14.1, release candidate #1

Update: All jars are now available. On 13/12/2021 20:28, Chesnay Schepler wrote: Hi everyone, This vote is for the emergency patch releases for 1.11, 1.12, 1.13 and 1.14 to address CVE-2021-44228. It covers all 4 releases as they contain the same changes (upgrading Log4j to 2.15.0) and were

[jira] [Created] (FLINK-25283) End-to-end application modules create oversized jars

Chesnay Schepler created FLINK-25283: Summary: End-to-end application modules create oversized jars Key: FLINK-25283 URL: https://issues.apache.org/jira/browse/FLINK-25283 Project: Flink

[VOTE] Release 1.11.5/1.12.6/1.13.4/1.14.1, release candidate #1

Hi everyone, This vote is for the emergency patch releases for 1.11, 1.12, 1.13 and 1.14 to address CVE-2021-44228. It covers all 4 releases as they contain the same changes (upgrading Log4j to 2.15.0) and were prepared simultaneously by the same person. (Hence, if something is broken, it

Re: [DISCUSS] Immediate dedicated Flink releases for log4j vulnerability

I will start preparing the release candidates. On 12/12/2021 23:23, Stephan Ewen wrote: Hi all! Without doubt, you heard about the log4j vulnerability [1]. There is an advisory blog post on how to mitigate this in Apache Flink [2], which involves setting a config option and restarting the

Re: [VOTE] FLIP-196: Source API stability guarantees

+1 On 10/12/2021 18:07, Till Rohrmann wrote: Hi everyone, I'd like to start a vote on FLIP-196: Source API stability guarantees [1] which has been discussed in this thread [2]. The vote will be open for at least 72 hours unless there is an objection or not enough votes. [1]

Re: [VOTE] FLIP-197: API stability graduation process

+1 On 10/12/2021 18:09, Till Rohrmann wrote: Hi everyone, I'd like to start a vote on FLIP-197: API stability graduation process [1] which has been discussed in this thread [2]. The vote will be open for at least 72 hours unless there is an objection or not enough votes. [1]

[jira] [Created] (FLINK-25266) StreamingKafkaITCase fails with incorrect number of messages

Chesnay Schepler created FLINK-25266: Summary: StreamingKafkaITCase fails with incorrect number of messages Key: FLINK-25266 URL: https://issues.apache.org/jira/browse/FLINK-25266 Project: Flink

Re: [DISCUSS] FLIP-198: Working directory for Flink processes

How do you intend to handle corrupted files, in particular due to process crashes during a write? Will all writes to a cached directory append some suffix (e.g., ".pending") and do a rename? On 10/12/2021 17:54, Till Rohrmann wrote: Hi everyone, I would like to start a discussion about

[jira] [Created] (FLINK-25263) KafkaSourceE2ECase is broken

Chesnay Schepler created FLINK-25263: Summary: KafkaSourceE2ECase is broken Key: FLINK-25263 URL: https://issues.apache.org/jira/browse/FLINK-25263 Project: Flink Issue Type: Technical

[jira] [Created] (FLINK-25252) Check whether Kafka E2E tests could be run on Java 11

Chesnay Schepler created FLINK-25252: Summary: Check whether Kafka E2E tests could be run on Java 11 Key: FLINK-25252 URL: https://issues.apache.org/jira/browse/FLINK-25252 Project: Flink

[jira] [Created] (FLINK-25251) Docker image should use Java 11 by default

Chesnay Schepler created FLINK-25251: Summary: Docker image should use Java 11 by default Key: FLINK-25251 URL: https://issues.apache.org/jira/browse/FLINK-25251 Project: Flink Issue

[jira] [Created] (FLINK-25250) Consider Java 11 as default version on CI

Chesnay Schepler created FLINK-25250: Summary: Consider Java 11 as default version on CI Key: FLINK-25250 URL: https://issues.apache.org/jira/browse/FLINK-25250 Project: Flink Issue Type

[jira] [Created] (FLINK-25248) Deprecate components that inherently require Java 8

Chesnay Schepler created FLINK-25248: Summary: Deprecate components that inherently require Java 8 Key: FLINK-25248 URL: https://issues.apache.org/jira/browse/FLINK-25248 Project: Flink

[jira] [Created] (FLINK-25247) Inform users about deprecation

Chesnay Schepler created FLINK-25247: Summary: Inform users about deprecation Key: FLINK-25247 URL: https://issues.apache.org/jira/browse/FLINK-25247 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-25246) Run benchmarks on Java 11

Chesnay Schepler created FLINK-25246: Summary: Run benchmarks on Java 11 Key: FLINK-25246 URL: https://issues.apache.org/jira/browse/FLINK-25246 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-25245) Allow Kubernetes E2E tests to run on Java 11

Chesnay Schepler created FLINK-25245: Summary: Allow Kubernetes E2E tests to run on Java 11 Key: FLINK-25245 URL: https://issues.apache.org/jira/browse/FLINK-25245 Project: Flink Issue

[jira] [Created] (FLINK-25244) Deprecate Java 8 support

Chesnay Schepler created FLINK-25244: Summary: Deprecate Java 8 support Key: FLINK-25244 URL: https://issues.apache.org/jira/browse/FLINK-25244 Project: Flink Issue Type: Improvement

Re: [VOTE] Deprecate Java 8 support

people let me know, let me update my vote to +1 (binding) (In all seriousness, thanks for the reminders!) On Mon, Dec 6, 2021, 16:54 Ingo Bürk wrote: +1 (non-binding) Ingo On Mon, Dec 6, 2021 at 4:44 PM Chesnay Schepler wrote: Hello, after recent discussions on the dev <ht

[jira] [Created] (FLINK-25210) PulsarSource(Un)OrderedE2ECase is brokern

Chesnay Schepler created FLINK-25210: Summary: PulsarSource(Un)OrderedE2ECase is brokern Key: FLINK-25210 URL: https://issues.apache.org/jira/browse/FLINK-25210 Project: Flink Issue Type

[jira] [Created] (FLINK-25209) SQLClientSchemaRegistryITCase#testReading is broken

Chesnay Schepler created FLINK-25209: Summary: SQLClientSchemaRegistryITCase#testReading is broken Key: FLINK-25209 URL: https://issues.apache.org/jira/browse/FLINK-25209 Project: Flink

Re: [DISCUSS] Drop Zookeeper 3.4

wrote: When should I prepare for upgrading ZK to 3.5 or newer? We're operating a Hadoop cluster w/ ZK 3.4.6 for running only Flink jobs. Just hope that the rolling update is not that painful - any advice on this? Best, Dongwon On Tue, Dec 7, 2021 at 3:22 AM Chesnay Schepler wrote

Re: [DISCUSS] Drop Zookeeper 3.4

, eventually deprecating old ZK, correct? If that is the only limitation, I'm +1 for the proposal since ZK 3.4 is already EOL. How are K8s users affected? Best, Arvid On Mon, Dec 6, 2021 at 2:00 PM Chesnay Schepler wrote: ping @users; any input on how this would affect you is highly

[VOTE] Deprecate Java 8 support

Hello, after recent discussions on the dev and user mailing list to deprecate Java 8 support, with a general consensus in favor of it, I would now like tod o

Re: [DISCUSS] Drop Zookeeper 3.4

ping @users; any input on how this would affect you is highly appreciated. On 25/11/2021 22:39, Chesnay Schepler wrote: I included the user ML in the thread. @users Are you still using Zookeeper 3.4? If so, were you planning to upgrade Zookeeper in the near future? I'm not sure about ZK

Re: [DISCUSS] FLIP-197: API stability graduation process

Given that you can delay the graduation if there is a good reason for it, we should be able to cover that case even if the graduation would happen by default after 1 month. That said, personally I would also be in favor of 2 releases; we see plenty of users not upgrading to every single Flink

[jira] [Created] (FLINK-25159) Streaming E2E surefire configuration setup

Chesnay Schepler created FLINK-25159: Summary: Streaming E2E surefire configuration setup Key: FLINK-25159 URL: https://issues.apache.org/jira/browse/FLINK-25159 Project: Flink Issue

[jira] [Created] (FLINK-25146) Drop support for Zookeeper 3.4

Chesnay Schepler created FLINK-25146: Summary: Drop support for Zookeeper 3.4 Key: FLINK-25146 URL: https://issues.apache.org/jira/browse/FLINK-25146 Project: Flink Issue Type

[jira] [Created] (FLINK-25145) Add support for Zookeeper 3.6

Chesnay Schepler created FLINK-25145: Summary: Add support for Zookeeper 3.6 Key: FLINK-25145 URL: https://issues.apache.org/jira/browse/FLINK-25145 Project: Flink Issue Type

Re: [DISCUSS] Deprecate Java 8 support

, wenlong.lwl wrote: hi, @Chesnay Schepler <mailto:ches...@apache.org> would you explain more about what would happen when deprecating Java 8, but still support it. IMO, if we still generate packages based on Java 8 which seems to be a consensus, we still can not take the advantages you men

[jira] [Created] (FLINK-25112) Remove TTL from e2e cache

Chesnay Schepler created FLINK-25112: Summary: Remove TTL from e2e cache Key: FLINK-25112 URL: https://issues.apache.org/jira/browse/FLINK-25112 Project: Flink Issue Type: Technical Debt

Re: [DISCUSS] Creating an external connector repository

n we guarantee the new Source and Sink API are stable with only test implementation? Best, Jark On Tue, 19 Oct 2021 at 23:56, Chesnay Schepler < ches...@apache.org> wrote: Could you clarify what release cadence you're thinking of? There's quite a big range that fits "mor

Re: [DISCUSS] Releasing Flink 1.14.1

FLINK-25022: I will open a PR later today, and it should be easy to backport. FLINK-25027: Unlikely to make it for 1.14.1; I also wouldn't consider it a blocker On 24/11/2021 19:40, Martijn Visser wrote: Hi all, I would like to start a discussion on releasing Flink 1.14.1. Flink 1.14 was

Re: [DISCUSS] Drop Zookeeper 3.4

, 2021 at 10:19 AM Chesnay Schepler wrote: Hello, I'd like to drop support for Zookeeper 3.4 in 1.15, upgrading the default to 3.5 with an opt-in for 3.6. Supporting Zookeeper 3.4 (which is already EOL) prevents us from upgrading Curator to 5.x, which would allow us to properly fix an issue

Re: [DISCUSS] PR component labeling

@Martijn do you need all the various sublabels, or would one like SQL or Connectors suffice? On 25/11/2021 16:28, Martijn Visser wrote: Hi Nico, I'm using the labels to filter on PRs that I find interesting (for example, I look at all the new or updated PRs that are related to SQL or

[jira] [Created] (FLINK-25064) Remove @VisibleForTesting from RestServerEndpoint#createUploadDir

Chesnay Schepler created FLINK-25064: Summary: Remove @VisibleForTesting from RestServerEndpoint#createUploadDir Key: FLINK-25064 URL: https://issues.apache.org/jira/browse/FLINK-25064 Project

[jira] [Created] (FLINK-25063) Allow calls to @VisibleForTesting from enclosing class

Chesnay Schepler created FLINK-25063: Summary: Allow calls to @VisibleForTesting from enclosing class Key: FLINK-25063 URL: https://issues.apache.org/jira/browse/FLINK-25063 Project: Flink

[jira] [Created] (FLINK-25059) Update code style guide to encourage usage of AssertJ

Chesnay Schepler created FLINK-25059: Summary: Update code style guide to encourage usage of AssertJ Key: FLINK-25059 URL: https://issues.apache.org/jira/browse/FLINK-25059 Project: Flink

Re: [DISCUSS] Deprecate Java 8 support

Users can already use APIs from Java 8/11. On 25/11/2021 09:35, Francesco Guardiani wrote: +1 with what both Ingo and Matthias sad, personally, I cannot wait to start using some of the APIs introduced in Java 9. And I'm pretty sure that's the same for our users as well. On Tuesday, 23

<    3   4   5   6   7   8   9   10   11   12   >