Method and device for processing task to be executed and electronic equipment

Abstract

The invention discloses a to-be-executed task processing method and device and electronic equipment. The method relates to the field of big data, and comprises the following steps: determining a target data set required for executing a target to-be-executed task, and determining data tables containing the target data set from a local database to obtain M target data tables; querying target task execution data of the data synchronization tasks of the M target data tables from a workflow record table in a local database to obtain M groups of target task execution data; identifying the M groups of target task execution data according to execution information required for executing the target to-be-executed task; and judging whether the target to-be-executed task is allowed to be executed or not according to the M identification results, and executing the target to-be-executed task according to the M target data tables under the condition that the target to-be-executed task is allowed to be executed. Through the method and the device, the problem that the execution success rate and the accuracy rate of the business task are relatively low under the condition that the data synchronization task is abnormal in the prior art is solved.

Description

Technical Field

[0001] This application relates to the field of big data, and more specifically, to a method, apparatus, and electronic device for processing a task to be performed. Background Technology

[0002] In the business processing systems of financial institutions, since users need to input business data on the application side and synchronize the business data from the application side to the business processing system for processing, data synchronization operations of application-level databases are the cornerstone of maintaining the efficient and reliable operation of the system.

[0003] However, in practice, the data synchronization process is affected by a variety of factors, including network conditions, performance differences between the source and target databases, and the adaptability of the synchronization strategy. These factors may lead to data synchronization failure or abnormal data status. When data synchronization problems occur, if they are not detected and handled in a timely manner, subsequent business tasks that rely on this data may be affected. This could not only lead to inaccurate task execution results but may even cause task execution processes to be interrupted, seriously impacting business continuity and user experience.

[0004] There is currently no effective solution to the problem of low success rate and accuracy of business tasks when data synchronization tasks encounter anomalies in related technologies. Summary of the Invention

[0005] The main objective of this application is to provide a method, apparatus, and electronic device for processing tasks to be executed, in order to solve the problem of low success rate and accuracy of business task execution when data synchronization tasks encounter anomalies in related technologies.

[0006] To achieve the above objectives, according to one aspect of this application, a method for processing a task to be executed is provided. The method includes: determining a set of target data required to execute a target task to be executed, and determining, from a local database, a data table containing the target data set, resulting in M ​​target data tables, wherein the target data set includes at least one target data, and each target data table contains at least one target data, and M is a positive integer; querying the target task execution data of the data synchronization task from the workflow record table in the local database, resulting in M ​​sets of target task execution data; obtaining execution information required to execute the target task to be executed, and identifying the M sets of target task execution data based on the execution information, resulting in M ​​identification results, wherein the identification results are used to indicate whether there are any anomalies in the target task execution data; determining, based on the M identification results, whether execution of the target task to be executed is permitted, and, if execution of the target task to be executed is permitted, executing the target task to be executed according to the M target data tables.

[0007] Optionally, determining the data tables containing the target data set from the local database to obtain M target data tables includes: for each target data, determining the first table name for the data table used to store the target data; performing a query operation in the local database based on the first table name to obtain the query result; if the query result indicates that a local data table corresponding to the first table name exists, determining the local data table as the target data table of the target data; if the query result indicates that a local data table corresponding to the first table name does not exist, determining the source application of the target data, sending a data synchronization instruction to the source application, and determining the data table sent by the source application as the target data table of the target data, wherein the data synchronization instruction is used to instruct the source application to perform a data synchronization operation on the target data table; and combining the target data tables of each target data into M target data tables.

[0008] Optionally, the workflow record table includes task execution data for multiple data synchronization tasks. The workflow record table is constructed as follows: For any data synchronization task, record the task execution data of the data synchronization task, wherein the task execution data includes at least one of the following: start time, end time, synchronization method, and synchronization result; obtain the name of the second table of the data table being synchronized in the data synchronization task, and associate the second table name with the task execution data and store it in the initial table to obtain the workflow record table, and store the data table synchronized by the data synchronization task in the local database.

[0009] Optionally, querying the target task execution data of the data synchronization task for M target data tables from the workflow record table in the local database includes: for any target data table, determining whether task execution data for the target data table exists in the workflow record table based on the third table name of the target data table; if no task execution data for the target data table exists, executing the step of determining whether task execution data for the target data table exists in the workflow record table based on the third table name of the target data table according to a preset cycle until task execution data for the target data table exists in the workflow record table; if task execution data for the target data table exists, retrieving the data with the latest creation time to obtain the target task execution data.

[0010] Optionally, the M sets of target task execution data are identified based on the execution information to obtain M identification results, including: for any set of target task execution data, obtaining the synchronization duration, synchronization result, and synchronization completion time in the target task execution data; obtaining the update cycle of the target data table corresponding to the target task execution data from the execution information, and determining the update result of the target data table based on the update cycle and synchronization completion time; obtaining the duration threshold from the execution information, and comparing the duration threshold with the synchronization duration to obtain the comparison result; obtaining the identification requirements from the execution information, and identifying the comparison result, update result, and synchronization result based on the identification requirements to obtain the identification result, wherein the identification result is used to characterize whether the target data table is allowed to be applied to the target task to be executed.

[0011] Optionally, determining whether to allow the execution of the target task based on the M identification results includes: determining whether there are any abnormal identification results representing anomalies among the M identification results; if there are abnormal identification results, determining that the execution of the target task is not allowed; if there are no abnormal identification results, determining that the execution of the target task is allowed.

[0012] Optionally, if the synchronization result indicates that the data synchronization task has failed, the method further includes: determining whether the data in the target data table corresponding to the data synchronization task has changed; if the data in the target data table has not changed, re-executing the data synchronization task until the synchronization result of the data synchronization task is successful, or the number of re-executions of the data synchronization task reaches a preset number; if the data in the target data table has changed, identifying the target data table as an abnormal data table and sending alarm information to the operation and maintenance end, wherein the alarm information is used to indicate that the data in the target data table is abnormal.

[0013] To achieve the above objectives, according to another aspect of this application, a processing apparatus for a task to be executed is provided. The apparatus includes: a first determining unit, configured to determine a set of target data required to execute a target task, and to determine data tables containing the target data set from a local database, obtaining M target data tables, wherein the target data set includes at least one target data, and each target data table contains at least one target data, and M is a positive integer; a querying unit, configured to query the target task execution data of the data synchronization task from the workflow record table of the M target data tables in the local database, obtaining M sets of target task execution data; an acquiring unit, configured to acquire execution information required to execute the target task, and to identify the M sets of target task execution data according to the execution information, obtaining M identification results, wherein the identification results are used to indicate whether there are any abnormalities in the target task execution data; and a first judging unit, configured to judge whether the execution of the target task is permitted based on the M identification results, and, if the execution of the target task is permitted, to execute the target task according to the M target data tables.

[0014] Optionally, in the processing apparatus for the task to be executed provided in the embodiments of this application, the first determining unit includes: a first determining module, configured to determine, for each target data, a first table name for a data table used to store the target data; a query module, configured to perform a query operation in a local database according to the first table name to obtain a query result; a second determining module, configured to determine the local data table as the target data table of the target data if the query result indicates that a local data table corresponding to the first table name exists; a sending module, configured to determine the source application of the target data and send a data synchronization instruction to the source application if the query result indicates that a local data table corresponding to the first table name does not exist, and determine the data table sent by the source application as the target data table of the target data, wherein the data synchronization instruction is used to instruct the source application to perform a data synchronization operation on the target data table; and a combining module, configured to combine the target data tables of each target data into M target data tables.

[0015] Optionally, in the processing device for tasks to be executed provided in the embodiments of this application, the workflow record table includes task execution data of multiple data synchronization tasks. The workflow record table is constructed by the following devices: a recording unit, used to record the task execution data of any data synchronization task, wherein the task execution data includes at least one of the following: start time, completion time, synchronization method, and synchronization result; and a storage unit, used to obtain the name of the second table of the data table synchronized in the data synchronization task, associate the second table name with the task execution data and store it in the initial table to obtain the workflow record table, and store the data table synchronized by the data synchronization task in the local database.

[0016] Optionally, in the processing device for tasks to be executed provided in this application embodiment, the query unit includes: a third determining module, used to determine whether task execution data of the target data table exists in the workflow record table based on the third table name of the target data table for any target data table; an execution module, used to execute the step of determining whether task execution data of the target data table exists in the workflow record table based on the third table name of the target data table according to a preset period when no task execution data of the target data table exists, until task execution data of the target data table exists in the workflow record table; and a first obtaining module, used to obtain the latest data created when task execution data of the target data table exists, to obtain the target task execution data.

[0017] Optionally, in the processing device for the task to be executed provided in this application embodiment, the acquisition unit includes: a second acquisition module, used to acquire the synchronization duration, synchronization result, and synchronization completion time in any set of target task execution data; a third acquisition module, used to acquire the update cycle of the target data table corresponding to the target task execution data from the execution information, and determine the update result of the target data table according to the update cycle and the synchronization completion time; a comparison module, used to acquire a duration threshold from the execution information, and compare the duration threshold with the synchronization duration to obtain a comparison result; and an identification module, used to acquire identification requirements from the execution information, and identify the comparison result, update result, and synchronization result according to the identification requirements to obtain an identification result, wherein the identification result is used to characterize whether the target data table is allowed to be applied to the target task to be executed.

[0018] Optionally, in the processing device for the task to be executed provided in the embodiments of this application, the first judgment unit includes: a judgment module, used to judge whether there is an abnormal recognition result representing an abnormality among the M recognition results; a fourth determination module, used to determine that the target task to be executed is not allowed to be executed if there is an abnormal recognition result; and a fifth determination module, used to determine that the target task to be executed is allowed to be executed if there is no abnormal recognition result.

[0019] Optionally, in the processing device for the task to be executed provided in the embodiments of this application, when the synchronization result indicates that the data synchronization task has failed, the device further includes: a second judgment unit, used to judge whether the data in the target data table corresponding to the data synchronization task has changed; an execution unit, used to re-execute the data synchronization task when the data in the target data table has not changed, until the synchronization result of the data synchronization task is successful, or the number of times the data synchronization task is repeatedly executed reaches a preset number; and a second determination unit, used to determine the target data table as an abnormal data table when the data in the target data table has changed, and send alarm information to the operation and maintenance terminal, wherein the alarm information is used to indicate that the data in the target data table is abnormal.

[0020] To achieve the above objectives, according to another aspect of this application, an electronic device is provided, the electronic device including a memory storing an executable program; and a processor for running the program, wherein the program executes the processing method of the above-described task to be executed during runtime.

[0021] To achieve the above objectives, according to another aspect of this application, a computer program product is provided, including computer instructions that, when executed by a processor, implement the steps of the processing method for the task to be executed described above.

[0022] In this embodiment, a target data set required for executing the target task is determined, and a data table containing the target data set is determined from the local database, resulting in M ​​target data tables. Each target data set includes at least one target data item, and each target data table contains at least one target data item; M is a positive integer. The target task execution data of the data synchronization task for the M target data tables is queried from the workflow record table in the local database, resulting in M ​​sets of target task execution data. Execution information required for executing the target task is obtained, and the M sets of target task execution data are identified based on the execution information, resulting in M ​​identification results. These identification results indicate whether there are any anomalies in the target task execution data. Based on M identification results, it is determined whether the target task can be executed. If the target task can be executed, the execution method of the target task is determined according to the M target data tables. The data synchronization status is analyzed by querying the data tables, and the business task execution strategy is dynamically adjusted by identifying the data in the data tables. This achieves the goal of ensuring that the business task is executed when the data synchronization status is good, avoiding operations based on erroneous or outdated data. This improves the accuracy of business task processing, reduces the risk of business task interruption and data inconsistency, and solves the technical problem of low success rate and accuracy of business task execution when data synchronization tasks are abnormal in related technologies. Attached Figure Description

[0023] The accompanying drawings, which form part of this application, are used to provide a further understanding of this application. The illustrative embodiments and descriptions of this application are used to explain this application and do not constitute an undue limitation of this application. In the drawings:

