[jira] [Created] (FLINK-29134) fetch metrics may cause oom(ThreadPool task pile up)

Sitan Pang created FLINK-29134: -- Summary: fetch metrics may cause oom(ThreadPool task pile up) Key: FLINK-29134 URL: https://issues.apache.org/jira/browse/FLINK-29134 Project: Flink Issue Type:

[jira] [Created] (FLINK-29133) Adapt to new calcite rule configuration api

Sergey Nuyanzin created FLINK-29133: --- Summary: Adapt to new calcite rule configuration api Key: FLINK-29133 URL: https://issues.apache.org/jira/browse/FLINK-29133 Project: Flink Issue Type:

Re: Rescuing Queryable State from deprecation

Hi Ron, >From my understanding, the feature of queryable state is introduced to Flink >very early but lacks maintainers, in other words, this feature is currently a >toy instead of a production-ready tool. I have heard from users many times asking for this feature in the production environment

[jira] [Created] (FLINK-29132) SubtaskMetricStore causes memory leak.

Sitan Pang created FLINK-29132: -- Summary: SubtaskMetricStore causes memory leak. Key: FLINK-29132 URL: https://issues.apache.org/jira/browse/FLINK-29132 Project: Flink Issue Type: Bug

Flink Table Task question

Hello, We are calling flink table apis and are wondering is it possible to have a better naming of such operators to show on ui? E.g how do we renaming the following when the code is trying to make a sqlQuery() call SourceConversion(table=[default_catalog.default_database.mytable], fields=[data1,

Deadlock in Subtask in the FlinkKinesisConsumer

Hi I wanted to bring awareness to this Jira describing a deadlock state we've experienced for a single subtask in the FlinkKinesisConsumer. This occurs when we've reached the following conditions in the subtask: - reached the max lookahead so th

Re: [Discuss] KafkaSink making low level components PublicEvolving

Hi all, I know everyone is busy with preparing the 1.16 release. Just want to give this thread a gentle ping, please give your +1 if there are no concerns! Best, Mason On Thu, Aug 11, 2022 at 1:27 AM Mason Chen wrote: > I understand that the 1.16 feature freeze is in place so I propose for > t

Re: [DISCUSS] FLIP-246: Multi Cluster Kafka Source

Hi Max, Thanks for taking a look! > I'm wondering whether we can share some of the code of the existing > KafkaSource. > That is the intention--let me call it out more explicitly. Regarding your questions: 1. Indeed, the KafkaMetadataService has the describe stream method to get a particular

Re: [DISCUSS] FLIP-256 Support Job Dynamic Parameter With Flink Rest Api

 Ok, I think that’s fair - overriding user config expands the scope of the FLIP, should cover CLI and REST, and can be split into another discussion. Since the motivation is to make the REST API have parity with the CLI, happy to defer further work to a different thread. @Chesnay, to clarif

Re: [DISCUSS] FLIP-256 Support Job Dynamic Parameter With Flink Rest Api

+1 for Chesnay's suggestion and taking a simple pragmatic approach. Gyula On Mon, Aug 29, 2022 at 3:41 PM Chesnay Schepler wrote: > TBH I don't really get why we're discussion the prioritization of config > options vs. what users have set in their application in this thread. > > Why don't we ju

Re: [DISCUSS] FLIP-256 Support Job Dynamic Parameter With Flink Rest Api

TBH I don't really get why we're discussion the prioritization of config options vs. what users have set in their application in this thread. Why don't we just follow the same order that the CLI currently enforces? Same point regarding the external vs internal parameters. Ultimately this FLIP

[jira] [Created] (FLINK-29131) Kubernetes operator webhook can use hostPort

Dylan Meissner created FLINK-29131: -- Summary: Kubernetes operator webhook can use hostPort Key: FLINK-29131 URL: https://issues.apache.org/jira/browse/FLINK-29131 Project: Flink Issue Type:

[jira] [Created] (FLINK-29130) Correct the doc description of state.backend.local-recovery

Yun Tang created FLINK-29130: Summary: Correct the doc description of state.backend.local-recovery Key: FLINK-29130 URL: https://issues.apache.org/jira/browse/FLINK-29130 Project: Flink Issue Ty

[jira] [Created] (FLINK-29129) Try best to push down value filter

Jane Chan created FLINK-29129: - Summary: Try best to push down value filter Key: FLINK-29129 URL: https://issues.apache.org/jira/browse/FLINK-29129 Project: Flink Issue Type: Improvement

Re: Rescuing Queryable State from deprecation

Hi Ron, thanks you for sharing your use case and your initiative to save Queryable State. Queryable State was deprecated due to a lack of maintainers and thus the community did not have resources to improve and develop it further. The deprecation notice was added to signal this lack of attention t

[jira] [Created] (FLINK-29128) Uncatch IllegalStateException found when log split changes handling result in KafkaPartitionSplitReader

Leo zhang created FLINK-29128: - Summary: Uncatch IllegalStateException found when log split changes handling result in KafkaPartitionSplitReader Key: FLINK-29128 URL: https://issues.apache.org/jira/browse/FLINK-29128

Re: [DISCUSS] Support 'DYNAMIC MetadataColumn' in flink table

Hi Jack. Timo summed it up very well. In fact, my problem is that the current flink table metadata is fixed and cannot be compatible with the connector's changes in metadata columns. A metadata column that did not exist in the past, does exist at some point in the future, and vice versa. There is f

Re: [Discuss] Let's Session Cluster JobManager take a breather (FLIP-257: Flink JobManager Process Split)

Thanks, for the community fallback suggestions. In fact, the problem I want to solve is to reduce the current workload of the JobManager (as the title says, more focus is on how to reduce the workload of the JobManager). First my idea, I thought of reducing the resource overhead of the JobManager i