[KYLIN-5267] force limit to protect the service when SQL has no limit

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: v4.0.1
• Component/s: Query Engine
• Assignee: Unassigned
• Reporter: Liu Zhao
• Created: 16/Sep/22 14:33
• Updated: 02/Oct/22 02:15

Description

Kylin4 queries use Spark, and the result data will be sent to the driver (that is, query service). If the user's SQL returns a large data set, it may cause the query oom to be unavailable. To solve this problem, can we provide a means for users to enforce limit when SQL has no limit to protect services. I am here https://issues.apache.org/jira/browse/KYLIN-2649 You can see the idea above, but can reduce the limit on the SQL structure？