Task Execution Method, Device, Computer Equipment and Medium

Abstract

The embodiments of this specification provide a task execution method, apparatus, computer device, and medium. The method includes: executing a first export task including a plurality of first subtasks, where the first subtasks that fail to execute in the first export task form a failure task set; executing a second export task, where the second export task at least includes a second task corresponding to the first subtask in the failure task set; and merging the export data of the second export task with the export data of the first export task to form result data. This improves the efficiency of data export.

Description

Technical Field

[0001] This specification relates to the technical field of computer data processing, and particularly relates to a task execution method, apparatus, computing device, and storage medium. Background Art

[0002] With the development of technology, a large amount of data can be stored in a database, such as text data, image data, or sound data, etc. When users hope to extract value from the data, they often need to export a large amount of data from the database.

[0003] In some scenarios, users can export data from the database through a client. In related technologies, after a data export fails once, users need to re-export all the data again, which reduces the data export efficiency. Summary of the Invention

[0004] In view of this, the embodiments of this specification provide a task execution method, apparatus, computer device, and storage medium, which can improve the data export efficiency to a certain extent.

[0005] The embodiments of this specification provide a task execution method, which includes: executing a first export task including a plurality of first subtasks, where the first subtasks that fail in the first export task form a failure task set; executing a second export task, where the second export task at least includes second subtasks corresponding to the first subtasks in the failure task set; and merging the export data of the second export task with the export data of the first export task to form result data.

[0006] The embodiments of this specification provide an execution apparatus, including a first execution module, a second execution module, and a third execution module. The first execution module is configured to execute a first export task including a plurality of first subtasks; where the first subtasks that fail in the first export task form a failure task set, the second execution module is configured to execute a second export task; where the second export task at least includes second subtasks corresponding to the first subtasks in the failure task set; and the merging module is configured to merge the export data of the second export task with the export data of the first export task to form result data.

[0007] The embodiments of this specification provide a computer device, including a memory and a processor, where the memory stores a computer program, and the processor implements the method described in the foregoing embodiments when executing the computer program.

[0008] The embodiments of this specification provide a computer-readable storage medium, on which computer program instructions are stored, and when the program is executed by a processor, the method described in the foregoing embodiments is implemented.

[0009] The technical solution provided by the embodiments of this specification forms a failure task set for the tasks that fail to be exported. When exporting again, the data that failed to be exported is exported and merged with the data that was successfully exported previously to obtain the final data. By this technical means, it is possible to only export the previously failed data after the export fails, improving the efficiency of data export. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The drawings are used to provide a further understanding of the embodiments of the specification and constitute a part of the specification. Together with the following specific embodiments, they are used to explain this specification, but do not constitute a limitation to the embodiments of this specification. In the drawings:

[0011] Figure 1 is an interaction diagram of task execution in the scenario example provided by the embodiments of this specification;

[0012] Figure 2 is an application environment diagram of a task execution method provided by the embodiments of this specification;

[0013] Figure 3 is a flowchart of a task execution provided by the embodiments of this specification;

[0014] Figure 4 is a schematic diagram of the functional modules of a task execution device provided by the embodiments of this specification;

[0015] Figure 5 is a schematic diagram of the functions of an electronic device provided by the embodiments of this specification. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0016] In order to enable those skilled in the art of this technology to better understand the solution of this application, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the drawings in the embodiments of this specification. Obviously, the described embodiments are only a part of the embodiments of this specification, rather than all the embodiments. Based on the embodiments in this specification, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope protected by this application.

[0017] Before introducing the task execution method provided by this specification, the application scenarios of the embodiments of this specification will be introduced first. The embodiments of this specification can be applied to various data export occasions, such as exporting text data from a database, exporting audio data from a database, and so on.

[0018] Please refer to Figure 1, the embodiment of this specification provides an interaction scenario for task execution in a scenario instance. The user operates the client 101 to send a data download request 1. The server 102 receives the first task request from the client 101, such as a data export request, which requests to export all the medical clinical trial data of subject Zhang San. The data export request contains a subject ID of subject Zhang San. The server 102 can determine the corresponding subject as Zhang San based on the subject ID and determine that the data export request needs to export all the data related to subject Zhang San. The server 102 establishes a total task for exporting all the data of Zhang San. The server 102 finds that Zhang San has a total of 5 visits. The server 102 constructs 5 first subtasks for this total task, sets a status flag for each task, each first subtask corresponds to a visit respectively, and each first subtask is used to download the data of the corresponding visit. Each first subtask will output the corresponding visit data as a file, and finally form a file set from multiple files, for example, it can be packaged into a compressed package, and a download link 1 is provided and fed back to the corresponding client 101. The user operates the client to access the download link 1 and can obtain the corresponding download file. There may be a situation where 2 out of the 5 first subtasks fail to execute. The compressed package provided in the download link address for the client only contains files for 3 visits, missing files for 2 visits. The user operates the client 101 to send a data download request 2 to the server 102 again, and the user only needs to download the visit files that failed to download. After receiving this request, the server 102 analyzes based on the subject ID of Zhang San and finds that the status flags of 2 first subtasks indicate that the corresponding first subtasks failed to execute. The server 102 constructs second subtasks for the visits corresponding to the 2 first subtasks that failed to execute in the first export task. The server 102 executes the second subtasks and puts the corresponding files into the corresponding compressed package.

[0019] Please refer to Figure 2, an embodiment of this specification provides a task execution system. The task execution system may include a client 201 and a server 202. The client 201 communicates with the server 202 via a network. The client 201 sends a task execution instruction to the server 202 via the network. The server 202 receives the task execution instruction and executes the task. After the task execution is completed, a download link can be provided to the client 201 for sending. The client 201 may be an electronic device with network access capabilities. Specifically, for example, the client may be a desktop computer, a tablet computer, a laptop computer, a smart phone, a digital assistant, a smart wearable device, a shopping guide terminal, a television, a smart speaker, a microphone, etc. Among them, the smart wearable device includes but is not limited to a smart bracelet, a smart watch, smart glasses, a smart helmet, a smart necklace, etc. Alternatively, the client may also be software that can run on the above-mentioned electronic devices. The server 202 may be an electronic device with certain computing and processing capabilities. It may have a network communication module, a processor, a memory, etc. Of course, the above-mentioned server 202 may also refer to the software running on the electronic device. The above-mentioned server 202 may also be a distributed server, which may be a system with multiple processors, memories, network communication modules, etc. operating in coordination. Alternatively, the server 202 may also be a server cluster formed by several servers. Or, with the development of science and technology, the server 202 may also be a new technical means capable of implementing the corresponding functions of the embodiment of the specification. For example, it may be a new form of "server" based on quantum computing.

[0020] Please refer to Figure 3 , an embodiment of this specification provides a task execution method. The task execution method may include the following steps.

[0021] Step S301: Execute a first export task including multiple first subtasks, where the first subtasks that fail to execute in the first export task form a failure task set.

[0022] In this embodiment, after receiving a program instruction, the server responds to the task indicated by the program instruction. Specifically, for example, the server 202 receives a task request sent by the client 201 and determines a target data set for the corresponding request. The task request may carry, for example, the identifier of a subject, or the identifier of a visit, or the identifier of a hospital, all of which can be used as the target data set. The data associated therewith can be used as the content of the target data. The server generates an export task for the target data as the first subtask. By executing the first subtask, the data can be exported and provided to the terminal that issues the data request instruction.

[0023] The first export task can be used to export a specified target data set from a distributed storage system. The first export task can be divided into multiple first subtasks, and each first subtask is used to export a part of the data in the target data set. Specifically, each first subtask can have a separate execution thread, or multiple subtasks can share several threads for execution.

[0024] The first export task may mainly be for the export of clinical trial data. The clinical trial data may be stored in a distributed storage system. The clinical trial data can be divided into multiple levels according to the characteristics of the data itself. For example, at the hospital level, it can be divided into the subject level, and at the subject level, it can be divided into the visit level, etc., and refined downward iteratively. When the server constructs the first subtask, it divides the target data set into a certain level. The data included in this level is used to specify the corresponding first subtask. For example, when all the data of a certain subject is selected, each visit of this subject can correspond to a first subtask, and each first subtask is used to export the file corresponding to the visit and generate a corresponding file.

[0025] In this embodiment, there may be some cases where the first export task fails during execution. In some cases, the export conditions are not met when exporting data. For example, a form is being modified during export. Or, there is a field for which the data has not been entered yet. etc. The first subtasks that fail to execute can be formed into a failure task set. The failure task set may have a data structure that stores the corresponding identifiers of each failed first subtask internally, or it can also be without a specific data structure. The execution status data of each first subtask is recorded in the log, and the corresponding first subtask information can be obtained by reading the log later.

[0026] Step S302: Execute the second export task, where the second export task at least includes a second subtask corresponding to the first subtask in the failure task set.

