[jira] [Created] (FLINK-27222) Execution history limit can lead to eviction of critical local-recovery information

Chesnay Schepler created FLINK-27222: Summary: Execution history limit can lead to eviction of critical local-recovery information Key: FLINK-27222 URL: https://issues.apache.org/jira/browse/FLINK-27222

[jira] [Created] (FLINK-27206) Deprecate reflection-based reporter instantiation

Chesnay Schepler created FLINK-27206: Summary: Deprecate reflection-based reporter instantiation Key: FLINK-27206 URL: https://issues.apache.org/jira/browse/FLINK-27206 Project: Flink

[jira] [Created] (FLINK-27146) [JUnit5 Migration] Module: flink-filesystems

Chesnay Schepler created FLINK-27146: Summary: [JUnit5 Migration] Module: flink-filesystems Key: FLINK-27146 URL: https://issues.apache.org/jira/browse/FLINK-27146 Project: Flink Issue

[jira] [Created] (FLINK-27125) Tests leak executor services

Chesnay Schepler created FLINK-27125: Summary: Tests leak executor services Key: FLINK-27125 URL: https://issues.apache.org/jira/browse/FLINK-27125 Project: Flink Issue Type: Technical

[jira] [Created] (FLINK-27122) Remove FutureUtils#retryWithDelay variants without RetryStrategy

Chesnay Schepler created FLINK-27122: Summary: Remove FutureUtils#retryWithDelay variants without RetryStrategy Key: FLINK-27122 URL: https://issues.apache.org/jira/browse/FLINK-27122 Project

[jira] [Created] (FLINK-27119) Cleanup JobMasters

Chesnay Schepler created FLINK-27119: Summary: Cleanup JobMasters Key: FLINK-27119 URL: https://issues.apache.org/jira/browse/FLINK-27119 Project: Flink Issue Type: Technical Debt

[jira] [Created] (FLINK-27082) Disable tests relying on non-writable directories

Chesnay Schepler created FLINK-27082: Summary: Disable tests relying on non-writable directories Key: FLINK-27082 URL: https://issues.apache.org/jira/browse/FLINK-27082 Project: Flink

[jira] [Created] (FLINK-27081) Remove Azure integration

Chesnay Schepler created FLINK-27081: Summary: Remove Azure integration Key: FLINK-27081 URL: https://issues.apache.org/jira/browse/FLINK-27081 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-27080) Enable builds for pull requests

Chesnay Schepler created FLINK-27080: Summary: Enable builds for pull requests Key: FLINK-27080 URL: https://issues.apache.org/jira/browse/FLINK-27080 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-27079) Setup cron jobs

Chesnay Schepler created FLINK-27079: Summary: Setup cron jobs Key: FLINK-27079 URL: https://issues.apache.org/jira/browse/FLINK-27079 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-27077) Setup per-commit builds for master

Chesnay Schepler created FLINK-27077: Summary: Setup per-commit builds for master Key: FLINK-27077 URL: https://issues.apache.org/jira/browse/FLINK-27077 Project: Flink Issue Type: Sub

[jira] [Created] (FLINK-27076) Setup runners

Chesnay Schepler created FLINK-27076: Summary: Setup runners Key: FLINK-27076 URL: https://issues.apache.org/jira/browse/FLINK-27076 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-27075) Migrate CI from Azure to Github Actions

Chesnay Schepler created FLINK-27075: Summary: Migrate CI from Azure to Github Actions Key: FLINK-27075 URL: https://issues.apache.org/jira/browse/FLINK-27075 Project: Flink Issue Type

[jira] [Created] (FLINK-27074) python_job.py should write to TEST_DATA_DIR

Chesnay Schepler created FLINK-27074: Summary: python_job.py should write to TEST_DATA_DIR Key: FLINK-27074 URL: https://issues.apache.org/jira/browse/FLINK-27074 Project: Flink Issue

[NOTICE] Migration to GitHub Actions

Over the next few weeks we will conduct the migration to github actions. We will do this gradually; first enabling it only for pushes to the master branch to gather data, and then bit by bit extend it to cover PRs as well. You can expect this to conclude within the next 2-3 weeks. During thi

[jira] [Created] (FLINK-27047) DispatcherResourceCleanupTest is unstable

Chesnay Schepler created FLINK-27047: Summary: DispatcherResourceCleanupTest is unstable Key: FLINK-27047 URL: https://issues.apache.org/jira/browse/FLINK-27047 Project: Flink Issue Type

