Re: RocksDB segfault on state restore

Hi! In our case, no schema evolution was triggered , only the TTL was set from the beginning as far as I remember. I will double check Gyula On Fri, 2 Jun 2023 at 06:12, Hangxiang Yu wrote: > Hi, Gyula. > It seems related to https://issues.apache.org/jira/browse/FLINK-23346. > We also saw

Re: RocksDB segfault on state restore

Hi, Gyula. It seems related to https://issues.apache.org/jira/browse/FLINK-23346. We also saw core dump while using list state after triggering state migration and ttl compaction filter. Have you triggered the schema evolution ? It seems a bug of the rocksdb list state together with ttl compaction

Re: Flink checkpoint timeout

HI, Ivan. Could you provide more information about it: 1. Which operator subtask is stuck ? or is it random ? 2. Could you share the stack or flame graph of the stuck subtask ? On Wed, May 31, 2023 at 12:45 PM Ethan T Yang wrote: > Hello all, > > We recently start to experience Checkpoint

Stateful functions roadmap

Hi, I came across Flink stateful functions and the project/idea excited me. But I noticed no code has been committed lately in this project and I couldn’t fins it’s roadmap. Can someone shed some light on state if this project? Thank you, Tarandeep

Re: apache-flink java question

Hi Chris, not yet and we are working on it[1]. best regards, Jing [1] https://issues.apache.org/jira/browse/FLINK-15736?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=17697544#comment-17697544 On Thu, Jun 1, 2023 at 11:40 PM Joseph, Chris S wrote: > Hi, > > > > Does

apache-flink java question

Hi, Does Apache flink table api work with java 17? Thanks, Chris Joseph

Re: [DISCUSS] Hive dialect shouldn't fall back to Flink's default dialect

+1, I think this can make the grammar more clear. Please remember to add a release note once the issue is finished. Best, Jark On Thu, 1 Jun 2023 at 11:28, yuxia wrote: > Hi, Jingsong. It's hard to provide an option regarding to the fact that we > also want to decouple Hive with flink planner.

AW: Using pre-registered schemas with avro-confluent-registry format is not possible

Hello Thias, thank you for your answer. We've tested registering an existing (byte equal) schema a second time, but unfortunately the schema registry does still deny the request. Your last suggestion sounds promising, but I think there are some edge cases with this approach that will still

AW: Using pre-registered schemas with avro-confluent-registry format is not possible

Hello Martijn, thanks for your answer. We've actually tried those properties. Unfortunately, they only apply to the standard KafkaAvroSerializer/-Deserializer classes by Confluent which are not used by Flink and therefore those properties have no effect here. Best regards, Jannik Von: