[FLINK-28969] Release Testing: Verify FLIP-229 Join Hints for Flink SQL Batch

• Type: Sub-task
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.16.0
• Component/s: Table SQL / Planner
• Assignee: lincoln lee
• Reporter: xuyang
• Created: 15/Aug/22 09:52
• Updated: 02/Sep/22 13:52
• Resolved: 02/Sep/22 13:52

Description

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:

1. 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 temporarily.
2. Test some unexpected behavior when writing the join hint (including but not limited to the conflicts on doc or the  pr), 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

Issue Links

• is related to: FLINK-29120 Unexpected join hint propagation into view
• is related to: FLINK-29113 Join hint with invalid table name mixed with valid names will not raise an error
• is related to: FLINK-29119 Should clarify how join hints work with CTE