[jira] [Created] (FLINK-27045) Remove shared TestingUtils executor

Chesnay Schepler created FLINK-27045: Summary: Remove shared TestingUtils executor Key: FLINK-27045 URL: https://issues.apache.org/jira/browse/FLINK-27045 Project: Flink Issue Type

[jira] [Created] (FLINK-27042) StreamTaskITCase#testMailboxMetricsScheduling is unstable

Chesnay Schepler created FLINK-27042: Summary: StreamTaskITCase#testMailboxMetricsScheduling is unstable Key: FLINK-27042 URL: https://issues.apache.org/jira/browse/FLINK-27042 Project: Flink

[jira] [Created] (FLINK-27035) Reduce memory usage of ByteArrayWrapperSerializerTest

Chesnay Schepler created FLINK-27035: Summary: Reduce memory usage of ByteArrayWrapperSerializerTest Key: FLINK-27035 URL: https://issues.apache.org/jira/browse/FLINK-27035 Project: Flink

[jira] [Created] (FLINK-27034) Use testcontainers for google cloud pubsub e2e test

Chesnay Schepler created FLINK-27034: Summary: Use testcontainers for google cloud pubsub e2e test Key: FLINK-27034 URL: https://issues.apache.org/jira/browse/FLINK-27034 Project: Flink

[jira] [Created] (FLINK-27027) Get rid of oddly named mvn-${sys mvn.forkNumber}.log files

Chesnay Schepler created FLINK-27027: Summary: Get rid of oddly named mvn-${sys mvn.forkNumber}.log files Key: FLINK-27027 URL: https://issues.apache.org/jira/browse/FLINK-27027 Project: Flink

[jira] [Created] (FLINK-27026) Upgrade checkstyle plugin

Chesnay Schepler created FLINK-27026: Summary: Upgrade checkstyle plugin Key: FLINK-27026 URL: https://issues.apache.org/jira/browse/FLINK-27026 Project: Flink Issue Type: Technical Debt

[jira] [Created] (FLINK-27024) Cleanup surefire configuration

Chesnay Schepler created FLINK-27024: Summary: Cleanup surefire configuration Key: FLINK-27024 URL: https://issues.apache.org/jira/browse/FLINK-27024 Project: Flink Issue Type: Technical

[jira] [Created] (FLINK-26995) Enable fork-reuse for all unit tests

Chesnay Schepler created FLINK-26995: Summary: Enable fork-reuse for all unit tests Key: FLINK-26995 URL: https://issues.apache.org/jira/browse/FLINK-26995 Project: Flink Issue Type

[jira] [Created] (FLINK-26994) Merge libraries CI profile into core

Chesnay Schepler created FLINK-26994: Summary: Merge libraries CI profile into core Key: FLINK-26994 URL: https://issues.apache.org/jira/browse/FLINK-26994 Project: Flink Issue Type

[jira] [Created] (FLINK-26993) CheckpointCoordinatorTest#testMinCheckpointPause

Chesnay Schepler created FLINK-26993: Summary: CheckpointCoordinatorTest#testMinCheckpointPause Key: FLINK-26993 URL: https://issues.apache.org/jira/browse/FLINK-26993 Project: Flink

Re: Speeding up the test builds

ote that in the long-term we could look deeper parallelizing the tests using junit5 (again, what Francesco already started in the table tests), removing the need for forks entirely. On 31/03/2022 15:40, Chesnay Schepler wrote: > we decided to limit the number of testing forks/disable fork

Re: Speeding up the test builds

> we decided to limit the number of testing forks/disable fork reuse for almost all tests IT cases were generally not reusing forks for as long as I can remember. A few modules opted into fork-reuse; most didn't. The Table API recently enabled fork-reuse, started causing OOMs due to memory lea

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

in the NOTICE of the main project  (or some other appropriate place) but we do not explicitly list the dependencies. Would be good to hear how others feel about this! Gyula On Mon, Mar 28, 2022 at 5:26 PM Chesnay Schepler wrote: I don't think having users build the fat-jar &

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

therefore it's not part of the release. We release the Dockerfile instead so that users can build the image. Since the fatjar is not part of the release we do not have bundled dependencies, and we do not need extra licensing information I believe. Cheers, Gyula On Mon, Mar 28, 2022 at

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

