Re: [DISCUSS] FLIP-447: Upgrade FRocksDB from 6.20.3 to 8.10.0

Thank you for driving this effort +1 Cheers Gyula On Wed, 24 Apr 2024 at 06:25, Yuan Mei wrote: > Hey Yue, > > Thanks for all the great efforts significantly improving rescaling and > upgrading rocksdb. > > +1 for this. > > Best > Yuan > > On Wed, Apr 24, 2024 at 10:46 AM Zakelly Lan >

Re: [DISCUSS] FLIP-447: Upgrade FRocksDB from 6.20.3 to 8.10.0

Hey Yue, Thanks for all the great efforts significantly improving rescaling and upgrading rocksdb. +1 for this. Best Yuan On Wed, Apr 24, 2024 at 10:46 AM Zakelly Lan wrote: > Hi Yue, > > Thanks for this proposal! > > Given the great improvement we could have, the slight regression in write

[jira] [Created] (FLINK-35220) the error of mysql cdc

xiaotouming created FLINK-35220: --- Summary: the error of mysql cdc Key: FLINK-35220 URL: https://issues.apache.org/jira/browse/FLINK-35220 Project: Flink Issue Type: Bug Components:

Re: [DISCUSS] FLIP-447: Upgrade FRocksDB from 6.20.3 to 8.10.0

Hi Yue, Thanks for this proposal! Given the great improvement we could have, the slight regression in write performance is a worthwhile trade-off, particularly as the mem-table operations contribute only a minor part to the overall overhead. So +1 for this. Best, Zakelly On Tue, Apr 23, 2024

[jira] [Created] (FLINK-35219) [Flink SQL]Support deserialize json string into Map

zhihao zhang created FLINK-35219: Summary: [Flink SQL]Support deserialize json string into Map Key: FLINK-35219 URL: https://issues.apache.org/jira/browse/FLINK-35219 Project: Flink Issue

Re: [ DISCUSS ] FLIP-XXX : [Plugin] Enhancing Flink Failure Management in Kubernetes with Dynamic Termination Log Integration

>From a procedural point of view, we shouldn't make FLIPs sub-tasks for existing FLIPs that have been voted/are released. That will only cause confusion down the line. A new FLIP should take existing functionality (like FLIP-304) into account, and propose how to improve on what that original FLIP

Re: [DISCUSS][QUESTION] Drop jdk 8 support for Flink connector Opensearch

thanks for your response, Danny yeah, I think we could have 2 releases: one for v1 (jdk8) and one for v2 (jdk11) I guess we could even have same version for both since anyway artifact names are different On Thu, Apr 18, 2024 at 4:01 PM Danny Cranmer wrote: > Hey Sergey, > > Given the

[jira] [Created] (FLINK-35218) Duplicated values caused by expired state TTL

garcia created FLINK-35218: -- Summary: Duplicated values caused by expired state TTL Key: FLINK-35218 URL: https://issues.apache.org/jira/browse/FLINK-35218 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-35217) Missing fsync in FileSystemCheckpointStorage

Marc Aurel Fritz created FLINK-35217: Summary: Missing fsync in FileSystemCheckpointStorage Key: FLINK-35217 URL: https://issues.apache.org/jira/browse/FLINK-35217 Project: Flink Issue

[jira] [Created] (FLINK-35216) Support for RETURNING clause of JSON_QUERY

Dawid Wysakowicz created FLINK-35216: Summary: Support for RETURNING clause of JSON_QUERY Key: FLINK-35216 URL: https://issues.apache.org/jira/browse/FLINK-35216 Project: Flink Issue

Re: [SUMMARY] Flink 1.20 Release Sync 04/23/2024

Hi Muhammet, Thanks for your reminder. Each meeting will start from 10am (UTC+2) and 4pm (UTC+8). And the release sync happens bi-weekly at first, and will be adjusted to weekly as we approach the feature freeze date. Best, Rui On Tue, Apr 23, 2024 at 5:34 PM Muhammet Orazov wrote: > Hey

Re: [ DISCUSS ] FLIP-XXX : [Plugin] Enhancing Flink Failure Management in Kubernetes with Dynamic Termination Log Integration

Hi Gyula and Ahmed, I totally agree that there is an interlap in the final goal that both the FLIPs are achieving here and infact FLIP-304 is more comprehensive for job failures. But as a proposal to move forward can we make Swathi's FLIP/JIRA as a sub task for FLIP-304 and continue with the PR

Re: [SUMMARY] Flink 1.20 Release Sync 04/23/2024

Hey Rui, Thanks for the summary! Could you please write what time are you meeting on 5th May? Thanks and best, Muhammet On 2024-04-23 09:13, Rui Fan wrote: Dear devs, Today is the second meeting for Flink 1.20 release cycle. I'd like to share the information synced in the meeting. -

Re: [SUMMARY] Flink 1.20 Release Sync 04/23/2024

Thanks Rui for the summary! Best regards, Weijie Rui Fan <1996fan...@gmail.com> 于2024年4月23日周二 17:13写道： > Dear devs, > > Today is the second meeting for > Flink 1.20 release cycle. I'd like to share > the information synced in the meeting. > > - Features: > There're 8 weeks until the feature

[SUMMARY] Flink 1.20 Release Sync 04/23/2024

Dear devs, Today is the second meeting for Flink 1.20 release cycle. I'd like to share the information synced in the meeting. - Features: There're 8 weeks until the feature freeze date, so far we've had 6 flips/features and the status looks good. It is encouraged to continuously updating

Re: [DISCUSS] FLIP-446: Kubernetes Operator State Snapshot CRD

Thank you all for the great discussion. > 2. I agree with you that "completed" is not very clear, but I would suggest the name "alreadyExists". WDYT? I'm fine with "alreadyExists" and for 3. also with "backoffLimit". > really like the idea of having something like Pod Conditions, but I think