[0024] Figure 1 A hardware block diagram of a computer terminal for implementing a processing method for a task to be performed is shown.

[0025] Figure 2 This is a flowchart of a method for processing a task to be executed according to Embodiment 1 of this application;

[0026] Figure 3 This is a flowchart of an optional method for processing a task to be executed according to Embodiment 1 of this application;

[0027] Figure 4 This is a schematic diagram of a processing device for a task to be performed according to Embodiment 2 of this application;

[0028] Figure 5 This is a structural block diagram of an electronic device according to an embodiment of this application. Detailed Implementation

[0029] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0030] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0031] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0032] It should be noted that the processing methods, apparatuses, and electronic devices for the tasks to be performed as defined in this disclosure can be used in the field of big data, or in any field other than big data. The application fields of the processing methods, apparatuses, and electronic devices for the tasks to be performed as defined in this disclosure are not limited.

[0033] It should be noted that all information, user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, and displayed data) used in this application are information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of related data all comply with the relevant laws, regulations, and standards of the relevant regions, have taken necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entry points for users to choose to authorize or refuse use. If the user chooses to refuse, the process proceeds to the expert decision-making process. For example, this system has interfaces with relevant users or institutions. Before obtaining relevant information, a request to obtain the information needs to be sent to the aforementioned user or institution through the interface, and the relevant information is obtained only after receiving consent from the aforementioned user or institution.

[0034] The embodiments or examples disclosed herein are not exhaustive, but merely illustrative of some embodiments or examples, and are not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment or example can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment or example can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment or example can be arbitrarily interchanged. Furthermore, optional methods or examples in a particular embodiment or example can be arbitrarily combined; moreover, embodiments or examples can be arbitrarily combined. For example, some or all steps of different embodiments or examples can be arbitrarily combined, and a particular embodiment or example can be arbitrarily combined with optional methods or examples of other embodiments or examples.

[0035] Example 1

[0036] According to an embodiment of this application, an embodiment of a method for processing a task to be executed is also provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0037] The method embodiment provided in Embodiment 1 of this application can be executed on a mobile terminal, computer terminal, or similar computing device. Figure 1 A hardware block diagram of a computer terminal for implementing a processing method for a task to be performed is shown. Figure 1As shown, the computer terminal 10 (or mobile device) may include one or more processors 102 (shown as 102a, 102b, ..., 102n in the figure) 102 (processor 102 may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of a BUS bus), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, computer terminal 10 may also include... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0038] It should be noted that the aforementioned one or more processors 102 and / or other data processing circuits are generally referred to herein as "data processing circuits". These data processing circuits may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuits may be a single, independent processing module, or may be integrated, in whole or in part, into any other element within the computer terminal 10 (or mobile device). As involved in the embodiments of this application, the data processing circuits serve as a processor control mechanism (e.g., selection of a variable resistor termination path connected to an interface).

[0039] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the processing method of the task to be executed in the embodiments of this application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, thereby realizing the above-mentioned processing method of the task to be executed. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the computer terminal 10 via a network. Examples of the above-mentioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0040] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the computer terminal 10. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0041] The display can be, for example, a touchscreen liquid crystal display (LCD) that allows the user to interact with the user interface of the computer terminal 10 (or mobile device).

[0042] Under the aforementioned operating environment, this application provides the following: Figure 2 The method for handling tasks to be executed is shown. Figure 2 This is a flowchart of the processing method for the task to be executed according to Embodiment 1 of this application, as follows: Figure 2 As shown, the method includes:

[0043] Step S201: Determine the target data set required to execute the target task, and determine the data table containing the target data set from the local database to obtain M target data tables. The target data set includes at least one target data, and each target data table contains at least one target data. M is a positive integer.

[0044] It should be noted that the target task to be executed can be a business task that performs a specific business operation, and the target data set refers to the dataset used to execute the business task. The target data table is a data table containing at least one target data item. All target data in the target data set can be obtained from M target data tables, thus ensuring the execution of the business task. The local database refers to the data storage resources of the business system.

[0045] Specifically, the execution entity in this embodiment can be a task processing system. When the system starts to execute a certain business task, it first needs to identify the business task, parse the execution flow of the business task, and thus identify the target data necessary to execute the business task, forming a target data set.

[0046] Then, the system sequentially identifies the location information of each target data storage, thereby determining the data table storing each target data, and then accurately locates the target data table storing the target data from the local database. Finally, it can retrieve each target data from the target data table, thus completing the execution process of the business task.

[0047] Step S202: Query the target task execution data of the data synchronization task of M target data tables from the workflow record table in the local database to obtain M sets of target task execution data.

[0048] It should be noted that the workflow record table, which is also the repository for the status and execution history of data synchronization tasks, contains detailed information about all data synchronization tasks, such as synchronization status, synchronization time, synchronization duration, synchronization results, and exception information. Target task execution data refers to the specific execution data of the data synchronization tasks related to the M target data tables.

[0049] Specifically, after identifying M target data tables, it is necessary to determine the data synchronization status of each target data table. Then, based on the data synchronization status, it can be determined whether the data recorded in the tables can be used to execute business tasks. When determining the data synchronization status of each target data table, the target task execution data of each target data table can be queried from the workflow record table. The data synchronization status can be determined based on the target task execution data.

[0050] Therefore, given that there are M target data tables, the system can access the workflow record table in the local database, retrieve the latest execution records of data synchronization tasks related to the M target data tables through database queries, and then determine the synchronization status and performance indicators of the target data tables through the query results, including but not limited to the start and end times of synchronization, synchronization time, whether the last synchronization was successful, the specific type of synchronization failure (such as data expiration, data unavailability), and any abnormal information that may be encountered during the synchronization process.

[0051] Step S203: Obtain the execution information required for the target task to be executed, and identify the M sets of target task execution data according to the execution information to obtain M identification results. The identification results are used to indicate whether there are any abnormalities in the target task execution data.

