xuyang created FLINK-28969: ------------------------------ Summary: Release Testing: Verify FLIP-229 Join Hints for Flink SQL Batch Key: FLINK-28969 URL: https://issues.apache.org/jira/browse/FLINK-28969 Project: Flink Issue Type: Sub-task Components: Table SQL / Planner Affects Versions: 1.16.0 Reporter: xuyang
Join hints for Flink SQL batch is ready. Users can define the join hint they want to suggest the optimizer to use the customized join strategy. I think we should verify: # Follow the doc to write a SQL with join hints and observe the final join strategy in the plan. The doc is preparing and you can refer this [pr|https://github.com/apache/flink/pull/20513] temporarily. # Test some unexpected behavior when writing the join hint (including but not limited to the conflicts on [doc|https://docs.google.com/document/d/19PL77ZggPIhz7FMZv2Yx7w_cnYyvmTc-mxUpJYv_934/edit#heading=h.uia01v8e78ov] or the [pr|https://github.com/apache/flink/pull/20513]), and observe whether the join strategy in the plan is expected. For example: ** Multi same or different args in one join hint ** Multi same or different join hints ** Multi query blocks and join hints ** Unknown table names in join hints ** Complex SQL like union, minus, correlate, filter and etc -- This message was sent by Atlassian Jira (v8.20.10#820010)