[0027] In this embodiment, not all of the first subtasks included in the first export task may be successfully executed, that is, there are some first subtasks that fail to execute. At this time, the data corresponding to these failed first subtasks needs to be exported continuously. The second subtask for constructing the second export task is to export the data corresponding to the first subtask that fails to execute. For example, if the first subtask corresponds to a visit, the second subtask also corresponds to a visit. The first subtask that fails to execute and the second subtask are both to download the same data.

[0028] Step S303: Merge the export data of the second export task with the export data of the first export task to form result data.

[0029] In this embodiment, the exported data of the first export task forms a file according to the data exported by each first subtask. The exported data of the second export task also forms a file for each subtask according to the second export subtasks. The files formed by the first export task and the files formed by the second export task are combined to form a compressed package, which is convenient for the client to download and improves the download efficiency. For example, if the first export task exports and forms 100 files and the second export task forms 200 files, there are a total of 300 exported files. Instead of downloading 300 files, only one compressed package needs to be downloaded. The result data is the data successfully exported by the first export task and the data successfully exported by the second export task. These two parts of data are different, and the result data formed by merging is the target data set of the export task.

[0030] The embodiment provided in this specification can quickly and successfully export the target data. For the first time, a part of the data fails to be exported successfully. For the second time, this part of the failed data is exported again, and there is no need to export the data that was successfully exported for the first time, saving time. The data exported twice is combined to form a compressed package, reducing the storage space and saving resources.

[0031] In some embodiments, the first export task is used to export the target data set stored distributively; wherein, different first subtasks are used to export different data in the target data set.

[0032] In this embodiment, the server distributes and stores the target data according to, for example, each subject or each visit through distributed storage. When exporting, the target data corresponding to multiple first subtasks can be exported simultaneously, saving the export time. The target data set can be a data set stored in different regions through distributed storage. When executing the export task, different targets are exported simultaneously to form files corresponding to the first subtasks. For example, for subject Zhang San, there are approximately three visits, each visit is approximately 7 days, some data is recorded after 7 days, and there are some forms under the visit. When exporting, the target data corresponding to each first subtask can be one visit, forming a corresponding export file. The data sets corresponding to all the first subtasks constitute the entire target data. Each first subtask is successfully executed, and the corresponding part of the data is exported respectively, making the overall export efficiency relatively high, and avoiding different first subtasks from executing the same data export task, resulting in waste of resources and inaccurate data when all the data is exported.

[0033] In some embodiments, the first subtasks are respectively used to output an export file; the export files of the first subtasks collectively constitute the exported data of the first export task.

[0034] In this embodiment, an export file refers to data files corresponding to multiple first subtasks output by the multiple first subtasks. For example, the first export task is to export files of multiple subjects, and the data of each subject forms a file corresponding to each subject. Alternatively, the first export task is to export data of different visits of the same subject, and the data of different visits forms a file for each different visit. Among them, each export file can be extracted separately, or the exported files can be combined to form the export data of the first export task.

[0035] In some embodiments, the first subtask is provided with a status identifier; the failed task set includes the first subtasks whose status identifiers indicate failed execution.

[0036] In this embodiment, the task status identifier can be used to identify whether the task is completed. Each first subtask has a status identifier, and different values of the status identifier indicate whether the first subtask is successfully executed. For example, when the first subtask export is completed, the first subtask is marked with "1" indicating completion. When the first subtask export fails, the first subtask is marked with "0". All the first subtasks with the identifier "0" are combined to form the failed task set.

[0037] In some embodiments, the failed task set includes the first subtasks among the multiple first subtasks that do not output export files.

[0038] In this embodiment, by identifying the export files output by the execution of the first subtask, the export files without corresponding first subtasks are found. When the first subtask execution is completed, the number of export files will correspond to the number of successfully executed first subtasks. For example, if 200 subtasks are executed successfully, there will be output export files corresponding to 200 subtasks. If 10 tasks fail, then there are 10 subtasks that do not output the corresponding export files. The set of first subtasks that do not output export files forms the failed task set.

[0039] In some embodiments, the second subtask is used to export the same target data as the corresponding first subtask.

[0040] In this embodiment, the second subtask is to export the target data corresponding to the first subtask that fails to execute, and the export task contents of the two are the same. For example, the first subtask is to export the form for the second visit of subject 1 (medication record, urine routine, blood routine, etc. of subject 1), but it fails. The target data of the first subtask that fails to execute is still stored in the original storage area, and the target data corresponding to the first subtask in this area is the form for the second visit of subject 1 (medication record, urine routine, blood routine, etc. of subject 1). The data in the output file of the second subtask execution is still the form for the second visit of subject 1 (medication record, urine routine, blood routine, etc. of subject 1).

[0041] In some embodiments, the second subtask is respectively used to output an export file; the overall composition of the export files of the second subtask constitutes the export data of the second export task.

[0042] In this embodiment, the second export task is to export the data composed of the target data corresponding to the failure of the first subtask execution. Each second subtask generates a corresponding file after execution. After all second subtasks are executed, a number of files corresponding to the second subtasks are generated. Each file has the data output corresponding to the second export task. All the files form a compressed package of the export files of the second subtask, and the data combination in the files forms the export data corresponding to the second export task. For example, the second subtask is to export 50 subtasks. The second subtask executes 50 subtasks and succeeds, generating 50 files. These 50 files are combined into the export data of the second export task and form a compressed package.

[0043] In some embodiments, in the step of executing the second export task, it includes: obtaining the first dataset version number of the target dataset targeted by the first export task and the second dataset version number of the target dataset targeted by the second export task. In the case where the first dataset version number is different from the second dataset version number, multiple second subtasks of the second export task export all the data of the target dataset.

[0044] In this embodiment, by the difference in the data version numbers twice, the server concludes that the target data in the first subtask has been modified, and directly exporting the data corresponding to the second dataset version number is all the target data. The target data is encrypted using the hash algorithm. Even if two different data are slightly different, their corresponding hash values must be different. Therefore, as long as there is a slight difference in the data corresponding to the first export task and the second export task, the corresponding data fingerprints are different. Each first subtask corresponds to a data fingerprint. The target data of the first subtask is divided into different levels to form data fingerprints corresponding to different levels, and the data fingerprints of each level are combined into the data fingerprint of the upper level. For example, the data fingerprint of each form can form the data fingerprint of the corresponding visit.

[0045] In some embodiments, the first subtasks are respectively used to export target data, and the target data corresponding to each first subtask respectively has a first data version number; in the step of performing the second export task, it includes: obtaining the second data version number of the target data corresponding to the first subtask.

[0046] In this embodiment, the target data of the second export task can be quickly found by obtaining the second data version number. The second export task is to export the data corresponding to the failure of the first subtask to execute, and its data fingerprint remains unchanged. The data fingerprints of the target data corresponding to this part of the first subtask form the data fingerprints of the data corresponding to the second subtask, and these data fingerprints are obtained.

[0047] In some embodiments, a second subtask corresponding to the first subtask with the second data version number different from the first data version number is established; wherein, the second subtask is used to export the target data of the second data version number.

[0048] In this embodiment, by comparing the first data version number and the second data version number, the data fingerprint of the target data for which the first subtask is successfully executed is compared with the data fingerprint of the target data of the first subtask. The different parts of the data fingerprints are the target data fingerprints corresponding to the failure of the first subtask to execute. The data corresponding to these data fingerprints constitutes the target data corresponding to the second subtask.

[0049] In some embodiments, in the step of merging the export data of the second export task and the export data of the first export task to form result data, it includes: replacing the export file output by the corresponding first subtask with the export file output by the second subtask.

[0050] In this embodiment, by partially replacing files, re-exporting some files is avoided. After the first export task is completed, for example, a form in a subject visit is modified, or a form for a certain inspection is added for the subject. The second subtask is executed to output the corresponding target data after modification or the added partial data. The file output by executing the second subtask replaces the file output by executing the first export task correspondingly. For example, subject 1 undergoes other inspections, and the form recording the file's record traces records the other inspection situations of subject 1. At this time, the form recording the record traces has changed. In the second subtask, the form recording the record traces is output to replace the form recording the record traces corresponding to the export file output by the first subtask, and it is not necessary to export all the target data of the first subtask.

[0051] It should be noted that for the above method embodiments, for the sake of simple description, they are all represented as a series of combined actions. However, those skilled in the art should be familiar that this description is not limited by the described action sequence. Those skilled in the art should be familiar that the embodiments described in this specification are all preferred embodiments, and the actions involved are not necessarily required.

[0052] In some embodiments, this specification provides an execution device. Referring to Figure 4 As shown in the block diagram of an execution device, the device S400 includes: a first execution module S401, a second execution module S402, and a merging module S403.

[0053] The first execution module S401 is used to execute a first export task including a plurality of first subtasks; wherein, the first subtasks that fail to execute in the first export task form a failure task set.

[0054] The second execution module S402 is used to execute a second export task; wherein, the second export task includes at least second subtasks corresponding to the first subtasks in the failure task set;

[0055] The merging module S403 is used to merge the export data of the second export task with the export data of the first export task to form result data.