[0052] It should be noted that the execution information can be the rules and conditions for executing business tasks, including but not limited to data timeliness requirements, data quality standards, and exception handling strategies. The identification result is a judgment on whether the synchronization status of the target data table meets the conditions for executing the business task.

[0053] Specifically, after obtaining the target task execution data, the system can determine the availability of data in each data table based on the target task execution data of each data table. First, the system can read execution information related to the target tasks to be executed in each target data table from the local configuration file or database, including but not limited to thresholds for data synchronization results, data timeliness requirements, and minimum data volume standards. Then, the system uses the execution information to identify and analyze the obtained M sets of target task execution data, checking for any data synchronization anomalies or situations that do not meet the business task execution conditions, and obtains the identification results of each target task execution data. This includes performing a series of data integrity checks, timestamp comparisons, and data volume analysis to ensure an accurate assessment of the data availability in the target data tables.

[0054] Step S204: Determine whether the target task to be executed is allowed based on the M identification results, and if the target task to be executed is allowed, execute the target task to be executed according to the M target data tables.

[0055] It should be noted that the identification results are used to indicate whether the data status of the M target data tables meets the execution conditions of the business task.

[0056] Specifically, after obtaining M recognition results, the system needs to comprehensively evaluate whether the synchronization status of all target data tables meets the execution threshold of the business task. If all recognition results indicate successful data synchronization and meet the conditions specified in the execution information, the system will automatically determine that the target task can be executed. At this time, the system will call the corresponding business logic module to execute the target task based on the target data in the M target data tables. Conversely, if any anomalies are found in the recognition results, the system will suspend the execution of the business task to ensure its accurate execution.

[0057] The method for processing tasks to be executed provided in this application involves determining the target data set required to execute the target task, and determining a data table containing the target data set from a local database to obtain M target data tables. Each target data set includes at least one target data item, and each target data table contains at least one target data item; M is a positive integer; querying the workflow record table in the local database for the target task execution data of the data synchronization task in the M target data tables to obtain M sets of target task execution data; acquiring the execution information required to execute the target task, and identifying the M sets of target task execution data based on the execution information to obtain M identification results. The identification results indicate whether the target task execution data is... An anomaly exists; based on M identification results, it is determined whether the target task to be executed is allowed. If the target task to be executed is allowed, the execution method of the target task is determined according to the M target data tables. The data synchronization status is analyzed by querying the data tables, and the business task execution strategy is dynamically adjusted by identifying the data in the data tables. This achieves the goal of ensuring that the business task is executed when the data synchronization status is good, avoiding operations based on erroneous or outdated data. This improves the accuracy of business task processing, reduces the risk of business task interruption and data inconsistency, and solves the technical problem of low success rate and accuracy of business task execution when anomalies occur in related technologies.

[0058] To accurately obtain the data tables for each target data, optionally, in the processing method for the task to be executed provided in this application embodiment, determining the data tables containing the target data set from the local database to obtain M target data tables includes: for each target data, determining the first table name for the data table used to store the target data; performing a query operation in the local database according to the first table name to obtain a query result; if the query result indicates that a local data table corresponding to the first table name exists, determining the local data table as the target data table for the target data; if the query result indicates that a local data table corresponding to the first table name does not exist, determining the source application of the target data, sending a data synchronization instruction to the source application, and determining the data table sent by the source application as the target data table for the target data, wherein the data synchronization instruction is used to instruct the source application to perform a data synchronization operation on the target data table; and combining the target data tables of each target data into M target data tables.

[0059] Specifically, when determining the target data table where each target data resides, it is first necessary to determine the name of the first table used to store the target data, and then perform a precise query operation in the local database environment based on the first table name to verify whether a local data table matching the first table name exists.

[0060] If the query results show a matching local data table, it is marked as the target data table and added to the set of M target data tables. If the query results show that the corresponding data table does not exist in the local database, it indicates that the data table to which the target data belongs has not yet been synchronized from the application database to the system database. In this case, the system will determine the source application of the target data and send a data synchronization instruction to the source application, instructing it to perform data synchronization operations on the target data table. The data synchronization instruction includes the specific requirements of the synchronization operation and the name of the target data table, ensuring that the source application can accurately identify and synchronize the required data. Once data synchronization is complete, the source application will send the synchronized data table to the system, and the system will mark it as the target data table of the target data, thus completing the data table retrieval operation for each target data.

[0061] This embodiment ensures that all data can be retrieved from the corresponding data table by obtaining the target data, thereby guaranteeing the normal execution of business tasks.

[0062] To ensure the accuracy of the workflow record table, optionally, in the task processing method provided in this application embodiment, the workflow record table includes task execution data of multiple data synchronization tasks. The workflow record table is constructed in the following way: for any data synchronization task, record the task execution data of the data synchronization task, wherein the task execution data includes at least one of the following: start time, completion time, synchronization method, and synchronization result; obtain the name of the second table of the data table synchronized in the data synchronization task, and associate the second table name with the task execution data and store it in the initial table to obtain the workflow record table, and store the data table synchronized by the data synchronization task in the local database.

[0063] It should be noted that the workflow record table is used to store and manage detailed execution information of data synchronization tasks, including but not limited to the start time, end time, synchronization method, and synchronization result. The data synchronization task is responsible for extracting data from different data sources and synchronizing it to the local database. The second table name refers to the name of the data table specified in the data synchronization task and stored in the local database.

[0064] Specifically, when constructing the workflow record table, the construction process needs to be determined to ensure that the execution information of each data synchronization task is accurately recorded. The workflow record table construction process first requires recording the start time of the task and the synchronization method used (e.g., incremental synchronization, full synchronization) upon receiving the data synchronization task execution request. After the data synchronization task is completed, the completion time and the final synchronization result (e.g., success, failure) need to be recorded. The synchronization result not only reflects the real-time status of data synchronization but also provides important reference for subsequent business task execution. The start time, completion time, synchronization method, and synchronization result are defined as task execution information.

[0065] After obtaining the task execution data of the data synchronization task, the system needs to determine the name of the data table transmitted in this data synchronization task, that is, the name of the second table, and associate the name of the second table with the task execution data for storage. Then, the task execution data of multiple data synchronization tasks and the second table name are combined to obtain the workflow record table. At the same time, the task execution data of each target data table can be queried according to the second table name.

[0066] It should be noted that after the data synchronization task is completed, the system also needs to store the synchronized data table in the local database to ensure that the data in the data table can be retrieved directly from the local database in subsequent applications.

[0067] This embodiment lays the foundation for subsequent operations to query the task execution data of data synchronization tasks based on the table name by constructing a workflow data table, thereby improving the query efficiency of task execution data.

[0068] To accurately query the target task execution data of each target data table's data synchronization task, optionally, in the task processing method provided in this application embodiment, querying the target task execution data of M target data tables from the workflow record table in the local database includes: for any target data table, determining whether task execution data for the target data table exists in the workflow record table based on the third table name of the target data table; if no task execution data for the target data table exists, executing the step of determining whether task execution data for the target data table exists in the workflow record table based on the third table name of the target data table according to a preset cycle until task execution data for the target data table exists in the workflow record table; if task execution data for the target data table exists, obtaining the data with the latest creation time to obtain the target task execution data.

[0069] Specifically, when querying task execution data for a target data table, a query can be performed in the workflow record table based on the table name of the target data table to obtain the query results. If the query results show that the task execution data for the target data table does not exist in the workflow record table, it indicates that the data table was already in the local data table when it was generated in the local database. At this point, it can be determined that the data in the target data table has expired. In this case, a data table retrieval request can be sent to the application database, and the steps of determining whether the task execution data for the target data table exists in the workflow record table based on the third table name of the target data table can be continuously executed until the synchronized record of the target data table is found, that is, the application database completes the data synchronization operation, thereby obtaining the task execution data.

[0070] When the workflow record table contains task execution data from the target data table, since the workflow record table may contain multiple task execution data from the same database, the system can further filter out the record with the latest creation time, that is, the execution data of the most recent data synchronization task, thereby ensuring the accuracy and effectiveness of the system's data identification operation.

[0071] This embodiment acquires and filters the target task execution data to ensure that the most timely and accurate task execution data is obtained, thereby ensuring the accuracy of subsequent analysis of the task execution data.

[0072] To accurately identify and analyze task execution data, optionally, in the task processing method provided in this application embodiment, identifying M sets of target task execution data based on execution information to obtain M identification results includes: for any set of target task execution data, obtaining the synchronization duration, synchronization result, and synchronization completion time in the target task execution data; obtaining the update cycle of the target data table corresponding to the target task execution data from the execution information, and determining the update result of the target data table based on the update cycle and synchronization completion time; obtaining a duration threshold from the execution information, and comparing the duration threshold with the synchronization duration to obtain a comparison result; obtaining identification requirements from the execution information, and identifying the comparison result, update result, and synchronization result based on the identification requirements to obtain an identification result, wherein the identification result is used to characterize whether the target data table is allowed to be applied to the target task to be executed.

[0073] It should be noted that the synchronization duration is the total time required for the data synchronization task from start to finish; the synchronization result reflects the final status of the data synchronization task, including but not limited to success, failure-data expiration, and failure-unavailable; the synchronization completion time refers to the exact point in time when the data synchronization task ends. All of this data is key information stored in the workflow record table.

[0074] Specifically, when identifying and analyzing task execution data, it is first necessary to read all synchronous task execution data related to the M target data tables from the workflow record table. For each set of target task execution data, it is necessary to obtain the synchronization duration, i.e., the total time spent from the start to the end of data synchronization; the synchronization result, including the data synchronization status and any abnormal information; and the synchronization completion time, i.e., the exact time when data synchronization ended, etc., and then determine whether the target data in the target data table can be used based on the analysis results of the above information.

[0075] First, the system obtains the update cycle of the target data table from the execution information, which is a pre-set time interval based on business requirements to define the update frequency of the data table. The system needs to calculate the latest update time of the target data table and compare it with the synchronization completion time of the target data table to determine whether the target data table has been updated in a timely manner.

[0076] Furthermore, the system also needs to obtain the duration threshold from the execution information and compare the obtained synchronization duration with the duration threshold to determine the duration of the synchronization operation.

[0077] Finally, after obtaining the above comparison results, it is necessary to comprehensively determine whether the data in the target data table can be used normally based on the synchronization results in the synchronous task execution data and the comparison results of the two comparisons. During the evaluation, the identification requirements for each target data table can be obtained. That is, the requirements for data in different target data tables are different when executing business tasks. Therefore, the conditions for executing the business task for each target data table can be obtained from the identification requirements, and the conditions for executing the business task can be evaluated based on the above comparison results. If all results meet the identification requirements, the system will assign the target data table an "application allowed" identification result; otherwise, if any result does not meet the requirements, the system will determine that the data table is "not allowed to be applied", thereby ensuring the accurate execution of business tasks when using target data tables to execute business tasks.

[0078] This embodiment ensures the accuracy of executing business tasks based on the data in the target data table by evaluating whether the status of the target data table meets the execution requirements of the business task.

[0079] Optionally, in the method for processing a task to be executed provided in the embodiments of this application, determining whether to allow the execution of the target task to be executed based on M identification results includes: determining whether there are any abnormal identification results representing abnormalities among the M identification results; if there are abnormal identification results, determining that the execution of the target task to be executed is not allowed; if there are no abnormal identification results, determining that the execution of the target task to be executed is allowed.

[0080] Specifically, after obtaining the identification results of the task execution data, if the identification result corresponding to any target data table is abnormal, it is determined that the target task to be executed is not allowed to be executed. If the identification results corresponding to all target data tables are without abnormalities, the target task to be executed can be executed. This ensures that the business task is executed only when all the data in the target data tables is valid, thus guaranteeing the accuracy of the business task.

[0081] This embodiment ensures the accurate execution of business tasks by processing the identification results of the target data table.

[0082] Optionally, in the method for processing tasks to be executed provided in the embodiments of this application, if the synchronization result indicates that the data synchronization task has failed, the method further includes: determining whether the data in the target data table corresponding to the data synchronization task has changed; if the data in the target data table has not changed, re-executing the data synchronization task until the synchronization result of the data synchronization task is successful, or the number of times the data synchronization task is repeatedly executed reaches a preset number; if the data in the target data table has changed, identifying the target data table as an abnormal data table and sending alarm information to the operation and maintenance terminal, wherein the alarm information is used to indicate that the data in the target data table is abnormal.

[0083] Specifically, when the synchronization result in the data synchronization task fails, it is first necessary to determine whether the data in the target data table corresponding to the data synchronization task has changed. This determines whether the original data in the target data table has changed. If it has changed, in the next synchronization process, if the synchronization operation is incremental data synchronization, the data in the target data table will have changed after synchronization. It is impossible to determine whether data loss or tampering occurred in the previous failed synchronization operation. Therefore, the target data table needs to be identified as an abnormal data table, and an alarm message needs to be sent to the operation and maintenance department. This allows the operation and maintenance personnel to intervene manually in a timely manner based on the alarm message and handle the abnormal data table to avoid the potential impact of abnormal data on the execution of subsequent business tasks.

[0084] If the data in the target data table has not changed, indicating that the target data table has not been altered, meaning that the failed data synchronization operation has not affected the target data table, the data synchronization task can be re-executed until the synchronization result is successful. A preset limit on the number of repetitions should also be set to prevent resource waste caused by infinite looping synchronization attempts. If the preset number of repetitions for the data synchronization task is reached and synchronization still fails, an alarm should be sent to the operations and maintenance team to prevent the potential impact of abnormal data on the execution of subsequent business tasks.

[0085] This embodiment significantly enhances the fault tolerance and business continuity of data synchronization tasks by detecting data changes and selecting different error recovery strategies based on different data change situations.

[0086] Figure 3 This is a flowchart of an optional method for processing a task to be executed according to Embodiment 1 of this application, as shown below. Figure 3 As shown, the system simultaneously receives the data tables to be synchronized and the task information of the data synchronization task sent by the application side. It stores the data tables in the database and adds the task information to the workflow record table. For the data synchronization task, the system can use a database connection to synchronize data from a remote application database. Before, during, and after the synchronization process, the system registers the information involved in the synchronization operation in the workflow. This allows the administrator to clearly understand the synchronization status, synchronization method (incremental, full), synchronization time, last successful synchronization time, synchronization result (success, failure-unavailable, failure-data expired), synchronization exception information, synchronization time, and the amount of table data after synchronization for each data table.

[0087] After completing the data synchronization task, it is necessary to determine whether the synchronization operation was successful. If successful, the data synchronization task is complete. If it fails, it is necessary to determine whether the expired data in the historical data table stored in the database has been changed, that is, whether it can still be used. If it has not been changed, that is, the expired data can be used, then it is necessary to determine whether the number of synchronizations for the data synchronization task has exceeded the threshold. If it has not exceeded the threshold, the data synchronization task can be restarted. If the data in the historical data table has been changed, or the number of synchronizations for the data synchronization task has exceeded the threshold, a prompt message is sent to the operations and maintenance department for handling by the operations and maintenance personnel.

[0088] Upon receiving an execution instruction for a business task, it is necessary to determine whether the data used to execute the business task meets the preset requirements based on the information recorded in the workflow log table. If it does, the task can be executed; otherwise, it will not be executed, thereby ensuring the accuracy of the data used to execute the business task.

[0089] It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases the steps shown or described may be executed in a different order than that shown here.

[0090] Example 2

[0091] This application also provides a processing device for tasks to be executed. It should be noted that the processing device for tasks to be executed in this application can be used to execute the processing method for tasks to be executed provided in the above embodiments. The processing device for tasks to be executed provided in this application will be described below.

[0092] According to an embodiment of this application, an apparatus for implementing the above-described processing method for the task to be performed is also provided. Figure 4 This is a schematic diagram of a processing device for a task to be performed according to Embodiment 2 of this application, as shown below. Figure 4 As shown, the device includes:

[0093] The first determining unit 41 is used to determine the target data set required to perform the target task, and to determine the data table containing the target data set from the local database to obtain M target data tables. The target data set includes at least one target data, and each target data table contains at least one target data. M is a positive integer.

[0094] The query unit 42 is used to query the target task execution data of the data synchronization task of M target data tables from the workflow record table in the local database, and obtain M sets of target task execution data.

[0095] The acquisition unit 43 is used to acquire the execution information required for the target task to be executed, and to identify the M sets of target task execution data according to the execution information to obtain M identification results. The identification results are used to indicate whether there are any abnormalities in the target task execution data.

[0096] The first judgment unit 44 is used to determine whether the target task to be executed is allowed to be executed based on the M recognition results, and if the target task to be executed is allowed to be executed, the target task to be executed is executed based on the M target data tables.

[0097] The processing apparatus for the task to be executed provided in this application embodiment determines the target data set required to execute the target task to be executed by the first determining unit 41, and determines the data table containing the target data set from the local database to obtain M target data tables, wherein the target data set includes at least one target data, and each target data table contains at least one target data, and M is a positive integer; the querying unit 42 queries the target task execution data of the data synchronization task of the M target data tables from the workflow record table in the local database to obtain M sets of target task execution data; the obtaining unit 43 obtains the execution information required to execute the target task to be executed, and identifies the M sets of target task execution data according to the execution information to obtain M identification results, wherein the identification results are used to indicate whether there is an anomaly in the target task execution data; the first judging unit 44 judges whether to allow the execution of the target task to be executed according to the M identification results, and if the execution of the target task to be executed is allowed, executes the target task to be executed according to the M target data tables. By analyzing the data synchronization status through querying data tables and dynamically adjusting the business task execution strategy by identifying the data in the data tables, the goal of ensuring that business tasks are executed under good data synchronization conditions is achieved, avoiding operations based on erroneous or outdated data. This improves the accuracy of business task processing, reduces the risk of business task interruption and data inconsistency, and solves the technical problem of low success rate and accuracy of business task execution when data synchronization tasks are abnormal.

