[jira] [Created] (FLINK-26096) add isolationLevel for jdbc Connector Options

nyingping created FLINK-26096: - Summary: add isolationLevel for jdbc Connector Options Key: FLINK-26096 URL: https://issues.apache.org/jira/browse/FLINK-26096 Project: Flink Issue Type: Improveme

Re: Re: [DISCUSS] Future of Per-Job Mode

Hi David, Zeppelin and SQL CLI also support submitting long-running streaming SQL jobs. So the session cluster is not a fit mode. Best, Jark On Fri, 11 Feb 2022 at 22:42, David Morávek wrote: > Hi Jark, can you please elaborate about the current need of the per-job > mode for interactive clien

Re: Re: [DISCUSS] FLIP-213: TaskManager's Flame Graphs

Pyroscope[1] and Parca[2] are other options for less-intrusive profiling (& great fits for k8s) that move the burden from Flink & its UI to tools that are purpose-built for this use case. Perhaps we could investigate what it would take (if anything) to make Flink compatible with those? Best, Austi

Re: Re: [DISCUSS] Future of Per-Job Mode

Hi Jark, can you please elaborate about the current need of the per-job mode for interactive clients (eg. Zeppelin that you've mentioned)? Aren't these a natural fit for the session cluster? D. On Fri, Feb 11, 2022 at 3:25 PM Jark Wu wrote: > Hi Konstantin, > > I'm not very familiar with the im

Re: Re: [DISCUSS] Future of Per-Job Mode

Hi Konstantin, I'm not very familiar with the implementation of per-job mode and application mode. But is there any instruction for users abou how to migrate platforms/jobs to application mode? IIUC, the biggest difference between the two modes is where the main() method is executed. However, SQL

[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

[jira] [Created] (FLINK-26094) Graph library not producing output to file

Hariharan Gopalan created FLINK-26094: - Summary: Graph library not producing output to file Key: FLINK-26094 URL: https://issues.apache.org/jira/browse/FLINK-26094 Project: Flink Issue Ty

Re: [DISCUSS] Release Flink 1.14.4

+1 for a 1.14.4 release. The release-1.14 branch already includes 36 fixed issues, some of them quite severe. Cheers, Till On Fri, Feb 11, 2022 at 1:23 PM Martijn Visser wrote: > Hi Konstantin, > > Thanks for opening the discussion. I think FLINK-25732 does indeed warrant > a speedy Flink 1.14.

Re: Re: [DISCUSS] FLIP-213: TaskManager's Flame Graphs

Are you sure the UI is the bottleneck? The UI gets back a JSON representation of this data structure: https://github.com/apache/flink/blob/2e21321f9c9d9aada7e4ad8ca90d915c34f58015/flink-runtime/src/main/java/org/apache/flink/runtime/webmonitor/threadinfo/JobVertexFlameGraph.java All samples from

[jira] [Created] (FLINK-26093) SavepointFormatITCase fails with ChangelogStateBackend

Roman Khachatryan created FLINK-26093: - Summary: SavepointFormatITCase fails with ChangelogStateBackend Key: FLINK-26093 URL: https://issues.apache.org/jira/browse/FLINK-26093 Project: Flink

Re: [DISCUSS] Release Flink 1.14.4

Hi Konstantin, Thanks for opening the discussion. I think FLINK-25732 does indeed warrant a speedy Flink 1.14.4 release. I would indeed also like to include FLINK-26018. Best regards, Martijn Op vr 11 feb. 2022 om 10:29 schreef Konstantin Knauf > Hi everyone, > > what do you think about a tim

[jira] [Created] (FLINK-26092) JsonAggregationFunctionsITCase fails with NPE when using RocksDB

Roman Khachatryan created FLINK-26092: - Summary: JsonAggregationFunctionsITCase fails with NPE when using RocksDB Key: FLINK-26092 URL: https://issues.apache.org/jira/browse/FLINK-26092 Project: F

Re: Re: [DISCUSS] FLIP-213: TaskManager's Flame Graphs

There are already tools [1] that simplify this for the user. I honestly don't know, it feels like it can bring more problems that actual benefits as this heavily relies on the environment. It can easily break for some users, eg. because of the kernel settings; their architecture might not be suppo

[DISCUSS] Release Flink 1.14.4

Hi everyone, what do you think about a timely Flink 1.14.4 in order to release the fix for https://issues.apache.org/jira/browse/FLINK-25732. Currently, the landing page of Flink Web User Interface is not working when there are standby Jobmanagers. In addition, I propose to wait for https://issue

[jira] [Created] (FLINK-26091) SafetyNetCloseableRegistryTest.testNonBlockingClose failed on azure

Yun Gao created FLINK-26091: --- Summary: SafetyNetCloseableRegistryTest.testNonBlockingClose failed on azure Key: FLINK-26091 URL: https://issues.apache.org/jira/browse/FLINK-26091 Project: Flink Is

[jira] [Created] (FLINK-26090) Remove pre FLIP-84 methods

Francesco Guardiani created FLINK-26090: --- Summary: Remove pre FLIP-84 methods Key: FLINK-26090 URL: https://issues.apache.org/jira/browse/FLINK-26090 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-26089) Introduce TablePipeline

Francesco Guardiani created FLINK-26089: --- Summary: Introduce TablePipeline Key: FLINK-26089 URL: https://issues.apache.org/jira/browse/FLINK-26089 Project: Flink Issue Type: Sub-task

Re: Azure Pipelines are dealing with an incident, causing pipeline runs to fail

Thanks Martijn and everyone involved. > On 11.02.2022, at 09:02, Martijn Visser wrote: > > Hi all, > > The issue has been resolved now indeed. The cause was the following: > > - Azure had an outage [1] > - When that outage was resolved, all of Flink's free build agents were > gone. > - A tempo

[ANNOUNCE] Pushing the feature freeze by a couple of days

Dear Apache Flink Community, As we have been facing some CI instabilities due to some infrastructure issues in the last couple of days we might push the feature freeze for 1.15. by a couple of days. We will evaluate the situation on the go and will keep you up to date. Best, Joe

[jira] [Created] (FLINK-26088) Add Elasticsearch 8.0 support

Yuhao Bi created FLINK-26088: Summary: Add Elasticsearch 8.0 support Key: FLINK-26088 URL: https://issues.apache.org/jira/browse/FLINK-26088 Project: Flink Issue Type: Improvement Compo

[jira] [Created] (FLINK-26087) S3 filesystem tests never run in AzureCI

Matthias Pohl created FLINK-26087: - Summary: S3 filesystem tests never run in AzureCI Key: FLINK-26087 URL: https://issues.apache.org/jira/browse/FLINK-26087 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-26086) fixed some causing ambiguities including the 'shit' comment

nyingping created FLINK-26086: - Summary: fixed some causing ambiguities including the 'shit' comment Key: FLINK-26086 URL: https://issues.apache.org/jira/browse/FLINK-26086 Project: Flink Issue

[jira] [Created] (FLINK-26085) Statefun Support PbJson Type

xinchenyuan created FLINK-26085: --- Summary: Statefun Support PbJson Type Key: FLINK-26085 URL: https://issues.apache.org/jira/browse/FLINK-26085 Project: Flink Issue Type: New Feature

Re: [DISCUSS]Support the merge statement in FlinkSQL

Hi, Martijn Visser, thanks for your reply. Firstly, I am sorry for posting the discussion twice. I sent the message to the dev mail group from an unsub- scribed account, but the message was not shown for a while, and I guessed that the dev mail group would not post an email coming from an unsubscr

RE: Re: [DISCUSS] FLIP-213: TaskManager's Flame Graphs

Our flink application is on k8s.Yes, user can use the async-profiler directly, but it is not convenient for user, who should download the jars and need to know how to use it. And some users don’t know the tool.if we integrate it, user will benefit a lot. On 2022/01/26 18:56:17 David Morávek wro

RE: Re: [DISCUSS] FLIP-213: TaskManager's Flame Graphs

Our flink application is on k8s.Yes, user can use the async-profiler directly, but it is not convenient for user, who should download the jars and need to know how to use it. And some users don’t know the tool.if we integrate it, user will benefit a lot. On 2022/01/26 18:56:17 David Morávek wro

RE: Re: [DISCUSS] FLIP-213: TaskManager's Flame Graphs

Our flink application is on k8s.Yes, user can use the async-profiler directly, but it is not convenient for user, who should download the jars and need to know how to use it. And some users don’t know the tool.if we integrate it, user will benefit a lot. On 2022/01/26 18:56:17 David Morávek wro

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: Azure Pipelines are dealing with an incident, causing pipeline runs to fail

Thanks for following up on this, Martijn. On Fri, Feb 11, 2022 at 9:03 AM Martijn Visser wrote: > Hi all, > > The issue has been resolved now indeed. The cause was the following: > > - Azure had an outage [1] > - When that outage was resolved, all of Flink's free build agents were > gone. > - A

Re: Azure Pipelines are dealing with an incident, causing pipeline runs to fail

Hi all, The issue has been resolved now indeed. The cause was the following: - Azure had an outage [1] - When that outage was resolved, all of Flink's free build agents were gone. - A temporary switch was made to paid agents, while we reached out once more to Azure. However, those paid agents had