[0056] Each module in the above task execution device can be implemented in whole or in part by software, hardware, and their combination. The above modules can be embedded in the processor in the computer device in hardware form or be independent of it, or can be stored in the memory in the computer device in software form, so as to facilitate the processor to call and execute the operations corresponding to the above respective modules.

[0057] In one embodiment, a computer device is provided. The computer device can be a terminal, and its internal structure diagram can be as Figure 5As shown in the figure. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected via a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a carrier network, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a method for converting clinical trial data. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, a trackball, or a touchpad provided on the housing of the computer device, or an external keyboard, a touchpad, or a mouse, etc.

[0058] Those skilled in the art can understand that Figure 5 the structure shown in the figure is only a block diagram of some structures related to the solution of this application, and does not constitute a limitation on the computer device to which the solution of this application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine some components, or have different component arrangements.

[0059] In some embodiments, a computer device may be provided, including a memory and a processor. A computer program is stored in the memory, and when the processor executes the computer program, the method steps in the above embodiments are implemented.

[0060] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by the processor, the method steps in the above embodiments are implemented.

[0061] In some embodiments, a computer program product may be provided. The computer program product includes instructions that, when executed by a processor of a computer device, implement the method steps in the above embodiments. Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, storage, database, or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memories. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical memory, etc. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0062] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope recorded in this specification.

[0063] The above is only a part of the embodiments in this specification and is not intended to limit this specification. Any modification, equivalent replacement, etc. made within the spirit and principle of this specification shall be included within the scope of the disclosure of this specification.

Claims

1. A task execution method, characterized in that, The method includes: Performing a first export task including a plurality of first subtasks; wherein, the first subtasks that fail in the first export task form a set of failed tasks; the first subtasks are respectively used to export target data, and the target data corresponding to each first subtask respectively has a first data version number; Performing a second export task; wherein, the second export task at least includes second subtasks corresponding to the first subtasks in the set of failed tasks; the process of establishing the second export task includes: obtaining a second data version number of the target data corresponding to the first subtask, and establishing second subtasks corresponding to the first subtasks with the second data version number different from the first data version number, and the second subtasks are used to export the target data of the second data version number; Merging the export data of the second export task and the export data of the first export task to form result data; the process of forming the result data includes: replacing the export file output by the corresponding first subtask with the export file output by the second subtask.

2. The method according to claim 1, characterized in that, The first export task is used to export a target data set stored distributively; wherein, different first subtasks are used to export different data in the target data set.

3. The method according to claim 2, characterized in that, Each of the first subtasks is respectively used to output an export file; the overall export files of the first subtasks constitute the export data of the first export task.

4. The method according to claim 1, characterized in that, A status flag is set for each of the first subtasks; the set of failed tasks includes the first subtasks with the status flag indicating failure in execution.

5. The method according to claim 1, characterized in that, The set of failed tasks includes the first subtasks that do not output export files among the plurality of first subtasks.

6. The method according to claim 1, characterized in that, The second subtasks are used to export the same target data as the corresponding first subtasks.

7. The method according to claim 6, characterized in that, Each of the second subtasks is respectively used to output an export file; the overall export files of the second subtasks constitute the export data of the second export task.

8. The method according to claim 1, characterized in that, In the step of performing the second export task, it includes: Obtaining a first data set version number of the target data set targeted by the first export task and a second data set version number of the target data set targeted by the second export task; When the first data set version number is different from the second data set version number, the plurality of second subtasks of the second export task export all the data of the target data set.

9. A task execution device, characterized in that, It includes: A first execution module, configured to perform a first export task including a plurality of first subtasks; wherein, the first subtasks that fail in the first export task form a set of failed tasks; the first subtasks are respectively used to export target data, and the target data corresponding to each first subtask respectively has a first data version number; A second execution module, configured to execute a second export task; wherein, the second export task at least includes a second subtask corresponding to a first subtask in the failed task set; the process of establishing the second export task includes: obtaining a second data version number of target data corresponding to the first subtask, and establishing a second subtask corresponding to the first subtask for which the second data version number is different from the first data version number, where the second subtask is used to export the target data of the second data version number; A merging module, configured to merge the export data of the second export task and the export data of the first export task to form result data; the process of forming the result data includes: replacing the export file output by the corresponding first subtask with the export file output by the second subtask.

10. A computer device, comprising a memory and a processor, the memory storing a computer program, characterized in that, When the processor executes the computer program, the method according to any one of claims 1-8 is implemented.

11. A computer-readable storage medium, having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, the method according to any one of claims 1-8 is implemented.

Images