[0098] Optionally, in the processing apparatus for the task to be executed provided in the embodiments of this application, the first determining unit 41 includes: a first determining module, configured to determine a first table name for a data table used to store the target data for each target data; a query module, configured to perform a query operation in a local database according to the first table name to obtain a query result; a second determining module, configured to determine the local data table as the target data table of the target data if the query result indicates that a local data table corresponding to the first table name exists; a sending module, configured to determine the source application of the target data and send a data synchronization instruction to the source application if the query result indicates that a local data table corresponding to the first table name does not exist, and determine the data table sent by the source application as the target data table of the target data, wherein the data synchronization instruction is used to instruct the source application to perform a data synchronization operation on the target data table; and a combining module, configured to combine the target data tables of each target data into M target data tables.

[0099] Optionally, in the processing device for tasks to be executed provided in the embodiments of this application, the workflow record table includes task execution data of multiple data synchronization tasks. The workflow record table is constructed by the following devices: a recording unit, used to record the task execution data of any data synchronization task, wherein the task execution data includes at least one of the following: start time, completion time, synchronization method, and synchronization result; and a storage unit, used to obtain the name of the second table of the data table synchronized in the data synchronization task, associate the second table name with the task execution data and store it in the initial table to obtain the workflow record table, and store the data table synchronized by the data synchronization task in the local database.

[0100] Optionally, in the processing device for tasks to be executed provided in this application embodiment, the query unit 42 includes: a third determining module, used to determine whether task execution data of the target data table exists in the workflow record table based on the third table name of the target data table for any target data table; an execution module, used to execute the step of determining whether task execution data of the target data table exists in the workflow record table based on the third table name of the target data table according to a preset period when no task execution data of the target data table exists, until task execution data of the target data table exists in the workflow record table; and a first obtaining module, used to obtain the latest data created when task execution data of the target data table exists, to obtain the target task execution data.

[0101] Optionally, in the processing device for the task to be executed provided in this application embodiment, the acquisition unit 43 includes: a second acquisition module, used to acquire the synchronization duration, synchronization result, and synchronization completion time in any set of target task execution data; a third acquisition module, used to acquire the update cycle of the target data table corresponding to the target task execution data from the execution information, and determine the update result of the target data table according to the update cycle and the synchronization completion time; a comparison module, used to acquire a duration threshold from the execution information, and compare the duration threshold with the synchronization duration to obtain a comparison result; and an identification module, used to acquire identification requirements from the execution information, and identify the comparison result, update result, and synchronization result according to the identification requirements to obtain an identification result, wherein the identification result is used to characterize whether the target data table is allowed to be applied to the target task to be executed.

[0102] Optionally, in the processing device for the task to be executed provided in the embodiments of this application, the first judgment unit 44 includes: a judgment module, used to judge whether there is an abnormal recognition result representing an abnormality among the M recognition results; a fourth determination module, used to determine that the target task to be executed is not allowed to be executed if there is an abnormal recognition result; and a fifth determination module, used to determine that the target task to be executed is allowed to be executed if there is no abnormal recognition result.

[0103] Optionally, in the processing device for the task to be executed provided in the embodiments of this application, when the synchronization result indicates that the data synchronization task has failed, the device further includes: a second judgment unit, used to judge whether the data in the target data table corresponding to the data synchronization task has changed; an execution unit, used to re-execute the data synchronization task when the data in the target data table has not changed, until the synchronization result of the data synchronization task is successful, or the number of times the data synchronization task is repeatedly executed reaches a preset number; and a second determination unit, used to determine the target data table as an abnormal data table when the data in the target data table has changed, and send alarm information to the operation and maintenance terminal, wherein the alarm information is used to indicate that the data in the target data table is abnormal.

[0104] It should be noted that the first determining unit 41, querying unit 42, obtaining unit 43, and first judging unit 44 mentioned above correspond to steps S201 to S204 in Embodiment 1. The instances and application scenarios implemented by each of the above units and corresponding steps are the same, but are not limited to the content disclosed in Embodiment 1. It should be noted that the above modules or units can be hardware components or software components stored in memory (e.g., memory 104) and processed by one or more processors (e.g., processors 102a, 102b, ..., 102n). The above modules can also be part of a device and can run in the computer terminal 10 provided in Embodiment 1.

[0105] Example 3

[0106] Embodiments of this application may provide an electronic device. Figure 5 This is a structural block diagram of an electronic device according to an embodiment of this application. Figure 5 As shown, the electronic device may include: one or more ( Figure 5 (Only one is shown) processor 1002, memory 1004, memory controller, and peripheral interface, wherein the peripheral interface is connected to the radio frequency module, audio module and display.

[0107] The memory can be used to store software programs and modules, such as the program instructions / modules corresponding to the methods and apparatus in the embodiments of this application. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, thereby implementing the above-described methods. The memory may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include memory remotely located relative to the processor, and these remote memories can be connected to the terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0108] The processor can access information and applications stored in memory via a transmission device to perform the following steps: determine the target data set required to execute the target task, and determine the data table containing the target data set from the local database, obtaining M target data tables, where the target data set includes at least one target data, and each target data table contains at least one target data, and M is a positive integer; query the target task execution data of the data synchronization task from the workflow record table of the M target data tables in the local database, obtaining M sets of target task execution data; obtain the execution information required to execute the target task, and identify the M sets of target task execution data according to the execution information, obtaining M identification results, where the identification results are used to indicate whether there are any abnormalities in the target task execution data; determine whether the execution of the target task is allowed based on the M identification results, and if the execution of the target task is allowed, execute the target task according to the M target data tables.

[0109] Those skilled in the art will understand that Figure 5 The structure shown is for illustrative purposes only. Electronic devices can also be smartphones, tablets, handheld computers, mobile internet devices (MIDs), PADs, and other terminal devices. Figure 5 This does not limit the structure of the aforementioned electronic device. For example, electronic devices may also include components that are more... Figure 5 The more or fewer components shown (such as network interfaces, display devices, etc.), or having the same Figure 5 The different configurations shown.

