Re: Configuration not propagating unless explicitly initializing FileSystem for Azure File System

Hi, Yuval The issue you're encountering arises because Flink's FileSystem is designed to operate with cluster-level configuration. And this configuration is sourced from the flink-conf.yaml file. Consequently, when the FileSystem is initialized, it isn't able to access the configuration objects

Configuration not propagating unless explicitly initializing FileSystem for Azure File System

Flink: 1.17.1 Hi, I've encountered a weird issue when passing a configuration object to StreamExecutionEnvironment.getExecutionEnvironment does not propagate to the hadoop file system being initialized when running Flink locally in an IDE. I am passing credentials in order to connect to Azure

RE: Feature flag functionality on flink

Hi, If it is for simplicity, you can also try writing the flag into an external system, such as Redis、Zookeeper or MySQL, and query the flag from the external system when perform data processing. However, Broadcast State is still the mode that I recommend. Perhaps we only need to encapsulate

Re: 退订

Please send email to user-unsubscr...@flink.apache.org if you want to unsubscribe the mail from u...@flink.apache.org, and you can refer [1][2] for more details. 请发送任意内容的邮件到 user-unsubscr...@flink.apache.org 地址来取消订阅来自 u...@flink.apache.org 邮件组的邮件，你可以参考[1][2] 管理你的邮件订阅。 Best, Hang [1]

Re: 退订

Please send email to user-unsubscr...@flink.apache.org if you want to unsubscribe the mail from user@flink.apache.org, and you can refer [1][2] for more details. 请发送任意内容的邮件到 user-unsubscr...@flink.apache.org 地址来取消订阅来自 user@flink.apache.org 邮件组的邮件，你可以参考[1][2] 管理你的邮件订阅。 Best, Hang [1]

Re: Flink KafkaProducer Failed Transaction Stalling the whole flow

Hi, Dominik. >From the code, your sink has received an InvalidTxnStateException in KafkaCommittter[1]. And kafka connector treats it as a known exception to invoke `signalFailedWithKnownReason`. `signalFailedWithKnownReason` will not throw an exception. It let the committer to decide fail or

RE: flink1.15-flink1.18官方提供写入Elasticsearch的接口报序列化异常

Hi, createIndexRequest是否不是静态的，scala的话可以在object中声明该方法。 Lambda中访问非静态方法，并且外部类不是可序列化的，可能会导致lambda无法被序列化。 Best, Jiabao On 2023/12/12 07:53:53 李世钰 wrote: > val result: ElasticsearchSink[String] = new Elasticsearch7SinkBuilder[String] > // This instructs the sink to emit after every element,

退订

退订

退订

退订

Re: Flink KafkaProducer Failed Transaction Stalling the whole flow

Hi Dominik, Sounds like it could be this? https://issues.apache.org/jira/browse/FLINK-28060 It doesn't mention transactions but I'd guess it could be the same mechanism. Regards, Alexis. On Mon, 18 Dec 2023, 07:51 Dominik Wosiński, wrote: > Hey, > I've got a question regarding the

Flink KafkaProducer Failed Transaction Stalling the whole flow

Hey, I've got a question regarding the transaction failures in EXACTLY_ONCE flow with Flink 1.15.3 with Confluent Cloud Kafka. The case is that there is a FlinkKafkaProducer in EXACTLY_ONCE setup with default *transaction.timeout.ms *of 15min. During the

Re: Flink 1.18.0 Checkpoints on cancelled jobs

Hi Ethan! Thanks for raising the issue, this is indeed a bug - for the previous code path, it falls back to "execution graph store" for completed jobs. I've raise a JIRA here - https://issues.apache.org/jira/browse/FLINK-33872 I've also managed to RC and fix it in the associated PR -

RE: Java 8 support in Flink 1.18

Thanks a lot for quick response. From: Junrui Lee Sent: 18 December 2023 15:57 To: Praveen Chandna via user Cc: Praveen Chandna Subject: Re: Java 8 support in Flink 1.18 Hello, Praveen According to the Flink release-2.0 wiki page

Re: Java 8 support in Flink 1.18

Hello, Praveen According to the Flink release-2.0 wiki page ( https://cwiki.apache.org/confluence/display/FLINK/2.0+Release), there is a must-have task to remove Java 8 support. Therefore, Flink plans to remove support for Java 8 in the upcoming release-2.0. Best regards, Junrui Praveen

Re: Java 8 support in Flink 1.18

Hello, Praveen Java 8 is still supported in the latest Flink 1.18 release despite its deprecation. You can continue using Java 8 for now. However, deprecation serves as a warning that in future releases, Java 8 may no longer be supported. It is recommended that you begin planning your migration

Java 8 support in Flink 1.18

Hello Team As per the Flink 1.15 release notes, Java 8 support has been deprecated. Will there be any impact ? Can I continue to use Java 8 or is there any risk ? Thanks !! // Regards Praveen Chandna