Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
5.0-beta
-
None
Description
When SQL is in the planning stage and pruning segment optimization is performed, it may cause the query to cross the expected 300s and trigger the timeout cancellation logic due to the existence of a large number of segments, and a large number of filter expressions for simplification issues.