Repository navigation
Conversation
… schema operations Reuse lazy transient clients per metadata applier and release them on close. Stop schema workers before releasing metadata resources, deferring cleanup on timeout. Cover client ownership and coordinator shutdown with lifecycle regressions. Generated-by: OpenAI Codex
Contributor
|
still need apache/fluss#4200 |
loserwang1024
self-requested a review
October 10, 2026 03:30
Merge upstream/master and retain its explicit bucket-key validation alongside metadata client reuse and lifecycle cleanup. Generated-by: OpenAI Codex
…data conflicts Merge upstream/master while retaining metadata client reuse and lifecycle cleanup. Preserve upstream ADD COLUMN replay handling and schema table options. Generated-by: OpenAI Codex
Contributor
|
@fxbing ,apache/fluss#4200 is merged, pushing forward it now. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the purpose of this pull request?
Fluss schema operations create and close a connection for each lookup or DDL. Waiting for the Netty event loop to shut down adds repeated delays to multi-table initialization. This PR reuses the metadata clients for the applier lifecycle.
JIRA: https://issues.apache.org/jira/browse/FLINK-40966
Brief change log
Verifying this change
-Pflink2).Focused command (Java 11):
mvn -o -pl flink-cdc-connect/flink-cdc-pipeline-connectors/flink-cdc-pipeline-connector-fluss -am \ -Dtest=FlussMetadataApplierTest,FlussMetadataApplierLifecycleITCase,FlussEventSerializationSchemaTest,FlussSinkITCase#testWrongTableOptions,SchemaCoordinatorTest \ -Dsurefire.failIfNoSpecifiedTests=false clean testFor Java 17 / Flink 2.2, use
-Pflink2, addExistingTableSchemaExpanderTestto the test selection, and runpackage -DskipITsafter cleaning. Packaging is required by the profile's reactor JAR-copy step. The selected lifecycle ITCase is explicitly executed by Surefire.Documentation
Was generative AI tooling used to co-author this PR?
Generated-by: OpenAI Codex