[
https://issues.apache.org/jira/browse/KYLIN-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17832363#comment-17832363
]
pengfei.zhan commented on KYLIN-5771:
-------------------------------------
How to reproduce this problem? Add a large number of Segments to a model, for
example, 5000; execute the query SQL and SQL with the filter condition of time
partition column; at the same time, set the query timeout about 10 seconds, you
can observe that the log execution prunning setgments process will not be
interrupted, and will continuously output the following log:
{code:java}
logger.info("Find candidates by table {} and project={} : {}",
olapContext.firstTableScan.getTableName(),
olapContext.olapSchema.getProjectName(), candidate);
log.info("Scan segment.size: {} after segment pruning",
selectedSegments.size()); {code}
> Query cannot be interrupted during Segment pruning phase
> --------------------------------------------------------
>
> Key: KYLIN-5771
> URL: https://issues.apache.org/jira/browse/KYLIN-5771
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 5.0-beta
> Reporter: pengfei.zhan
> Assignee: pengfei.zhan
> Priority: Major
> Fix For: 5.0.0
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
