lincoln-lil opened a new pull request, #20482:
URL: https://github.com/apache/flink/pull/20482

   ## What is the purpose of the change
   Introduces LOOKUP join hint to support delayed retry for lookup join (table 
alias unsupported in hint)
   This is the main part of FLINK-28779 to implement FLIP-234: Support 
Retryable Lookup Join To Solve Delayed Updates Issue In External Systems.
   The join hint based on [FLINK-28682][table-planner] support join hint in 
batch rules #20359, and adds a new hint 'LOOKUP' described in FLIP-234.
   
   ## Brief change log
   * Add new hint LOOKUP
   * Add related option class and validation
   * Add related tests for new classes
   * Adapt to async operator with retry and also adds a new 
RetryableLookupFunctionDelegator to wrap user's sync lookup func to support 
retry
   
   ## Verifying this change
   * LookupJoinHintSpecSerdeTest
   * LookupJoinHintSpecTest
   * LookupJoinJsonPlanTest
   * LookupJoinTest
   * RetryableLookupFunctionDelegatorTest
   * more ITCases will be updated in [Add it cases with lookup hint using new 
lookup function api for lookup 
join](https://issues.apache.org/jira/browse/FLINK-28849)
   
   ## 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? (yes)
     - If yes, how is the feature documented? (docs)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to