Skip to content

[FLINK-37921][table] Replace TableKeyedAsyncWaitOperator with new operator under new async framework #26698

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

xishuaidelin
Copy link
Contributor

@xishuaidelin xishuaidelin commented Jun 18, 2025

What is the purpose of the change

Current key ordered lookup join implementation borrows most concepts of FLIP-425 like Epoch, AsynExecutionController, etc. This leads to much code duplication. This pr aims to integrate current implementation into async processing framework which introduced in FLINK-37930. This pr is to replace the implementation in FLINK-37877 while the TableAsyncExecutionController would be removed later.

Brief change log

  • *AsyncKeyOrderedLookupOperator is introduced for async key ordered processing for lookup join. *

Verifying this change

This change added tests and can be verified as follows:

AsyncKeyOrderedLookupOperatorTest is added to verify this change

Does this pull request potentially affect one of the following parts:

  • Dependencies (does it add or upgrade a dependency): ( no )
  • The public API, i.e., is any changed class annotated with @Public(Evolving): ( no )
  • The serializers: ( no )
  • The runtime per-record code paths (performance sensitive): ( no )
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: ( no )
  • The S3 file system connector: ( no )

Documentation

  • Does this pull request introduce a new feature? (no)

@flinkbot
Copy link
Collaborator

flinkbot commented Jun 18, 2025

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run azure re-run the last Azure build

@xishuaidelin xishuaidelin force-pushed the refactor-pr branch 3 times, most recently from cbb45a6 to abaedef Compare June 20, 2025 01:57
@lincoln-lil
Copy link
Contributor

@xishuaidelin We need to split non table related changes into separate commit.

return resultHandler;
}

public void waitAllInFlightInputsFinished() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe asyncExecutionController.drainInflightRecords(0); is enough. I'd suggest not using waitUntil since it mainly used for waiting specified requests.

// which would trigger dispose the context in AsyncExecutionController
// This part is executed in the AsyncExecutor
() -> {
KeyedResultHandler handler = invoke(element);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahhh..... I don't think this is the best practice.

I'd suggest the invoke produce a AsyncFuture, by wrapping one and providing to asyncFunction. And do thenXxxx on the future here to chain the following action. The AEC will track all the chaining operation and keep it run in main thread. We'd better not do something like KeyedResultHandler.processInMailbox

@xishuaidelin xishuaidelin marked this pull request as draft June 25, 2025 02:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants