[jira] [Commented] (KYLIN-5267) force limit to protect the service when SQL has no limit

["liyang (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KYLIN-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612009#comment-17612009 ] 

liyang commented on KYLIN-5267:
-------------------------------

As a result of KYLIN-2649, a config parameter called "kylin.query.force-limit" is already added.

Does that help your use case?

 

Also "kylin.query.scan-threshold" is another config parameter that is often used to limit big queries going too wild.

> force limit to protect the service when SQL has no limit
> --------------------------------------------------------
>
>                 Key: KYLIN-5267
>                 URL: https://issues.apache.org/jira/browse/KYLIN-5267
>             Project: Kylin
>          Issue Type: Improvement
>          Components: Query Engine
>    Affects Versions: v4.0.1
>            Reporter: Liu Zhao
>            Priority: Minor
>
> 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？



--
This message was sent by Atlassian Jira
(v8.20.10#820010)