A task name query method and device, electronic equipment, and storage medium

Abstract

The application provides a task name query method and device, electronic equipment and medium, the method comprises the following steps: obtaining a to-be-queried instance ID and a project space corresponding to the to-be-queried instance ID in a MaxCompute computing platform; querying instance detail information corresponding to the to-be-queried instance ID by using the to-be-queried instance ID and the project space, and judging whether the instance detail information contains a scheduling node ID; if the instance detail information contains the scheduling node ID, extracting a task ID from the scheduling node ID, and querying a task name corresponding to the task ID in a DataWorks development platform. The application can use the to-be-queried instance ID and the corresponding project space to effectively locate the corresponding task ID and task name in the DataWorks platform, which can effectively avoid the manual inquiry mode in the related art, and thus can effectively improve the query positioning efficiency of abnormal instance tasks and the work efficiency of operation and maintenance personnel.

Description

Technical Field

[0001] This invention relates to the field of cloud computing, and in particular to a method, apparatus, electronic device, and storage medium for querying task names. Background Technology

[0002] MaxCompute is a big data computing service, while DataWorks is its accompanying visual development suite. In large data warehouse systems deploying both the MaxCompute computing platform and the DataWorks development platform, a large number of tasks are dispatched from DataWorks to MaxCompute for execution every minute. MaxCompute assigns a unique instance ID (InstanceId) to each instance task it processes. However, when operations personnel discover anomalies in certain instance tasks, they typically can only obtain the corresponding SQL operations after the instance task is submitted using the LogView query debugging tool in MaxCompute, and then inquire with other operations personnel about which DataWorks task initiated this SQL operation. Obviously, manual inquiry increases the burden on operations personnel and reduces task debugging efficiency. Furthermore, if there are many similar SQL operations, or if the intervals between SQL operations are long, operations personnel may even find it difficult to recall and determine the cause, thus preventing the investigation of abnormal tasks.

[0003] Therefore, how to effectively query the task name corresponding to the instance ID in MaxCompute in DataWorks is a technical problem that those skilled in the art need to address. Summary of the Invention

[0004] The purpose of this invention is to provide a method, apparatus, electronic device, and storage medium for querying task names. It can effectively locate the corresponding task ID and task name in the DataWorks platform using the instance ID to be queried and the corresponding project space, thereby effectively improving the efficiency of querying and locating abnormal instance tasks and the work efficiency of operation and maintenance personnel.

[0005] To solve the above-mentioned technical problems, the present invention provides a task name query method, including:

[0006] Obtain the instance ID to be queried and the project space corresponding to the instance ID from the MaxCompute computing platform;

[0007] Use the instance ID to be queried and the project space to query the instance details information corresponding to the instance ID to be queried;

[0008] Determine whether the instance details contain a scheduling node ID;

[0009] If the instance details include the scheduling node ID, then the task ID is extracted from the scheduling node ID, and the task name corresponding to the task ID is queried in the DataWorks development platform.

[0010] Optionally, querying the instance details information corresponding to the instance ID using the instance ID to be queried and the project space includes:

[0011] The query request encapsulates the instance ID to be queried and the project space into a query request, and sends the query request to the instance details query interface;

[0012] Receive the instance details information returned by the instance details query interface.

[0013] Optionally, extracting the task ID from the scheduling node ID includes:

[0014] The scheduling node ID is cleaned using a preset regular expression to obtain the task ID;

[0015] Verify the task ID, and after the task ID passes the verification, execute the step of querying the task name corresponding to the task ID in the database of the DataWorks development platform.

[0016] Optionally, verifying the task ID includes:

[0017] Determine whether the task ID contains only numbers;

[0018] If so, the task ID is deemed to have passed verification;

[0019] If not, the task ID is determined to have failed the verification.

[0020] Optionally, after querying the task name corresponding to the task ID in the DataWorks development platform, the method further includes:

[0021] Output the instance ID to be queried, the project space, and the task name.

[0022] Optionally, querying the task name corresponding to the task ID in the DataWorks development platform includes:

[0023] Query the task name corresponding to the task ID in the service component database of the DataWorks development platform;

[0024] If the task name is not found in the service component database, the task log is retrieved from the physical machine node that executes the task published by the DataWorks development platform, and the task name corresponding to the task ID is queried in the task log.

[0025] The present invention also provides a task name query device, comprising:

[0026] The acquisition module is used to obtain the ID of the instance to be queried and the project space corresponding to the ID of the instance to be queried in the MaxCompute computing platform;

[0027] The instance details query module is used to query the instance details information corresponding to the instance ID to be queried using the instance ID to be queried and the project space;

[0028] The judgment module is used to determine whether the instance details information contains a scheduling node ID;

[0029] The task name query module is used to extract the task ID from the scheduling node ID if the instance details information contains the scheduling node ID, and then query the task name corresponding to the task ID in the DataWorks development platform.

[0030] Optionally, the instance details query module includes:

[0031] The query request encapsulation submodule is used to encapsulate the instance ID to be queried and the project space into a query request, and send the query request to the instance details query interface;

[0032] The information receiving submodule is used to receive the instance details information returned by the instance details query interface.

[0033] The present invention also provides an electronic device, comprising:

[0034] Memory, used to store computer programs;

[0035] A processor is configured to implement the task name query method as described above when executing the computer program.

[0036] The present invention also provides a storage medium storing computer-executable instructions, which, when loaded and executed by a processor, implement the task name query method described above.

[0037] This invention provides a method for querying task names, comprising: obtaining a query instance ID and the project space corresponding to the query instance ID in the MaxCompute computing platform; querying instance details information corresponding to the query instance ID using the query instance ID and the project space, and determining whether the instance details information contains a scheduling node ID; if the instance details information contains the scheduling node ID, extracting a task ID from the scheduling node ID, and querying the task name corresponding to the task ID in the DataWorks development platform.

[0038] As can be seen, after obtaining the instance ID to be queried and its corresponding project space, this invention first uses these two pieces of information to query the instance details information corresponding to the instance ID to be queried, and determines whether the instance details information contains a scheduling node ID. If it contains a scheduling node ID, it means that the instance task corresponding to the instance ID to be queried is issued by the DataWorks development platform; otherwise, it is a temporary task. This can initially filter out instance tasks corresponding to DataWorks tasks in the MaxCompute computing platform. Furthermore, since the scheduling node ID contains the task ID of the DataWorks task, after confirming that the instance details information contains the scheduling node ID, the task ID can be directly extracted from the scheduling node ID. Then, the task ID can be used to directly query the corresponding task name in the DataWorks development platform, which can effectively query the task name corresponding to the instance ID, avoiding the manual querying method used in related technologies. This can effectively improve the efficiency of querying and locating abnormal instance tasks and the work efficiency of operation and maintenance personnel. This invention also provides a task name query device, electronic device, and storage medium, which have the above-mentioned beneficial effects. Attached Figure Description

[0039] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0040] Figure 1 A flowchart illustrating a task name query method provided in an embodiment of the present invention;

[0041] Figure 2 A flowchart illustrating another task name query method provided in an embodiment of the present invention;

[0042] Figure 3 This is a structural block diagram of a task name query device provided in an embodiment of the present invention. Detailed Implementation

[0043] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0044] In related technologies, when operations and maintenance personnel discover anomalies in certain instance tasks, they typically can only obtain the corresponding SQL operations using the LogView query debugging tool in MaxCompute after the instance task is submitted, and then inquire with other operations and maintenance personnel about which task in DataWorks initiated this SQL operation. Clearly, this manual inquiry method easily increases the burden on operations and maintenance personnel and reduces task debugging efficiency. Furthermore, if there are many similar SQL operations, or if the intervals between SQL operations are long, operations and maintenance personnel may even find it difficult to recall and determine the cause, thus preventing the investigation of abnormal tasks. In view of this, this invention provides a task name query method that can effectively locate the corresponding task ID and task name in the DataWorks platform using the instance ID to be queried and the corresponding project space, thereby effectively improving the efficiency of querying and locating abnormal instance tasks and the work efficiency of operations and maintenance personnel. Please refer to... Figure 1 , Figure 1 A flowchart of a task name query method provided in an embodiment of the present invention, the method may include:

[0045] S101. Obtain the instance ID to be queried and the project space corresponding to the instance ID in the MaxCompute computing platform.

[0046] In the MaxCompute computing platform, the project space is the basic organizational unit and the primary boundary for multi-user isolation and access control. The project space stores and manages instances generated by the MaxCompute computing platform, and each instance corresponds to a unique instance ID (InstanceId). Therefore, simply put, each project space manages multiple instance IDs. In subsequent steps, both the instance ID and the project space will be used to query information related to the instance ID. It should be noted that this embodiment of the invention does not limit the specific method for obtaining the instance ID to be queried and its associated project space; relevant MaxCompute technologies can be referenced.

[0047] S102. Use the instance ID to be queried and the project space to query the instance details information corresponding to the instance ID to be queried.

[0048] In related technologies, each instance ID corresponds to instance details, which record various information about the instance task, such as the instance ID, project space, start time, and end time. Of course, if an instance originates from a task submitted by DataWorks, the instance details also include parameters related to the scheduling node, such as the scheduling node ID (SKYNET_ID). In other words, this embodiment of the invention determines whether the instance corresponding to the instance details is related to a task on the DataWorks development platform based on whether the instance details contain a scheduling node ID. Furthermore, the scheduling node ID contains the task ID of the DataWorks task; therefore, after determining that the instance details contain a scheduling node ID, the task ID of the DataWorks task can be directly extracted from that node ID. It should be noted that this embodiment of the invention does not limit the specific content of the instance details or the specific form of the scheduling node ID; reference can be made to related technologies of MaxCompute.

[0049] Furthermore, when querying instance details, the instance details query interface (DescribeInstance) provided by MaxCompute can be used. Specifically, the instance ID to be queried and the project space can be encapsulated in the query request, and the request can be sent to the interface so that the interface can use the instance ID to be queried and its project space to query the corresponding instance details and return them.

[0050] In one possible scenario, retrieving instance details corresponding to the instance ID using the instance ID and project space could include:

[0051] Step 11: Encapsulate the instance ID and project space to be queried into a query request, and send the query request to the instance details query interface;

[0052] Step 12: Receive the instance details information returned by the instance details query interface.

[0053] It should be noted that the embodiments of the present invention do not limit the specific form of the query request, and the relevant technologies of the MaxCompute and DescribeInstance interfaces can be referred to.

[0054] S103. Determine whether the instance details information contains the scheduling node ID; if it does, proceed to step S104; if it does not, exit.

[0055] If the instance details include a scheduling node ID, it means that the instance ID to be queried is related to the DataWorks task, and subsequent operations can be performed; otherwise, it means that it is not related.

[0056] S104. If the instance details include a scheduling node ID, extract the task ID from the scheduling node ID and query the task name corresponding to the task ID in the DataWorks development platform.

[0057] After obtaining the scheduling node ID, the task ID can be extracted from it. Specifically, since the scheduling node ID contains a lot of information, string cleaning is required to remove irrelevant content in order to accurately extract the task ID. This embodiment of the invention does not limit the specific method of string cleaning; relevant content on data cleaning can be consulted, and the setting can be combined with the relative position of the task ID in the scheduling node ID. Specifically, for efficient cleaning, a regular expression for extracting the task ID can be pre-set, and the task ID can be directly extracted from the scheduling node ID using this expression. This embodiment of the invention also does not limit the specific form and content of the regular expression; relevant techniques on regular expressions can be consulted, and the setting can be combined with the relative position of the task ID in the scheduling node ID. Furthermore, to ensure the accuracy of the extracted task ID, string validation is required to ensure that the task ID does not contain any invalid characters.

[0058] In one possible scenario, extracting the task ID from the scheduling node ID could include:

[0059] Step 21: Clean the scheduling node IDs using a preset regular expression to obtain the task IDs;