There's some strange stuff in here. What exactly is the purpose of flink-kubernetes-shaded? You're just re-packaging flink-kubernetes without making any changes. The uploaded flink-kubernetes-operator jar isn't bundling any dependencies. Why is the fat jar not uploaded? Is it used anywhere el

[jira] [Created] (FLINK-26888) Add e2e tests for network partitions

Chesnay Schepler created FLINK-26888: Summary: Add e2e tests for network partitions Key: FLINK-26888 URL: https://issues.apache.org/jira/browse/FLINK-26888 Project: Flink Issue Type

[jira] [Created] (FLINK-26887) Drop Jepsen tests

Chesnay Schepler created FLINK-26887: Summary: Drop Jepsen tests Key: FLINK-26887 URL: https://issues.apache.org/jira/browse/FLINK-26887 Project: Flink Issue Type: Technical Debt

[jira] [Created] (FLINK-26886) Document reporter behavior w.r.t. scopes & push/pull

Chesnay Schepler created FLINK-26886: Summary: Document reporter behavior w.r.t. scopes & push/pull Key: FLINK-26886 URL: https://issues.apache.org/jira/browse/FLINK-26886 Project: F

[jira] [Created] (FLINK-26885) Cleanup MetricRegistryImplTest

Chesnay Schepler created FLINK-26885: Summary: Cleanup MetricRegistryImplTest Key: FLINK-26885 URL: https://issues.apache.org/jira/browse/FLINK-26885 Project: Flink Issue Type: Technical

[jira] [Created] (FLINK-26851) Properly model reporter options as ConfigOptions

Chesnay Schepler created FLINK-26851: Summary: Properly model reporter options as ConfigOptions Key: FLINK-26851 URL: https://issues.apache.org/jira/browse/FLINK-26851 Project: Flink

[jira] [Created] (FLINK-26850) Add MetricType enum

Chesnay Schepler created FLINK-26850: Summary: Add MetricType enum Key: FLINK-26850 URL: https://issues.apache.org/jira/browse/FLINK-26850 Project: Flink Issue Type: Improvement

[jira] [Created] (FLINK-26849) Deduplicate MetricRegistry code for (un)registering metrics with reporters

Chesnay Schepler created FLINK-26849: Summary: Deduplicate MetricRegistry code for (un)registering metrics with reporters Key: FLINK-26849 URL: https://issues.apache.org/jira/browse/FLINK-26849

[jira] [Created] (FLINK-26842) Remove flink-python Scala dependency

Chesnay Schepler created FLINK-26842: Summary: Remove flink-python Scala dependency Key: FLINK-26842 URL: https://issues.apache.org/jira/browse/FLINK-26842 Project: Flink Issue Type

[jira] [Created] (FLINK-26831) Move JarHandlers to flink-runtime

Chesnay Schepler created FLINK-26831: Summary: Move JarHandlers to flink-runtime Key: FLINK-26831 URL: https://issues.apache.org/jira/browse/FLINK-26831 Project: Flink Issue Type

Re: Flink cassandra connector performance issue

I'd be quite curious on what the analysis that the mapper isn't re-used is based on. A given CassandraPojoSink instance has been re-using the same mapper since it was added in 1.1: https://github.com/apache/flink/blob/release-1.1/flink-streaming-connectors/flink-connector-cassandra/src/main/java

[jira] [Created] (FLINK-26780) Add an option to force serialization for rpc invocations

Chesnay Schepler created FLINK-26780: Summary: Add an option to force serialization for rpc invocations Key: FLINK-26780 URL: https://issues.apache.org/jira/browse/FLINK-26780 Project: Flink

[jira] [Created] (FLINK-26779) StopWithSavepoint fails when called from standby JM

Chesnay Schepler created FLINK-26779: Summary: StopWithSavepoint fails when called from standby JM Key: FLINK-26779 URL: https://issues.apache.org/jira/browse/FLINK-26779 Project: Flink

[jira] [Created] (FLINK-26680) SessionDispatcherLeaderProcess#onAddJobGraph crashes if the job is marked as deleted

Chesnay Schepler created FLINK-26680: Summary: SessionDispatcherLeaderProcess#onAddJobGraph crashes if the job is marked as deleted Key: FLINK-26680 URL: https://issues.apache.org/jira/browse/FLINK-26680

[jira] [Created] (FLINK-26658) Migrate documentation generation to Github Actions