[0110] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing the hardware related to the terminal device. The program can be stored in a computer-readable storage medium, which may include: flash drive, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0111] Example 4

[0112] Embodiments of this application also provide a storage medium. Optionally, in this embodiment, the storage medium can be used to store the program code executed by the processing method of the task to be executed provided in Embodiment 1.

[0113] Optionally, in this embodiment, the storage medium may be located in any computer terminal in a group of computer terminals in a computer network, or in any mobile terminal in a group of mobile terminals.

[0114] Embodiments of this application also provide a computer program product, which, when executed on a data processing device, is a program adapted to perform the steps of a processing method for a task to be performed.

[0115] Embodiments of this application also provide a computer-readable storage medium, which includes a stored executable program, wherein the processing method for controlling the device where the computer-readable storage medium is located to perform the above-described task to be performed is provided when the executable program is running.

[0116] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0117] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0118] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0119] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0120] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0121] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0122] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for processing a task to be executed, characterized in that, include: Determine the target data set required to execute the target task, and determine the data table containing the target data set from the local database to obtain M target data tables, wherein the target data set includes at least one target data, and each target data table contains at least one target data, and M is a positive integer; Query the target task execution data of the data synchronization task of the M target data tables from the workflow record table in the local database to obtain M sets of target task execution data; Obtain the execution information required to execute the target task, and identify the M sets of target task execution data based on the execution information to obtain M identification results, wherein the identification results are used to indicate whether there are any abnormalities in the target task execution data; Based on the M identification results, determine whether the target task to be executed is allowed, and if the target task to be executed is allowed, execute the target task according to the M target data tables.

2. The method according to claim 1, characterized in that, From the local database, determine the data tables containing the target data set, resulting in M ​​target data tables, including: For each target data, determine the name of the first table used to store the target data; Execute a query operation in the local database based on the name of the first table to obtain the query results; If the query results indicate the existence of a local data table corresponding to the first table name, then the local data table is determined as the target data table for the target data. If the query result indicates that there is no local data table corresponding to the first table name, the source application of the target data is determined, and a data synchronization instruction is sent to the source application. The data table sent by the source application is determined as the target data table of the target data. The data synchronization instruction is used to instruct the source application to perform a data synchronization operation on the target data table. The target data tables of each target data are combined into the M target data tables.

3. The method according to claim 1, characterized in that, The workflow record table includes task execution data for multiple data synchronization tasks, and the workflow record table is constructed in the following manner: For any data synchronization task, record the task execution data of the data synchronization task, wherein the task execution data includes at least one of the following: start time, completion time, synchronization method, and synchronization result; Obtain the name of the second table of the data table to be synchronized in the data synchronization task, associate the second table name with the task execution data and store it in the initial table to obtain the workflow record table, and store the data table synchronized by the data synchronization task in the local database.

4. The method according to claim 1, characterized in that, The target task execution data for the data synchronization task of the M target data tables is retrieved from the workflow record table in the local database, including: For any target data table, determine whether the task execution data of the target data table exists in the workflow record table based on the name of the third table of the target data table; If no task execution data exists in the target data table, the step of determining whether the task execution data of the target data table exists in the workflow record table based on the third table name of the target data table is executed according to a preset period until the task execution data of the target data table exists in the workflow record table. If the target data table contains task execution data, retrieve the record with the latest creation time to obtain the target task execution data.

5. The method according to claim 1, characterized in that, Based on the execution information, the execution data of the M groups of target tasks are identified, resulting in M ​​identification results, including: For any set of target task execution data, obtain the synchronization duration, synchronization result, and synchronization completion time from the target task execution data; The update cycle of the target data table corresponding to the target task execution data is obtained from the execution information, and the update result of the target data table is determined according to the update cycle and the synchronization completion time. The duration threshold is obtained from the execution information, and the duration threshold is compared with the synchronization duration to obtain the comparison result; The identification requirements are obtained from the execution information, and the comparison results, update results and synchronization results are identified according to the identification requirements to obtain the identification results, wherein the identification results are used to characterize whether the target data table is allowed to be applied to the target task to be executed.

6. The method according to claim 1, characterized in that, Determining whether to allow the execution of the target task based on the M recognition results includes: Determine whether any of the M identification results represent anomalies; If the anomaly identification result exists, it is determined that the execution of the target task to be executed is not allowed; if the anomaly identification result does not exist, it is determined that the execution of the target task to be executed is allowed.

7. The method according to claim 5, characterized in that, If the synchronization result indicates that the data synchronization task has failed, the method further includes: Determine whether the data in the target data table corresponding to the data synchronization task has changed; If the data in the target data table has not changed, the data synchronization task is re-executed until the synchronization result of the data synchronization task is successful, or the number of times the data synchronization task is repeated reaches a preset number. If the data in the target data table changes, the target data table is identified as an abnormal data table, and an alarm message is sent to the operation and maintenance terminal. The alarm message is used to indicate that the data in the target data table is abnormal.

8. A processing device for a task to be performed, characterized in that, include: The first determining unit is used to determine the target data set required to execute the target task, and to determine the data table containing the target data set from the local database to obtain M target data tables, wherein the target data set includes at least one target data, each target data table contains at least one target data, and M is a positive integer; The query unit is used to query the target task execution data of the data synchronization tasks of the M target data tables from the workflow record table in the local database, and obtain M sets of target task execution data; The acquisition unit is used to acquire the execution information required to execute the target task to be executed, and to identify the M sets of target task execution data according to the execution information to obtain M identification results, wherein the identification results are used to indicate whether there is an anomaly in the target task execution data; The first judgment unit is used to determine whether the execution of the target task is allowed based on the M recognition results, and if the execution of the target task is allowed, to execute the target task according to the M target data tables.

9. A computer program product comprising computer instructions, characterized in that, When the computer instructions are executed by the processor, they implement the steps of the processing method for the task to be executed according to any one of claims 1 to 7.

10. An electronic device, characterized in that, include: Memory, which stores executable programs; A processor for running the program, wherein the program, when running, executes the processing method of the task to be executed according to any one of claims 1 to 7.

Images