[0060] Step 22: Verify the task ID, and after the task ID passes the verification, perform the step of querying the task name corresponding to the task ID in the database of the DataWorks development platform.

[0061] It should be noted that the embodiments of the present invention do not limit the specific method of verifying the task ID; the method is related to the character types that can be contained in the task ID. Since the task ID corresponding to a DataWorks task is usually a numeric string, it is only necessary to determine whether the task ID contains only numbers to determine whether the task ID meets the requirements. Of course, the string length of the task ID can also be verified. If the task ID of a DataWorks task may subsequently contain other types of characters, these additional character types can be added to the verification items.

[0062] In one possible scenario, verifying the task ID could include:

[0063] Step 31: Determine if the task ID contains only numbers; if yes, proceed to step 32; if no, proceed to step 33.

[0064] Step 32: Determine if the task ID passes verification;

[0065] Step 33: Determine that the task ID has failed verification.

[0066] Furthermore, this embodiment of the invention is not limited to the specific query location of the task name corresponding to the task ID in the DataWorks development platform. It can be searched either in the service component database (Phoenix) of the DataWorks development platform or in the physical machine node (Gateway) executing the task published by the DataWorks development platform, where the physical machine node stores the task logs of the DataWorks task. Considering the high efficiency of database queries, this embodiment of the invention will prioritize searching for the task name corresponding to the task ID in the service component database of the DataWorks development platform. Of course, if the service component database does not store the task name, the task logs can also be retrieved from the physical machine node, and the task ID can be matched in the task logs to obtain the corresponding task name.

[0067] In one possible scenario, querying the task name corresponding to the task ID in the DataWorks development platform will yield the following results:

[0068] Step 41: Query the task name corresponding to the task ID in the service component database of the DataWorks development platform.

[0069] Step 42: If the task name is not found in the service component database, retrieve the task log from the physical machine node that executed the task published by the DataWorks development platform, and query the task name corresponding to the task ID in the task log.

[0070] It should be noted that the embodiments of the present invention do not limit how to query the task name corresponding to the task ID in the service component database. For reference, please refer to the relevant technologies of DataWorks and Phoenix. The embodiments of the present invention also do not limit how to pull task logs from physical machine nodes and query the task name corresponding to the task ID in the task logs. For reference, please refer to the relevant technologies of DataWorks.

[0071] Finally, after obtaining the task name, the instance ID to be queried, the project space, and the task name can be output in a unified manner to facilitate the operation and maintenance personnel in locating and troubleshooting.

[0072] In one possible scenario, after querying the task name corresponding to the task ID in the DataWorks development platform, it may also include:

[0073] Step 51: Output the instance ID, project space, and task name to be queried.

[0074] Based on the above embodiments, after obtaining the instance ID to be queried and its corresponding project space, the present invention first uses these two pieces of information to query the instance details information corresponding to the instance ID to be queried, and determines whether the instance details information contains a scheduling node ID. If it contains a scheduling node ID, it means that the instance task corresponding to the instance ID to be queried is issued by the DataWorks development platform; otherwise, it is a temporary task. This can initially filter out the instance tasks corresponding to DataWorks tasks in the MaxCompute computing platform. Furthermore, since the scheduling node ID contains the task ID of the DataWorks task, after determining that the instance details information contains the scheduling node ID, the task ID can be directly extracted from the scheduling node ID. Then, the task ID can be used to directly query the corresponding task name in the DataWorks development platform. This can effectively query the task name corresponding to the instance ID, avoiding the manual query method used in related technologies, thereby effectively improving the efficiency of querying and locating abnormal instance tasks and the work efficiency of operation and maintenance personnel.

[0075] The following flowchart illustrates the method for querying the task name. Please refer to it. Figure 2 , Figure 2 A flowchart of another task name query method provided in an embodiment of the present invention, the process may include:

[0076] 1. Obtain the instance ID to be queried and the project space corresponding to the instance ID in the MaxCompute computing platform.

[0077] 2. Encapsulate the instance ID and project space to be queried into the query request, and send the query request to the instance details query interface.

[0078] 3. Receive instance details information returned by the instance details query interface.

[0079] 4. Determine whether the instance details contain the scheduling node ID; if it does, proceed to step 5; if it does not, exit.

[0080] 5. Clean the scheduling node ID using a preset regular expression to obtain the task ID.

[0081] 6. Verify the task ID, and after the task ID passes verification, query the task name corresponding to the task ID in the service component database of the DataWorks development platform.

[0082] 8. Determine if the task name is found; if yes, proceed to step 10; if no, proceed to step 9.

[0083] 9. Retrieve task logs from the physical machine nodes that execute tasks published by the DataWorks development platform, and query the task name corresponding to the task ID in the task logs.

[0084] 10. Output the instance ID, project space, and task name to be queried.

[0085] The following describes a task name query device, electronic device, and storage medium provided by an embodiment of the present invention. The task name query device, electronic device, and storage medium described below can be referred to in correspondence with the task name query method described above.

[0086] Please refer to Figure 3 , Figure 3 This is a structural block diagram of a task name query device provided in an embodiment of the present invention. The device may include:

[0087] The acquisition module 301 is used to obtain the instance ID to be queried and the project space corresponding to the instance ID in the MaxCompute computing platform;

[0088] The instance details query module 302 is used to query the instance details information corresponding to the instance ID to be queried using the instance ID to be queried and the project space;

[0089] The judgment module 303 is used to determine whether the instance details information contains a scheduling node ID;

[0090] The task name query module 304 is used to extract the task ID from the scheduling node ID if the instance details information includes the scheduling node ID, and then query the task name corresponding to the task ID in the DataWorks development platform.

[0091] Optionally, the instance details query module 302 may include:

[0092] The query request encapsulation submodule is used to encapsulate the instance ID and project space to be queried into a query request and send the query request to the instance details query interface;

[0093] The information receiving submodule is used to receive instance detail information returned by the instance detail query interface.

[0094] Optionally, the task name query module 304 may include:

[0095] The cleaning submodule is used to clean the scheduling node IDs using preset regular expressions to obtain task IDs;

[0096] The verification submodule is used to verify the task ID, and after the task ID passes verification, it performs the step of querying the task name corresponding to the task ID in the database of the DataWorks development platform.

[0097] Optionally, the verification submodule may include:

[0098] The judgment unit is used to determine whether the task ID contains only numbers;

[0099] The first processing unit is used to determine if the task ID passes the verification if so.

[0100] The second processing unit is used to determine if the task ID fails the verification if not.

[0101] Optionally, the device may further include:

[0102] The output module is used to output the instance ID, project space, and task name to be queried.

[0103] Optionally, the task name query module 304 may include:

[0104] The first query submodule is used to query the task name corresponding to the task ID in the service component database of the DataWorks development platform.

[0105] The second query submodule is used to retrieve task logs from the physical machine node executing the task published by the DataWorks development platform if the task name is not found in the service component database, and then query the task name corresponding to the task ID in the task logs.

[0106] This invention also provides an electronic device, comprising:

[0107] Memory, used to store computer programs;

[0108] A processor is used to implement the steps of the task name lookup method described above when executing a computer program.

[0109] Since the embodiments of the electronic device part correspond to the embodiments of the task name query method part, please refer to the description of the embodiments of the task name query method part for the embodiments of the electronic device part, and will not be repeated here.

[0110] This invention also provides a storage medium storing a computer program, which, when executed by a processor, implements the steps of the task name query method described in any of the above embodiments.

[0111] Since the embodiments of the storage medium section correspond to the embodiments of the task name query method section, please refer to the description of the embodiments of the task name query method section for the embodiments of the storage medium section, and will not be repeated here.

[0112] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to the method section.

[0113] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0114] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0115] The above provides a detailed description of the task name query method, apparatus, electronic device, and storage medium provided by the present invention. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The descriptions of the embodiments above are merely for the purpose of helping to understand the method and core ideas of the present invention. It should be noted that those skilled in the art can make various improvements and modifications to the present invention without departing from its principles, and these improvements and modifications also fall within the protection scope of the claims of the present invention.

Claims

1. A task name inquiry method characterized by comprising: The method comprises the following steps: obtaining an instance ID to be queried and a project space corresponding to the instance ID to be queried in a MaxCompute computing platform; querying instance detail information corresponding to the instance ID to be queried by using the instance ID to be queried and the project space; judging whether the instance detail information contains a scheduling node ID; if the instance detail information contains the scheduling node ID, determining that the instance corresponding to the instance ID to be queried originates from a task submitted by a DataWorks development platform, extracting a task ID from the scheduling node ID, and querying a task name corresponding to the task ID in the DataWorks development platform; the scheduling node ID contains a task ID of a DataWorks task; the step of extracting the task ID from the scheduling node ID comprises the following steps: cleaning the scheduling node ID by using a preset regular expression to obtain the task ID; verifying the task ID, and after the task ID passes the verification, performing the step of querying the task name corresponding to the task ID in a database of the DataWorks development platform; the step of verifying the task ID comprises the following steps: judging whether the task ID contains only numbers; if yes, determining that the task ID passes the verification; if no, determining that the task ID does not pass the verification.

2. The task name inquiry method according to claim 1, characterized by, the step of querying the instance detail information corresponding to the instance ID to be queried by using the instance ID to be queried and the project space comprises the following steps: encapsulating the instance ID to be queried and the project space into a query request, and sending the query request to an instance detail query interface; receiving the instance detail information returned by the instance detail query interface.

3. The task name inquiry method according to claim 1, characterized by, after querying the task name corresponding to the task ID in the DataWorks development platform, the method further comprises the following steps: outputting the instance ID to be queried, the project space and the task name.

4. The task name inquiry method according to any one of claims 1 to 3, characterized by, the step of querying the task name corresponding to the task ID in the DataWorks development platform comprises the following steps: querying the task name corresponding to the task ID in a service component database of the DataWorks development platform; if the task name is not queried in the service component database, pulling a task log from a physical machine node executing a task published by the DataWorks development platform, and querying the task name corresponding to the task ID in the task log.

5. A task name inquiry apparatus characterized by comprising: The method comprises the following steps: an obtaining module, configured to obtain an instance ID to be queried and a project space corresponding to the instance ID to be queried in a MaxCompute computing platform; an instance detail information query module, configured to query instance detail information corresponding to the instance ID to be queried by using the instance ID to be queried and the project space; a judging module, configured to judge whether the instance detail information contains a scheduling node ID; The task name query module is configured to: if the instance detail information contains the scheduling node ID, determine that the instance corresponding to the to-be-queried instance ID originates from a task submitted by a Dataworks development platform, extract a task ID from the scheduling node ID, and query a task name corresponding to the task ID in the DataWorks development platform; The scheduling node ID contains a task ID of a DataWorks task; The task name query module comprises: A cleaning submodule configured to clean the scheduling node ID by using a preset regular expression to obtain the task ID; A verification submodule configured to verify the task ID, and perform the step of querying the task name corresponding to the task ID in the database of the DataWorks development platform after the task ID passes the verification; The verification submodule comprises: A judgment unit configured to determine whether the task ID contains only numbers; A first processing unit configured to determine that the task ID passes the verification if the task ID contains only numbers; A second processing unit configured to determine that the task ID fails the verification if the task ID does not contain only numbers.

6. The task name query apparatus according to claim 5, wherein The instance detail information query module comprises: A query request packaging submodule configured to package the to-be-queried instance ID and the project space into a query request, and send the query request to an instance detail query interface; An information receiving submodule configured to receive the instance detail information returned by the instance detail query interface.

7. An electronic device, comprising: Comprise: A memory configured to store a computer program; A processor configured to implement the task name query method according to any one of claims 1 to 4 when executing the computer program.

8. A storage medium, characterized by The storage medium stores computer executable instructions, and the computer executable instructions are loaded and executed by the processor to implement the task name query method according to any one of claims 1 to 4.

Images