You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by lg...@apache.org on 2020/12/10 09:46:26 UTC
[incubator-dolphinscheduler] branch dev updated: [FIX-4190][DAO]
When the amount of json data is large,
the process list page display slowly. (#4201)
This is an automated email from the ASF dual-hosted git repository.
lgcareer pushed a commit to branch dev
in repository https://gitbox.apache.org/repos/asf/incubator-dolphinscheduler.git
The following commit(s) were added to refs/heads/dev by this push:
new 68541f2 [FIX-4190][DAO] When the amount of json data is large, the process list page display slowly. (#4201)
68541f2 is described below
commit 68541f281d0b0908f605ad49847d3e7acdd5a302
Author: bao liang <29...@users.noreply.github.com>
AuthorDate: Thu Dec 10 17:46:15 2020 +0800
[FIX-4190][DAO] When the amount of json data is large, the process list page display slowly. (#4201)
* fix 4190: When the amount of json data is large, process list page display slowly
* fix 4190: When the amount of json data is large, process list page display slowly
* fix 4190: When the amount of json data is large, process list page display slowly
Co-authored-by: baoliang <ba...@analysys.com.cn>
---
.../dao/mapper/ProcessInstanceMapper.xml | 17 ++++-------------
1 file changed, 4 insertions(+), 13 deletions(-)
diff --git a/dolphinscheduler-dao/src/main/resources/org/apache/dolphinscheduler/dao/mapper/ProcessInstanceMapper.xml b/dolphinscheduler-dao/src/main/resources/org/apache/dolphinscheduler/dao/mapper/ProcessInstanceMapper.xml
index d707c9c..f661635 100644
--- a/dolphinscheduler-dao/src/main/resources/org/apache/dolphinscheduler/dao/mapper/ProcessInstanceMapper.xml
+++ b/dolphinscheduler-dao/src/main/resources/org/apache/dolphinscheduler/dao/mapper/ProcessInstanceMapper.xml
@@ -88,21 +88,12 @@
</select>
<select id="queryProcessInstanceListPaging" resultType="org.apache.dolphinscheduler.dao.entity.ProcessInstance">
- select
- instance.id, instance.name, instance.process_definition_id, instance.state, instance.recovery,
- instance.start_time, instance.end_time, instance.run_times, instance.host,
- instance.command_type, instance.command_param, instance.task_depend_type, instance.max_try_times,
- instance.failure_strategy, instance.warning_type,
- instance.warning_group_id, instance.schedule_time, instance.command_start_time, instance.global_params,
- instance.process_instance_json, instance.flag,
- instance.update_time, instance.is_sub_process, instance.executor_id, instance.locations, instance.connects,
- instance.history_cmd, instance.dependence_schedule_times,
- instance.process_instance_priority, instance.worker_group, instance.timeout, instance.tenant_id,
- instance.var_pool
+ select instance.id, instance.process_definition_id, instance.command_type, instance.executor_id,
+ instance.name, instance.state, instance.schedule_time, instance.start_time, instance.end_time,
+ instance.run_times, instance.recovery, instance.host
from t_ds_process_instance instance
join t_ds_process_definition define ON instance.process_definition_id = define.id
- where 1=1
- and instance.is_sub_process=0
+ where instance.is_sub_process=0
and define.project_id = #{projectId}
<if test="processDefinitionId != 0">
and instance.process_definition_id = #{processDefinitionId}