Chesnay Schepler created FLINK-26658: Summary: Migrate documentation generation to Github Actions Key: FLINK-26658 URL: https://issues.apache.org/jira/browse/FLINK-26658 Project: Flink

Re: [ANNOUNCE] release-1.15 branch cut

Correction: The fixVersion should not contain 1.15.0 and 1.16.0 at the same time, but only 1.15.0. On 14/03/2022 18:35, Yun Gao wrote: Hi devs, The release-1.15 branch has been forked out from the master branch, at the commit 9c77f13e587d7cb52469cac934c6aaec28dcd17d. Also, the version on the m

Re: [DISCUSS] Enable scala formatting check

Just merge it to master & release-1.15 after 1.15.0 is released. No impact on the current release, but also no issues with backports. On 10/03/2022 07:33, Jark Wu wrote: I also have some concerns because it's a huge change and the 1.15 will be released soon. I remember the last time when we mer

[jira] [Created] (FLINK-26547) Accepting slots without a matching requirement lead to unfulfillable requirements

Chesnay Schepler created FLINK-26547: Summary: Accepting slots without a matching requirement lead to unfulfillable requirements Key: FLINK-26547 URL: https://issues.apache.org/jira/browse/FLINK-26547

[jira] [Created] (FLINK-26352) Missing license header in WebUI source files

Chesnay Schepler created FLINK-26352: Summary: Missing license header in WebUI source files Key: FLINK-26352 URL: https://issues.apache.org/jira/browse/FLINK-26352 Project: Flink Issue

Re: [DISCUSS] Plan to externalize connectors and versioning

e Flink 1.16 release cycle) we do the same for other connectors like Kafka, Pulsar, Kinesis. I don't think it's feasible or helpful to make it a condition that this happens for all connectors at the same time. Cheers and thanks, Konstantin On Sun, Feb 20, 2022 at 7:57 PM Chesnay Scheple

[jira] [Created] (FLINK-26303) Print rat-plugin violations to the console

Chesnay Schepler created FLINK-26303: Summary: Print rat-plugin violations to the console Key: FLINK-26303 URL: https://issues.apache.org/jira/browse/FLINK-26303 Project: Flink Issue

[jira] [Created] (FLINK-26302) Upgrat rat-plugin to 1.13

Chesnay Schepler created FLINK-26302: Summary: Upgrat rat-plugin to 1.13 Key: FLINK-26302 URL: https://issues.apache.org/jira/browse/FLINK-26302 Project: Flink Issue Type: Technical Debt

[jira] [Created] (FLINK-26298) [JUnit5 Migration] Module: flink-rpc-core

Chesnay Schepler created FLINK-26298: Summary: [JUnit5 Migration] Module: flink-rpc-core Key: FLINK-26298 URL: https://issues.apache.org/jira/browse/FLINK-26298 Project: Flink Issue Type

Re: [DISCUSS] Plan to externalize connectors and versioning

on hint in the documentation. With regards to point 6, do you have an alternative? Would you prefer to remove a connector in a Flink patch release? Best regards, Martijn On Fri, 18 Feb 2022 at 16:17, Chesnay Schepler wrote: Why do you want to immediately do a release for the elasticsearch connec

Re: [DISCUSS] Plan to externalize connectors and versioning

Why do you want to immediately do a release for the elasticsearch connector? What does that provide us? I'd rather first have a fully working setup and integrated documentation before thinking about releasing anything. Once we have that we may be able to externalize all connectors within 1 rel

[jira] [Created] (FLINK-26253) Speed up detection fo dropped message in MessageSerializationTest

Chesnay Schepler created FLINK-26253: Summary: Speed up detection fo dropped message in MessageSerializationTest Key: FLINK-26253 URL: https://issues.apache.org/jira/browse/FLINK-26253 Project

[jira] [Created] (FLINK-26251) [JUnit5 Migration] Module: flink-rpc-akka

Chesnay Schepler created FLINK-26251: Summary: [JUnit5 Migration] Module: flink-rpc-akka Key: FLINK-26251 URL: https://issues.apache.org/jira/browse/FLINK-26251 Project: Flink Issue Type

[jira] [Created] (FLINK-26246) Setup JUnit 5 infrastructure for parallel test execution

Chesnay Schepler created FLINK-26246: Summary: Setup JUnit 5 infrastructure for parallel test execution Key: FLINK-26246 URL: https://issues.apache.org/jira/browse/FLINK-26246 Project: Flink

[jira] [Created] (FLINK-26244) [JUnit5 Migration] Module: flink-runtime-web

Chesnay Schepler created FLINK-26244: Summary: [JUnit5 Migration] Module: flink-runtime-web Key: FLINK-26244 URL: https://issues.apache.org/jira/browse/FLINK-26244 Project: Flink Issue

Re: [NOTICE] Pulsar tests disabled

Given these instabilities we might also want to consider excluding it from the 1.15 release, because it is clearly not in a reasonable stable state before the feature freeze. On 18/02/2022 08:58, Chesnay Schepler wrote: FYI: I just disabled all Pulsar tests on master in

[NOTICE] Pulsar tests disabled

FYI: I just disabled all Pulsar tests on master in 296c3be7576940d6bd76f4d065a0b70bceb06991. They are currently the main source of test instabilities, and I don't see any real efforts or progress on those being addressed.

[jira] [Created] (FLINK-26230) [JUnit5 Migration] Module: flink-metrics-core

Chesnay Schepler created FLINK-26230: Summary: [JUnit5 Migration] Module: flink-metrics-core Key: FLINK-26230 URL: https://issues.apache.org/jira/browse/FLINK-26230 Project: Flink Issue

[jira] [Created] (FLINK-26229) [JUnit5 Migration] Module: flink-metrics-datadog

Chesnay Schepler created FLINK-26229: Summary: [JUnit5 Migration] Module: flink-metrics-datadog Key: FLINK-26229 URL: https://issues.apache.org/jira/browse/FLINK-26229 Project: Flink

[jira] [Created] (FLINK-26228) [JUnit5 Migration] Module: flink-metrics-dropwizard

Chesnay Schepler created FLINK-26228: Summary: [JUnit5 Migration] Module: flink-metrics-dropwizard Key: FLINK-26228 URL: https://issues.apache.org/jira/browse/FLINK-26228 Project: Flink

[jira] [Created] (FLINK-26227) [JUnit5 Migration] Module: flink-metrics-graphite

Chesnay Schepler created FLINK-26227: Summary: [JUnit5 Migration] Module: flink-metrics-graphite Key: FLINK-26227 URL: https://issues.apache.org/jira/browse/FLINK-26227 Project: Flink

[jira] [Created] (FLINK-26226) [JUnit5 Migration] Module: flink-metrics-influxdb

Chesnay Schepler created FLINK-26226: Summary: [JUnit5 Migration] Module: flink-metrics-influxdb Key: FLINK-26226 URL: https://issues.apache.org/jira/browse/FLINK-26226 Project: Flink

[jira] [Created] (FLINK-26225) [JUnit5 Migration] Module: flink-metrics-jmx

Chesnay Schepler created FLINK-26225: Summary: [JUnit5 Migration] Module: flink-metrics-jmx Key: FLINK-26225 URL: https://issues.apache.org/jira/browse/FLINK-26225 Project: Flink Issue

Re: [DISCUSS] Disable "Automated Checks / Review Progress" GitHub integration

+1 to remove it. On 17/02/2022 13:31, Konstantin Knauf wrote: +1 On Thu, Feb 17, 2022 at 1:11 PM Robert Metzger wrote: Hi all, Some time ago, we added this "Automated Checks / Review Progress" [1] bot to the Flink PRs. I'm not aware of anybody using it, and I'm also not sure if it still wor

[jira] [Created] (FLINK-26221) [JUnit5 Migration] Module: flink-metrics-prometheus

Chesnay Schepler created FLINK-26221: Summary: [JUnit5 Migration] Module: flink-metrics-prometheus Key: FLINK-26221 URL: https://issues.apache.org/jira/browse/FLINK-26221 Project: Flink

[jira] [Created] (FLINK-26219) [JUnit5 Migration] Module: flink-metrics-slf4j

Chesnay Schepler created FLINK-26219: Summary: [JUnit5 Migration] Module: flink-metrics-slf4j Key: FLINK-26219 URL: https://issues.apache.org/jira/browse/FLINK-26219 Project: Flink Issue

[jira] [Created] (FLINK-26218) Enable JUnit 5 Automatic Extension Detection

Chesnay Schepler created FLINK-26218: Summary: Enable JUnit 5 Automatic Extension Detection Key: FLINK-26218 URL: https://issues.apache.org/jira/browse/FLINK-26218 Project: Flink Issue

