6.0
/
6.0.3
Upgrade the Update Task Management interface comprehensively.
6.0.4
Added prompts for update progress.
Added prompts that explain the reason for queuing.
6.0.8
Added update status No need to extract.
To extract data, you need to update data and ensure data availability. Update Task Management can be used for data management and monitoring:
It can be used to check the tasks that are currently being updated and the tasks that have been updated and to monitor the update content and error messages.
It allows you to view and manage different scheduled tasks for regular updates on one page.
Users with management permissions can also stop updating tasks.
Super admin can allow update tasks to cut in line.
FineBI allows for monitoring update status, stopping update tasks, and setting scheduled updates.
1. Click Public Data > Update Task Management.
2. Go to the first tab page Current Operation Condition. You can view all tasks currently being updated and can search for updating tasks through the search box in the upper right corner.
The super admin can view the overall information to know how many tasks are being updated, queuing, and cutting in line.
You can select task time by hour, minute, and second. You can also click Dynamic to select dynamic time.
3. Hover your cursor at Task Progress, and you can view the current update progress of the task.
If the task is being updated, it will prompt the update progress: Number of finished tables or relationships: x / Total: y.
If the task is waiting in line, it will prompt the reason why the task is waiting.
When a task is being updated, the newcomers need to wait in line. If you want the waiting task to be updated first, you can allow it to cut in line.
When the number of tasks cutting in line exceeds the limit, which is set to 5 by default, no more tasks can cut in line. You can modify the number limit by modifying the value of SystemOptimizationConfig.maxCutInLineCount.
Manual Stop
You can manually stop updating tasks one by one or in batches.
The table/association has been updated when you stop the update.
No error
Updated data
The table/association failed to update when you stop the update.
It prompts the reason for the update failure.
Last updated data
The update has not finished when you stop the update.
The task update was interrupted and no longer executed.
Intelligent Stop
During the update, you may encounter update exceptions due to an unstable network or environment, which results in update failures.
To address this problem, FineBI supports automatically interrupting updates. If a basis table fails to be updated, FineBI will automatically stop the update of that table without affecting the update of other tables in the same updating task.
The intelligent stop function is valid for base tables and is used for determining whether the base tables are updated abnormally.
The longest update time for a base table is 12 hours. If the update of a base table has not finished in 12 hours, the update will be forcibly terminated.
This interruption does not affect the next scheduled update task, and you can also perform single table updates in this period.
The intelligent stop will detect whether there is a false stop and will not mistakenly stop the update of normal base tables.
If you do not want FineBI to intelligently stop update tasks, modify the value of SystemOptimizationConfig.openUpdateIntelligentKill to false. For details, see FINE_CONF_ENTITY Visualization Configuration.
Click Details to view more update information.
You can end tasks and let tasks cut in line on this interface. Only super administrators can let tasks cut in line.
You can also check specific update information on this interface. For example, click Base Table to see the update status of a table, as shown in the following figure:
1) Click a faulty table to view the specific data.
2) Click a faulty table and the affected self-service datasets are listed below.
3) Click to view specific error information.
Click Historical Operation Condition to view the records of update tasks.
Click Details to view the error information of this task, as well as details on updates of base tables, self-service datasets, and other associated tasks.
Click Dataset Operation Record to check the detailed operation information of a single table, including Average Daily Updates, Average Update Duration, and Historical Failure Rate.
By checking these fields, you can troubleshoot datasets with high failure rates and make reasonable arrangements for frequently updated tables.
The following listed several cases where extracting data is unnecessary:
1. The self-service dataset is inactive and does not require an update. For more details, see Section 4 of Update of Self-service Dataset Single Table.
2. No changes have been made to the dataset, and no update is required.
On this interface, you can better manage scheduled update tasks.
By checking the chart at the top, you know the update schedule of each task. If too many tasks are set to update in the same period, you can make appropriate adjustments.
You can perform operations such as deleting, enabling/disabling, and editing the scheduled update tasks for which you have permission in the table at the bottom.
You can only see the scheduled update tasks for which you have data management permissions on this tab page. For details, see "Assigning Data Permission" in Public Data Management Permission.
Click the edit button, and you can modify the task name, start time, execution frequency, end time, and result notification.
For details about update information storage, see Platform Log.
If the SQL statement of the SQL dataset has been modified, incremental updates cannot work. A global update must be performed first.
The incremental update is not supported for Newly added DB tables and SQL datasets. A global update must be performed first.
滑鼠選中內容,快速回饋問題
滑鼠選中存在疑惑的內容,即可快速回饋問題,我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy