Re: [VOTE] FLIP-472: Aligning timeout logic in the AdaptiveScheduler's WaitingForResources and Executing states

+1 (binding) On Mon, Aug 5, 2024 at 11:05 AM David Morávek wrote: > +1 (binding) > > Best, > D. > > On Mon, Aug 5, 2024 at 9:24 AM yuanfeng hu wrote: > > > +1 (no-binding) > > > > Rui Fan <1996fan...@gmail.com> 于2024年8月5日周一 15:18写道： > > > > > +1(binding) > > > > > > Best, > > > Rui > > > > > >

[jira] [Created] (FLINK-36005) Specify to get part of the potgresql field

宇宙先生 created FLINK-36005: Summary: Specify to get part of the potgresql field Key: FLINK-36005 URL: https://issues.apache.org/jira/browse/FLINK-36005 Project: Flink Issue Type: Bug Compone

[jira] [Created] (FLINK-36004) Flink SQL returns wrong results for Paimon tables with complex schemas

Xingcan Cui created FLINK-36004: --- Summary: Flink SQL returns wrong results for Paimon tables with complex schemas Key: FLINK-36004 URL: https://issues.apache.org/jira/browse/FLINK-36004 Project: Flink

[jira] [Created] (FLINK-36003) Add CompiledPlan annotations to BatchExecExpand and BatchExecSortAggregate

Jim Hughes created FLINK-36003: -- Summary: Add CompiledPlan annotations to BatchExecExpand and BatchExecSortAggregate Key: FLINK-36003 URL: https://issues.apache.org/jira/browse/FLINK-36003 Project: Flink

[jira] [Created] (FLINK-36002) Add CompiledPlan annotations to BatchExecMatch

Jim Hughes created FLINK-36002: -- Summary: Add CompiledPlan annotations to BatchExecMatch Key: FLINK-36002 URL: https://issues.apache.org/jira/browse/FLINK-36002 Project: Flink Issue Type: Sub-ta

[Flink SQL Format] How to Process Metadata Columns in KafkaDynamicSink compatible EncodingFormat

Hi there, I'm looking to add some functionality to a custom Format that reads the `topic` metadata column in the context of serialization using the Flink SQL Kafka Connector. I'm c

[DISCUSS] FLIP-474: Store operator name and UID in state metadata

Hi Devs, I would like to start a discussion on FLIP-474: Store operator name and UID in state metadata[1]. In short users are interested in what kind of operators are inside a checkpoint data which can be enhanced from user experience perspective. The details can be found in FLIP-474[1]. Please

[jira] [Created] (FLINK-36001) Store operator name and UID in state metadata

Gabor Somogyi created FLINK-36001: - Summary: Store operator name and UID in state metadata Key: FLINK-36001 URL: https://issues.apache.org/jira/browse/FLINK-36001 Project: Flink Issue Type: I

[jira] [Created] (FLINK-36000) DynamicTableSink#Context's getTargetColumns should not return an array of zero length

lincoln lee created FLINK-36000: --- Summary: DynamicTableSink#Context's getTargetColumns should not return an array of zero length Key: FLINK-36000 URL: https://issues.apache.org/jira/browse/FLINK-36000 P

Re:Re: [DISCUSS] FLIP-473: Introduce New SQL Operators Based on Asynchronous State APIs

Hi, Zakelly. You’re right. This is another advantage of choosing the where two sets of operators share the same execution node. In this approach, users can utilize the compiled plan and adjust the config 'table.exec.async-state.enabled', providing them with the flexibility to switch between asy

[jira] [Created] (FLINK-35999) Remove log4j internal dependency

Siddharth R created FLINK-35999: --- Summary: Remove log4j internal dependency Key: FLINK-35999 URL: https://issues.apache.org/jira/browse/FLINK-35999 Project: Flink Issue Type: Improvement

[jira] [Created] (FLINK-35998) Duplicate common type search in type inference

Dylan He created FLINK-35998: Summary: Duplicate common type search in type inference Key: FLINK-35998 URL: https://issues.apache.org/jira/browse/FLINK-35998 Project: Flink Issue Type: Improvemen

[jira] [Created] (FLINK-35997) Incomplete Table API & Python API of built-in function LTRIM & RTRIM

Dylan He created FLINK-35997: Summary: Incomplete Table API & Python API of built-in function LTRIM & RTRIM Key: FLINK-35997 URL: https://issues.apache.org/jira/browse/FLINK-35997 Project: Flink

[jira] [Created] (FLINK-35996) Add end-to-end tests for MySQL to Elasticsearch pipeline

wuzexian created FLINK-35996: Summary: Add end-to-end tests for MySQL to Elasticsearch pipeline Key: FLINK-35996 URL: https://issues.apache.org/jira/browse/FLINK-35996 Project: Flink Issue Type:

[jira] [Created] (FLINK-35995) postgresql有字段限制了，全量期间需要select * 的权限

宇宙先生 created FLINK-35995: Summary: postgresql有字段限制了，全量期间需要select * 的权限 Key: FLINK-35995 URL: https://issues.apache.org/jira/browse/FLINK-35995 Project: Flink Issue Type: Bug Components: Fli

Re: [DISCUSS] FLIP-XXX Amazon SQS Source Connector

Hi Saurabh Thanks for addressing, I see the FLIP is in much better state. Could we specify where we queue messages for deletion, In my opinion the record emitter is a good place for that where we delete messages that are forwarded to the next operator. Other than that I don't have further comments.

[jira] [Created] (FLINK-35994) CDC pipeline use SavepointRestoreSettings in flink config flile as a fallback strategy.

Hongshun Wang created FLINK-35994: - Summary: CDC pipeline use SavepointRestoreSettings in flink config flile as a fallback strategy. Key: FLINK-35994 URL: https://issues.apache.org/jira/browse/FLINK-35994

[jira] [Created] (FLINK-35993) Add UNHEX function

Dylan He created FLINK-35993: Summary: Add UNHEX function Key: FLINK-35993 URL: https://issues.apache.org/jira/browse/FLINK-35993 Project: Flink Issue Type: Sub-task Components: Table S