[jira] [Created] (FLINK-26215) [JUnit5 Migration] Module: flink-metrics-statsd

Chesnay Schepler created FLINK-26215: Summary: [JUnit5 Migration] Module: flink-metrics-statsd Key: FLINK-26215 URL: https://issues.apache.org/jira/browse/FLINK-26215 Project: Flink

[jira] [Created] (FLINK-26191) Incorrect license in Elasticsearch 7 connector

Chesnay Schepler created FLINK-26191: Summary: Incorrect license in Elasticsearch 7 connector Key: FLINK-26191 URL: https://issues.apache.org/jira/browse/FLINK-26191 Project: Flink Issue

[jira] [Created] (FLINK-26189) Remove bundling of grizzled-slf4j from rpc-akka

Chesnay Schepler created FLINK-26189: Summary: Remove bundling of grizzled-slf4j from rpc-akka Key: FLINK-26189 URL: https://issues.apache.org/jira/browse/FLINK-26189 Project: Flink

[jira] [Created] (FLINK-26187) Chinese docs override english aliases

Chesnay Schepler created FLINK-26187: Summary: Chinese docs override english aliases Key: FLINK-26187 URL: https://issues.apache.org/jira/browse/FLINK-26187 Project: Flink Issue Type

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

play/FLINK/FLIP-196%3A+Source+API+stability+guarantees On Fri, Feb 11, 2022 at 12:26 AM Chesnay Schepler wrote: The conclusion in FLIP-196 was that we only provide source compatibility for Public(Evolving) APIs, which means that _everything_ must be compiled against the Flink version you ar

[jira] [Created] (FLINK-26095) MetricQueryService actor system binds to different address than main actor system

Chesnay Schepler created FLINK-26095: Summary: MetricQueryService actor system binds to different address than main actor system Key: FLINK-26095 URL: https://issues.apache.org/jira/browse/FLINK-26095

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

The conclusion in FLIP-196 was that we only provide source compatibility for Public(Evolving) APIs, which means that _everything_ must be compiled against the Flink version you are using it with. D

Re: [DISCUSS] Drop Jepsen tests

this by nuking half the cluster, crashing HDFS/ZK, and restarting everything. On 09/02/2022 17:39, Chesnay Schepler wrote: The jepsen tests cover 3 cases: a) JM/TM crashes b) HDFS namenode crash (aka, can't checkpoint because HDFS is down) c) network partitions a) can (and probably is) reaso

Re: [DISCUSS] Drop Jepsen tests

those risks? On Wed, Feb 9, 2022 at 12:40 PM Chesnay Schepler wrote: For a few years by now we had a set of Jepsen tests that verify the correctness of Flinks coordination layer in the case of process crashes. In the past it has indeed found issues and thus provided value to the project, and in ge

[jira] [Created] (FLINK-26059) ResourceProfile#ANY can cause overflow exceptions

Chesnay Schepler created FLINK-26059: Summary: ResourceProfile#ANY can cause overflow exceptions Key: FLINK-26059 URL: https://issues.apache.org/jira/browse/FLINK-26059 Project: Flink

[DISCUSS] Drop Jepsen tests

For a few years by now we had a set of Jepsen tests that verify the correctness of Flinks coordination layer in the case of process crashes. In the past it has indeed found issues and thus provided value to the project, and in general the core idea of it (and Jepsen for that matter) is very soun

[jira] [Created] (FLINK-26035) Rework loader-bundle into separate module

Chesnay Schepler created FLINK-26035: Summary: Rework loader-bundle into separate module Key: FLINK-26035 URL: https://issues.apache.org/jira/browse/FLINK-26035 Project: Flink Issue Type

Re: [DISCUSS] Checkpointing (partially) failing jobs

Could someone expand on these operational issues you're facing when achieving this via separate jobs? I feel like we're skipping a step, arguing about solutions without even having discussed the underlying problem. On 08/02/2022 11:25, Gen Luo wrote: Hi, @Yuan Do you mean that there should

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

+1 (binding) - signatures OK - checksums OK - tag OK - all artifacts accounted for - PR looks good On 05/02/2022 21:06, Konstantin Knauf wrote: Hi everyone, Please review and vote on the release candidate #1 for the version 1.13.6, as follows: [ ] +1, Approve the release [ ] -1, Do not approve

[jira] [Created] (FLINK-25979) Suspicious Classloading error during close of KafkaEnumerator

Chesnay Schepler created FLINK-25979: Summary: Suspicious Classloading error during close of KafkaEnumerator Key: FLINK-25979 URL: https://issues.apache.org/jira/browse/FLINK-25979 Project: Flink

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

+1 (binding) On 21/01/2022 15:57, Gabor Somogyi wrote: Hi devs, I would like to start the vote for FLIP-211 [1], which was discussed and reached a consensus in the discussion thread [2]. The vote will be open for at least 72h, unless there is an objection or not enough votes. BR, G [1] https

Re: [VOTE] Deprecate NiFi connector

+1 On 31/01/2022 11:46, Martijn Visser wrote: Hi everyone, I would like to open up a vote to deprecate NiFi in Flink 1.15 and remove it in the next version. I've previously mentioned that we were looking for maintainers for NiFi, but so far none have come forward [1]. The vote will last for at

[jira] [Created] (FLINK-25957) Cache cassandra/pulsar images

Chesnay Schepler created FLINK-25957: Summary: Cache cassandra/pulsar images Key: FLINK-25957 URL: https://issues.apache.org/jira/browse/FLINK-25957 Project: Flink Issue Type: Technical

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

ht be a decision that can affect large scale production runs. Cheers, Gyula On Thu, Feb 3, 2022 at 7:32 PM Chesnay Schepler wrote: First of, at no point have we questioned the use-case and importance of this feature, and the fact that David, Till and me spent time looking at the FLIP

[jira] [Created] (FLINK-25956) KryoSerializer is noisy in scala-free Flink

Chesnay Schepler created FLINK-25956: Summary: KryoSerializer is noisy in scala-free Flink Key: FLINK-25956 URL: https://issues.apache.org/jira/browse/FLINK-25956 Project: Flink Issue

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

ask doesn't mean 1 request. The following type of kerberos auth types has been seen by me which can run at the same time: HDFS, Hbase, Hive, Kafka, all DBs (oracle, mariaDB, etc...) Additionally one task is not necessarily opens 1 connection. All in all I don't have steps to reproduc

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

its own? I am a bit worried that we are making Flink responsible for something that it is not really designed to do so. Cheers, Till On Thu, Feb 3, 2022 at 2:54 PM Chesnay Schepler wrote: Here's an example for the TM to run workloads without being connected to the RM, while potentia

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

er we face a real issue or the design is not leaking. On Thu, Feb 3, 2022 at 2:12 PM Chesnay Schepler wrote: > Just to learn something new. I think local recovery is clear to me which is not touching external systems like Kafka or so (correct me if I'm wrong). Is it po

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

code just starts to run blindly w/o JM coordination and connects to external systems to do data processing? On Thu, Feb 3, 2022 at 1:09 PM Chesnay Schepler wrote: 1) The manager certainly shouldn't check for specific implementations. The problem with classpath-based checks i

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

i wrote: Thanks for the quick response! Appreciate your invested time... G On Thu, Feb 3, 2022 at 11:12 AM Chesnay Schepler wrote: Thanks for answering the questions! 1) Does the HBase provider require HBase to be on the classpath? To be instantiated no, to obtain a token yes.

[jira] [Created] (FLINK-25947) License checker doesn't flink-table-planner

Chesnay Schepler created FLINK-25947: Summary: License checker doesn't flink-table-planner Key: FLINK-25947 URL: https://issues.apache.org/jira/browse/FLINK-25947 Project: Flink

[jira] [Created] (FLINK-25946) table-planner-loader jar NOTICE should list Scala

Chesnay Schepler created FLINK-25946: Summary: table-planner-loader jar NOTICE should list Scala Key: FLINK-25946 URL: https://issues.apache.org/jira/browse/FLINK-25946 Project: Flink

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

se. 10) I'm not sure myself. It could be something as trivial as creating some temporary directory in HDFS I suppose. On 03/02/2022 10:23, Gabor Somogyi wrote: Please see my answers inline. Hope provided satisfying answers to all questions. G On Thu, Feb 3, 2022 at 9:17 AM Chesnay Scheple

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

I have a few question that I'd appreciate if you could answer them. 1. How does the Provider know whether it is required or not? 2. How does the configuration of Providers work (how do they get access to a configuration)? 3. How does a user select providers? (Is it purely based on the provi

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