[FLINK-37921][table] Replace TableKeyedAsyncWaitOperator with new operator under new async framework
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)
CI report:
- a02df2f879d038dd5aa4782caeea2eb8cf20a0d2 Azure: FAILURE
Bot commands
The @flinkbot bot supports the following commands:@flinkbot run azurere-run the last Azure build
@xishuaidelin We need to split non table related changes into separate commit.
This PR is being marked as stale since it has not had any activity in the last 90 days. If you would like to keep this PR alive, please leave a comment asking for a review. If the PR has merge conflicts, update it with the latest from the base branch.
If you are having difficulty finding a reviewer, please reach out to the community, contact details can be found here: https://flink.apache.org/what-is-flink/community/
If this PR is no longer valid or desired, please feel free to close it. If no activity occurs in the next 30 days, it will be automatically closed.
This PR has been closed since it has not had any activity in 120 days. If you feel like this was a mistake, or you would like to continue working on it, please feel free to re-open the PR and ask for a review.