[
https://issues.apache.org/jira/browse/KYLIN-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550264#comment-14550264
]
Luke Han commented on KYLIN-773:
--------------------------------
it is a known issue, since there is no secondary index on the job id, all
job will be scanned (separately not in batch).
So as the number of job increase, query time increases.
As a workaround, you may just delete all entries whose the rowkey started
with /execute/{job_id} and /execute_output/{job_id}
> performance is slow list jobs
> -----------------------------
>
> Key: KYLIN-773
> URL: https://issues.apache.org/jira/browse/KYLIN-773
> Project: Kylin
> Issue Type: Improvement
> Affects Versions: v0.7.1
> Reporter: Zhong,Jason
> Priority: Minor
> Fix For: v0.7.2, v0.8.1
>
>
> performance is slow when click "Jobs" tab on web to list jobs under project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
