Task configuration method and device, electronic equipment and computer readable medium

Abstract

Embodiments of the present disclosure disclose a task configuration method and device, electronic equipment and a computer readable medium. A specific embodiment of the method comprises: in response to receiving a task creation instruction sent by a target user, displaying a task creation page; in response to detecting a first selection operation acting on a multi-type task page control, displaying a multi-type task configuration page; in response to detecting a second selection operation acting on a data warehouse task type in a task type selection box, displaying a data warehouse task configuration page; and in response to detecting a third selection operation acting on a task submission control, storing a task name input into a task name input box, a task queue name selected in a task queue selection box, a task priority selected in a task priority selection box and a task execution statement input into a task execution statement input box into a target database. The embodiment can simplify the steps of task configuration and improve upload efficiency.

Description

Technical Field

[0001] Embodiments of this disclosure relate to the field of computers, and more particularly to task configuration methods, apparatus, electronic devices, and computer-readable media. Background Technology

[0002] With the application of artificial intelligence technology in various industries, the demand for AI algorithms and models is growing exponentially. Currently, when creating and scheduling tasks in a cluster (e.g., Tasks in a Kubernetes distributed cluster), the common approach is to manually upload the task package to a designated storage location and then execute the task using a first-in, first-out (FIFO) method.

[0003] However, the above method presents the following technical problems:

[0004] First, tasks such as uploading and executing programs usually involve administrative permissions, the steps are repetitive and cumbersome, the uploading efficiency is low, and it is easy to cause information leakage.

[0005] Second, executing tasks in a first-in-first-out (FIFO) manner can lead to situations where less resource-intensive tasks, which are scheduled after some more resource-intensive tasks, cannot run in a timely manner, resulting in a waste of system resources.

[0006] The information disclosed in this background section is only intended to enhance the understanding of the background of the inventive concept, and therefore may contain information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0007] The summary portion of this disclosure is intended to provide a brief overview of the concepts, which will be described in detail in the detailed description portion that follows. This summary portion is not intended to identify key or essential features of the claimed technical solutions, nor is it intended to limit the scope of the claimed technical solutions.

[0008] Some embodiments of this disclosure provide task configuration methods, apparatuses, electronic devices, and computer-readable media to address one or more of the technical problems mentioned in the background section above.

[0009] In a first aspect, some embodiments of this disclosure provide a task configuration method, the method comprising: in response to receiving a task creation instruction sent by a target user, displaying a task creation page, wherein the task creation page displays at least one of the following controls: a multi-type task page control, a periodic task page control, and an associated task page control; in response to detecting a first selection operation performed on the multi-type task page control, displaying a multi-type task configuration page, wherein the multi-type task configuration page displays a task type selection box, the task type selection box including at least one of the following task types: a data warehouse task type, an object-oriented task type, and a distributed task type ...; For the second selection operation of the data warehouse task type in the task type selection box mentioned above, the data warehouse task configuration page is displayed. The data warehouse task configuration page displays a task submission control, a task name input box, a task queue selection box, a task priority selection box, and a task execution statement input box. In response to detecting the third selection operation acting on the task submission control, the task name entered into the task name input box, the task queue name selected in the task queue selection box, the task priority selected in the task priority selection box, and the task execution statement entered into the task execution statement input box are stored in the target database.

[0010] Secondly, some embodiments of this disclosure provide a task configuration apparatus, comprising: a first display unit configured to display a task creation page in response to receiving a task creation instruction sent by a target user, wherein the task creation page displays at least one of the following controls: a multi-type task page control, a periodic task page control, and an associated task page control; a second display unit configured to display a multi-type task configuration page in response to detecting a first selection operation performed on the multi-type task page control, wherein the multi-type task configuration page displays a task type selection box, the task type selection box including at least one of the following task types: a data warehouse task type, an object-oriented task type, and a distributed task type; and a third display unit. The system is configured to display a data warehouse task configuration page in response to a second selection operation applied to the task type selection box. This data warehouse task configuration page displays a task submission control, a task name input box, a task queue selection box, a task priority selection box, and a task execution statement input box. The storage unit is configured to store the task name entered into the task name input box, the task queue name selected in the task queue selection box, the task priority selected in the task priority selection box, and the task execution statement entered into the task execution statement input box in response to a third selection operation applied to the task submission control, in the target database.

[0011] Thirdly, some embodiments of this disclosure provide an electronic device, including: one or more processors; and a storage device having one or more programs stored thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any implementation of the first aspect above.

[0012] Fourthly, some embodiments of this disclosure provide a computer-readable medium having a computer program stored thereon, wherein the program, when executed by a processor, implements the method described in any of the implementations of the first aspect above.

[0013] The above embodiments of this disclosure have the following beneficial effects: the task configuration method of some embodiments of this disclosure simplifies the task upload steps, improves task upload efficiency, and reduces the possibility of information leakage. Specifically, the reason for low upload efficiency and easy information leakage is that tasks such as uploading and executing programs usually involve management permissions, the steps are repetitive and cumbersome, the upload efficiency is low, and information leakage is easy. Based on this, the task configuration method of some embodiments of this disclosure firstly displays a task creation page in response to receiving a task creation instruction sent by a target user. The task creation page displays at least one of the following controls: a multi-type task page control, a periodic task page control, and an associated task page control. Thus, tasks can be configured directly on the task creation page. Next, in response to detecting a first selection operation acting on the multi-type task page control, a multi-type task configuration page is displayed. The multi-type task configuration page displays a task type selection box, which includes at least one of the following task types: data warehouse task type, object-oriented task type, and distributed task type. Thus, a selection control is provided for configuring different types of tasks, which facilitates the quick configuration of different types of tasks. Then, in response to the detection of a second selection operation on the data warehouse task type in the task type selection box, the data warehouse task configuration page is displayed. This page displays a task submission control, as well as a task name input box, a task queue selection box, a task priority selection box, and a task execution statement input box. This allows for quick configuration of data warehouse task types within the data warehouse task configuration page. Finally, in response to the detection of a third selection operation on the task submission control, the task name entered in the task name input box, the task queue name selected in the task queue selection box, the task priority selected in the task priority selection box, and the task execution statement entered in the task execution statement input box are stored in the target database. This allows for direct task configuration and database upload directly from the task configuration page. This simplifies the task configuration process and improves upload efficiency. Furthermore, because task configuration can be completed directly through the configuration page, task uploads can be performed quickly, thus reducing the possibility of information leakage. Attached Figure Description

[0014] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and elements are not necessarily drawn to scale.

[0015] Figure 1This is a flowchart of some embodiments of the task configuration method according to this disclosure;

[0016] Figure 2 These are schematic diagrams illustrating the structure of some embodiments of the task configuration apparatus according to this disclosure;

[0017] Figure 3 This is a schematic diagram of the structure of an electronic device suitable for implementing some embodiments of the present disclosure. Detailed Implementation

[0018] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0019] It should also be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings. Unless otherwise specified, the embodiments and features described in this disclosure can be combined with each other.

[0020] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0021] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0022] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0023] This disclosure will now be described in detail with reference to the accompanying drawings and embodiments.

[0024] Figure 1 This is a flowchart of some embodiments of the task configuration method according to the present disclosure. A flowchart 100 of some embodiments of the task configuration method according to the present disclosure is shown. The task configuration method includes the following steps:

[0025] Step 101: In response to receiving a task creation instruction from the target user, display the task creation page.

[0026] In some embodiments, the execution entity of the task configuration method (e.g., a computing device) may display a task creation page in response to receiving a task creation instruction sent by a target user. The task creation page displays at least one of the following controls: a multi-type task page control, a periodic task page control, and an associated task page control. Here, the task creation instruction may refer to a command to create a task. Here, a task may refer to a Task in a Kubernetes distributed cluster. Here, the task creation page may refer to a page used to create different types of tasks. The multi-type task page control may be a page control used to configure multi-type tasks. Clicking the multi-type task page control will redirect to the multi-type task configuration page. Here, multi-type tasks may include tasks of types such as data warehouse task type, object-oriented task type, and distributed task type. Here, the data warehouse task type may refer to the Hive task type. The object-oriented task type may refer to the Python task type. The distributed task type may refer to the Spark task type. The periodic task page control may be a page control used to configure periodic tasks. Clicking the periodic task page control will redirect to the periodic task configuration page. The associated task page control may be a page control used to configure associated tasks. Clicking the related task page control will redirect you to the related task configuration page. Periodic tasks are tasks that execute at preset intervals. Related tasks can refer to multiple tasks that are related. For example, executing task A will necessarily execute task B.

[0027] Step 102: In response to detecting a first selection operation applied to the multi-type task page control, display the multi-type task configuration page.

[0028] In some embodiments, the aforementioned execution entity may display a multi-type task configuration page in response to detecting a first selection operation applied to the multi-type task page control. The multi-type task configuration page displays a task type selection box, which includes at least one of the following task types: data warehouse task type, object-oriented task type, and distributed task type. The first selection operation may include, but is not limited to, clicking, tossing, and sliding. The task type selection box can be used to select a task type. A data warehouse task type may refer to a Hive task type. An object-oriented task type may refer to a Python task type. A distributed task type may refer to a Spark task type.

[0029] Step 103: In response to detecting a second selection operation on the data warehouse task type in the task type selection box, the data warehouse task configuration page is displayed.

[0030] In some embodiments, the aforementioned executing entity may display a data warehouse task configuration page in response to detecting a second selection operation applied to the data warehouse task type in the task type selection box. The data warehouse task configuration page displays a task submission control, and also displays a task name input box, a task queue selection box, a task priority selection box, and a task execution statement input box. The second selection operation may include, but is not limited to, clicking, tossing, and sliding. The task submission control can be used to submit task information configured on the data warehouse task configuration page. Task information may include task name, task queue, task priority, and task execution statement. The task name input box can be an input box for entering the task name. The task queue selection box can be a selection box for selecting the task queue. The task priority selection box can be a selection box for selecting the task priority. The task execution statement input box can be an input box for entering the program statement for the task.

[0031] Step 104: In response to detecting a third selection operation applied to the task submission control, the task name entered into the task name input box, the task queue name selected in the task queue selection box, the task priority selected in the task priority selection box, and the task execution statement entered into the task execution statement input box are stored in the target database.

[0032] In some embodiments, the execution entity may, in response to detecting a third selection operation applied to the task submission control, store the task name entered into the task name input box, the task queue name selected in the task queue selection box, the task priority selected in the task priority selection box, and the task execution statement entered into the task execution statement input box in a target database. The third selection operation may include, but is not limited to, clicking, tossing, and sliding. Here, the task name entered into the task name input box, the task queue name selected in the task queue selection box, the task priority selected in the task priority selection box, and the task execution statement entered into the task execution statement input box can all be entered / selected by a technician. Here, the target database may refer to a pre-defined database used to store tasks to be executed.

[0033] Optionally, in response to detecting a fourth selection operation on the object-oriented task type in the task type selection box mentioned above, the object-oriented task configuration page is displayed.

[0034] In some embodiments, the execution entity may display an object-oriented task configuration page in response to detecting a fourth selection operation applied to the object-oriented task type in the task type selection box. This object-oriented task configuration page displays an object task submission control, and also displays an object task name input box, a priority selection box, and a task execution script input box. The fourth selection operation may include, but is not limited to, clicking, tossing, and sliding. The object task submission control can be used to submit object-oriented task information configured in the object-oriented task configuration page. The object-oriented task information may include the object task name, priority, and task execution script. The object task name input box can be an input box for entering the object task name. The priority selection box can be a selection box for selecting the task priority. The task execution script input box can be an input box for entering the task's execution script.

[0035] Optionally, in response to detecting a fifth selection operation applied to the object task submission control, the task name entered into the object task name input box, the priority selected in the priority selection box, and the task execution script entered into the task execution script input box are stored in the target database.

[0036] In some embodiments, the execution entity may, in response to detecting a fifth selection operation applied to the object task submission control, store the task name entered into the object task name input box, the priority selected in the priority selection box, and the task execution script entered into the task execution script input box into the target database. Here, the fifth selection operation may include, but is not limited to, clicking, flicking, and swiping.

[0037] Optionally, in response to detecting a sixth selection operation on the distributed task type in the task type selection box, the task resource file management interface is displayed.

[0038] In some embodiments, the aforementioned execution entity may display a task resource file management interface in response to detecting a sixth selection operation applied to the distributed task type in the task type selection box. This task resource file management interface displays a task resource file input box and a distributed task configuration control. The sixth selection operation may include, but is not limited to, clicking, tossing, and sliding. The task resource file input box can refer to an input box for entering task resource files. The distributed task configuration control can refer to a page control for configuring distributed tasks. That is, clicking the distributed task configuration control will redirect to the distributed task configuration page.

[0039] Optionally, in response to detecting an input operation of a task resource file into the task resource file input box and detecting a seventh selection operation on the distributed task configuration control, the distributed task configuration page is displayed.

[0040] In some embodiments, the execution entity may display a distributed task configuration page in response to detecting an input operation of a task resource file into the task resource file input box and a seventh selection operation applied to the distributed task configuration control. The distributed task configuration page displays a submit control, a distributed task name input box, a distributed task queue selection box, a distributed task priority selection box, and a task parameter input box. Here, the seventh selection operation may include, but is not limited to, clicking, tossing, and sliding. The submit control can be used to submit the distributed task information configured on the distributed task configuration page. The distributed task information may include the distributed task name, distributed task queue, distributed task priority, and task parameters. The distributed task name input box can be an input box for entering the name of the distributed task. The distributed task queue selection box can be a selection box for selecting a distributed task queue. The distributed task priority selection box can be a selection box for selecting a distributed task priority. The task parameter input box can be an input box for entering the parameters required to execute the task.

[0041] Optionally, in response to detecting an eighth selection operation performed on the submission control, the distributed task name entered into the distributed task name input box, the distributed task queue selected in the distributed task queue selection box, the distributed task priority selected in the distributed task priority selection box, and the task parameters entered into the task parameter input box are stored in the target database.

[0042] In some embodiments, the executing entity may, in response to detecting an eighth selection operation applied to the submission control, store the distributed task name entered into the distributed task name input box, the distributed task queue selected in the distributed task queue selection box, the distributed task priority selected in the distributed task priority selection box, and the task parameters entered into the task parameter input box into the target database. Here, the distributed task name is the filename of the task resource file. The eighth selection operation may include, but is not limited to, clicking, tossing, and sliding.

[0043] Optionally, in response to detecting a first click operation on the aforementioned periodic task page control, the periodic task configuration page is displayed.

[0044] In some embodiments, the execution entity may display a periodic task configuration page in response to detecting a first click operation applied to the periodic task page control. The periodic task configuration page displays a control for adding a periodic task. Here, the first click operation may refer to clicking a periodic task page control. The periodic task configuration page may refer to a page used for configuring periodic tasks. The control for adding a periodic task may refer to a control used for adding a periodic task.

[0045] Optionally, in response to detecting a second click operation on the newly added control of the aforementioned periodic task, the newly added periodic task is received and added to the periodic task queue.

[0046] In some embodiments, the execution entity may, in response to detecting a second click operation acting on the newly added control for the recurring task, receive user input for a new recurring task and add the new recurring task to the recurring task queue. Here, the second click operation may refer to clicking the newly added control for the recurring task. Here, the recurring task queue may be a queue used to store recurring tasks.

[0047] Optionally, in response to detecting a third click operation on the aforementioned associated task page control, the associated task configuration page is displayed, and the associated task group is displayed on the aforementioned associated task configuration page.

[0048] In some embodiments, the aforementioned execution entity may, in response to detecting a third click operation performed on the aforementioned associated task page control, display an associated task configuration page and, on the associated task configuration page, display an associated task group. The third click operation may refer to clicking the associated task page control.

[0049] Optionally, based on the task execution time corresponding to the associated tasks in the associated task group, the associated task group is sorted to obtain an associated task sequence, and the associated task sequence is stored in the target database.

[0050] In some embodiments, the executing entity can sort the associated task groups according to the execution time of the associated tasks within the associated task groups to obtain an associated task sequence, and store the associated task sequence in the target database. In practice, the executing entity can sort the associated task groups according to the chronological order of the execution time of the associated tasks within the associated task groups to obtain an associated task sequence, and store the associated task sequence in the target database.

[0051] Optionally, in response to receiving a task scheduling instruction sent by the target user, the remaining available task resources corresponding to the target user and the remaining available task resources locally are determined.

[0052] In some embodiments, the execution entity may, in response to receiving a task scheduling instruction sent by the target user, determine the remaining available task resources corresponding to the target user and the remaining available task resources locally. Here, the task scheduling instruction may refer to a command to execute a task. In practice, different task scheduling resources may be allocated to different users. In practice, the difference between the task scheduling resources allocated to the target user and the task scheduling resources currently used by the target user may be determined as the remaining available task resources. Here, the task scheduling resources currently used by the target user may refer to the resources occupied by the various tasks currently running and managed by the target user. The resources occupied by the tasks may be the memory occupied by the system when running tasks. Task scheduling resources may refer to the maximum memory allocated to a runnable task for a certain user. The remaining available task resources locally may refer to the memory resources that the execution entity can currently use to execute tasks.

[0053] Optionally, the user's actual available task resources are determined based on the aforementioned remaining available task resources and the aforementioned local remaining available task resources.

[0054] In some embodiments, the executing entity may determine the user's actual available task resources based on the remaining available task resources and the local remaining available task resources. In practice, in response to determining that the remaining available task resources are less than or equal to the local remaining available task resources, the remaining available task resources are determined as the user's actual available task resources. In response to determining that the remaining available task resources are greater than the local remaining available task resources, the local remaining available task resources are determined as the user's actual available task resources.

[0055] Optionally, tasks whose execution resources are less than or equal to the actual available task resources of the target user are selected from the task queue as tasks to be executed, thus obtaining a group of tasks to be executed.

[0056] In some embodiments, the execution entity may select tasks whose execution resources are less than or equal to the user's actual available task resources from the task queue corresponding to the target user as tasks to be executed, thus obtaining a group of tasks to be executed. Here, the task queue corresponding to the target user may refer to the various tasks to be executed that the target user has pre-created in the execution entity.

[0057] Optionally, a task scheduling operation can be performed based on the aforementioned group of tasks to be executed.

[0058] In some embodiments, the aforementioned execution entity can perform task scheduling operations based on the aforementioned group of tasks to be executed. The tasks to be executed in the aforementioned group include: submission time and task priority. A higher task priority indicates that the task should be executed as quickly as possible.

[0059] In practice, based on the aforementioned task group to be executed, the aforementioned executing entity can perform task scheduling operations through the following steps:

[0060] The first step is to sort the tasks in the task group in descending order of their priorities to obtain the first sequence of tasks to be executed. In practice, the executing entity can sort the tasks in the task group in descending order of their priorities to obtain the first sequence of tasks to be executed.

[0061] The second step involves sorting the tasks with the same priority within the first sequence of tasks to be executed, based on their submission times, to obtain the second sequence of tasks to be executed, which serves as the target sequence. In practice, for the tasks with the same priority within the first sequence of tasks to be executed, they can be sorted according to the order of their submission times.

[0062] Third, for each target execution task in the above target execution task sequence, perform the following processing steps:

[0063] The first sub-step involves performing a scheduling operation on the aforementioned target task. In practice, the execution entity can schedule the target task using a pre-defined thread for task execution.

[0064] The second sub-step involves updating the user's actual available task resources based on the resource usage of the target task, thereby generating updated user-available task resources. In practice, the difference between the user's actual available task resources and the resource usage of the target task can be used to determine the updated user-available task resources.

[0065] The third sub-step involves determining, in response to the discovery that there are candidate execution tasks in the candidate execution task sequence whose corresponding task resource usage is less than or equal to the aforementioned updated user's available task resources, that candidate execution task in the aforementioned candidate execution task sequence is identified as the first candidate execution task, thus obtaining the first candidate execution task group. Here, the aforementioned candidate execution task sequence is the target execution task sequence after removing the aforementioned target execution task.

[0066] The fourth sub-step involves selecting a certain number of first-option execution tasks from the aforementioned first-option execution task group as a second-option execution task group. The second-option execution task group must satisfy a target condition. This target condition could be: the total resources occupied by all tasks within the second-option execution task group are less than or equal to the available task resources for the updated user.

[0067] The fifth sub-step involves performing a task scheduling operation based on the second alternative task group mentioned above. In practice, the aforementioned execution entity can perform the task scheduling operation using pre-defined threads for task execution.

[0068] The relevant content in the second to fifth sub-steps described above constitutes an inventive point of this disclosure, thereby solving the second technical problem mentioned in the background art: "Executing tasks in a first-in, first-out (FIFO) manner causes tasks with lower resource consumption that are placed after tasks with higher resource consumption to fail to run in a timely manner, easily leading to a waste of system resources." Factors that easily lead to a waste of system resources are often as follows: Executing tasks in a FIFO manner causes tasks with lower resource consumption that are placed after tasks with higher resource consumption to fail to run in a timely manner, easily leading to a waste of system resources. If these factors are resolved, the waste of system resources can be reduced. To achieve this effect, firstly, based on the resource consumption of the target task, the actual available task resources for the user are updated to generate updated available task resources for the user. This determines the remaining available task resources for the current target user. Next, in response to determining that there are candidate tasks in the candidate task sequence whose resource consumption is less than or equal to the updated available task resources for the user, these candidate tasks are identified as the first candidate tasks, resulting in the first candidate task group. The aforementioned candidate task sequence is the target task sequence excluding the target task. This allows for the selection of resource-efficient tasks, ranked after tasks with high resource consumption, to avoid idle system resources. Then, a certain number of first candidate tasks are selected from the first candidate task group as the second candidate task group. This maximizes the utilization of the target user's currently available task resources, preventing resource-efficient tasks ranked after high-resource-consumption tasks from failing to run in a timely manner. Finally, task scheduling is performed based on the second candidate task group. This ensures the timely execution of resource-efficient tasks ranked after high-resource-consumption tasks, while maximizing the utilization of the target user's remaining available task resources and reducing system resource waste.

[0069] The above embodiments of this disclosure have the following beneficial effects: the task configuration method of some embodiments of this disclosure simplifies the task upload steps, improves task upload efficiency, and reduces the possibility of information leakage. Specifically, the reason for low upload efficiency and easy information leakage is that tasks such as uploading and executing programs usually involve management permissions, the steps are repetitive and cumbersome, the upload efficiency is low, and information leakage is easy. Based on this, the task configuration method of some embodiments of this disclosure firstly displays a task creation page in response to receiving a task creation instruction sent by a target user. The task creation page displays at least one of the following controls: a multi-type task page control, a periodic task page control, and an associated task page control. Thus, tasks can be configured directly on the task creation page. Next, in response to detecting a first selection operation acting on the multi-type task page control, a multi-type task configuration page is displayed. The multi-type task configuration page displays a task type selection box, which includes at least one of the following task types: data warehouse task type, object-oriented task type, and distributed task type. Thus, a selection control is provided for configuring different types of tasks, which facilitates the quick configuration of different types of tasks. Then, in response to the detection of a second selection operation on the data warehouse task type in the task type selection box, the data warehouse task configuration page is displayed. This page displays a task submission control, as well as a task name input box, a task queue selection box, a task priority selection box, and a task execution statement input box. This allows for quick configuration of data warehouse task types within the data warehouse task configuration page. Finally, in response to the detection of a third selection operation on the task submission control, the task name entered in the task name input box, the task queue name selected in the task queue selection box, the task priority selected in the task priority selection box, and the task execution statement entered in the task execution statement input box are stored in the target database. This allows for direct task configuration and database upload directly from the task configuration page. This simplifies the task configuration process and improves upload efficiency. Furthermore, because task configuration can be completed directly through the configuration page, task uploads can be performed quickly, thus reducing the possibility of information leakage.

[0070] Further reference Figure 2 As an implementation of the methods shown in the above figures, this disclosure provides some embodiments of a task configuration device, which are similar to... Figure 1 Corresponding to the method embodiments shown, the device can be specifically applied to various electronic devices.

[0071] like Figure 2As shown, the task configuration device 200 in some embodiments includes: a first display unit 201, a second display unit 202, a third display unit 203, and a storage unit 204. The first display unit 201 is configured to display a task creation page in response to receiving a task creation instruction sent by a target user. The task creation page displays at least one of the following controls: a multi-type task page control, a periodic task page control, and an associated task page control. The second display unit 202 is configured to display a multi-type task configuration page in response to detecting a first selection operation applied to the multi-type task page control. The multi-type task configuration page displays a task type selection box, which includes at least one of the following task types: a data warehouse task type, an object-oriented task type, and a distributed task type. The third display unit 203 is configured to display a multi-type task configuration page in response to detecting a first selection operation applied to the multi-type task page control. For the second selection operation of the data warehouse task type in the task type selection box mentioned above, the data warehouse task configuration page is displayed. The data warehouse task configuration page displays a task submission control, a task name input box, a task queue selection box, a task priority selection box, and a task execution statement input box. The storage unit 204 is configured to, in response to detecting a third selection operation applied to the task submission control, store the task name entered into the task name input box, the task queue name selected in the task queue selection box, the task priority selected in the task priority selection box, and the task execution statement entered into the task execution statement input box into the target database.

[0072] It is understandable that the units described in the device 200 are related to the reference. Figure 1 The steps in the described method correspond to each other. Therefore, the operations, features, and beneficial effects described above for the method also apply to the device 200 and the units contained therein, and will not be repeated here.

[0073] The following is for reference. Figure 3 This document illustrates a schematic diagram of an electronic device 300 (e.g., a computing device) suitable for implementing some embodiments of the present disclosure. The electronic devices in some embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 3 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments of this disclosure.

[0074] like Figure 3As shown, the electronic device 300 may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 301, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 302 or a program loaded from a storage device 308 into a random access memory (RAM) 303. The RAM 303 also stores various programs and data required for the operation of the electronic device 300. The processing unit 301, ROM 302, and RAM 303 are interconnected via a bus 304. An input / output (I / O) interface 305 is also connected to the bus 304.

[0075] Typically, the following devices can be connected to I / O interface 305: input devices 306 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 307 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 308 including, for example, magnetic tapes, hard disks, etc.; and communication devices 309. Communication device 309 allows electronic device 300 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 3 An electronic device 300 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively. Figure 3 Each box shown can represent a device or multiple devices as needed.

[0076] In particular, according to some embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, some embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 309, or installed from a storage device 308, or installed from a ROM 302. When the computer program is executed by the processing device 301, it performs the functions defined in the methods of some embodiments of this disclosure.

[0077] It should be noted that, in some embodiments of this disclosure, the computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In some embodiments of this disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In some embodiments of this disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0078] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0079] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device. The aforementioned computer-readable medium carries one or more programs that, when executed by the electronic device, cause the electronic device to: in response to receiving a task creation instruction sent by a target user, display a task creation page, wherein the task creation page displays at least one of the following controls: a multi-type task page control, a periodic task page control, and an associated task page control; in response to detecting a first selection operation performed on the aforementioned multi-type task page control, display a multi-type task configuration page, wherein the multi-type task configuration page displays a task type selection box, the task type selection box including at least one of the following task types: a data warehouse task type, an object-oriented task type, and a distributed task type. In response to detecting a second selection operation on the data warehouse task type in the task type selection box, a data warehouse task configuration page is displayed. This page displays a task submission control, a task name input box, a task queue selection box, a task priority selection box, and a task execution statement input box. In response to detecting a third selection operation on the task submission control, the task name entered in the task name input box, the task queue name selected in the task queue selection box, the task priority selected in the task priority selection box, and the task execution statement entered in the task execution statement input box are stored in the target database.

[0080] Computer program code for performing operations of some embodiments of this disclosure can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0081] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0082] The units described in some embodiments of this disclosure can be implemented in software or hardware. The described units can also be housed in a processor; for example, a processor may be described as including a first display unit, a second display unit, a third display unit, and a storage unit. The names of these units do not necessarily limit the specific unit itself; for example, the first display unit may also be described as "a unit that displays a task creation page in response to receiving a task creation instruction sent by a target user."

[0083] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0084] The above description is merely a selection of preferred embodiments of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in the embodiments of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described inventive concept. For example, technical solutions formed by substituting the above-described features with (but not limited to) technical features with similar functions disclosed in the embodiments of this disclosure.

Claims

1. A task configuration method, comprising: In response to receiving a task creation instruction from a target user, a task creation page is displayed, wherein the task creation page displays at least one of the following controls: multi-type task page control, periodic task page control, and associated task page control; In response to detecting a first selection operation applied to the multi-type task page control, a multi-type task configuration page is displayed, wherein the multi-type task configuration page displays a task type selection box, and the task type selection box includes at least one of the following task types: data warehouse task type, object-oriented task type, and distributed task type; In response to detecting a second selection operation on the data warehouse task type in the task type selection box, a data warehouse task configuration page is displayed. The data warehouse task configuration page displays a task submission control, and also displays a task name input box, a task queue selection box, a task priority selection box, and a task execution statement input box. The task execution statement input box is an input box used to input program statements for the task. In response to detecting a third selection operation applied to the task submission control, the task name entered into the task name input box, the task queue name selected in the task queue selection box, the task priority selected in the task priority selection box, and the task execution statement entered into the task execution statement input box are stored in the target database, wherein the target database is a database used to store tasks to be executed; Select tasks whose corresponding task execution resources are less than or equal to the user's actual available task resources from the task queue corresponding to the target user as tasks to be executed, thus obtaining a group of tasks to be executed. The task queue corresponding to the target user refers to each task to be executed that the target user has created in advance. According to the group of tasks to be executed, a task scheduling operation is performed, wherein the tasks to be executed in the group of tasks to be executed include: submission time and task priority; Based on the task priorities included in the task group to be executed, the task group to be executed is sorted in descending order to obtain the first sequence of tasks to be executed; Based on the submission time included in the first sequence of tasks to be executed, sort the first tasks to be executed that have the same priority in the first sequence of tasks to be executed to obtain the second sequence of tasks to be executed as the target sequence of tasks to be executed. Perform a scheduling operation for each target execution task in the target execution task sequence; Based on the resource consumption of the task corresponding to the target execution task, the actual available task resources of the user are updated to obtain the updated available task resources of the user. In response to determining that there is a candidate execution task in the candidate execution task sequence whose corresponding task resource usage is less than or equal to the available task resources of the updated user, the candidate execution task in the candidate execution task sequence whose corresponding task resource usage is less than or equal to the available task resources of the updated user is determined as the first candidate execution task, and a first candidate execution task group is obtained, wherein the candidate execution task sequence is the target execution task sequence after removing the target execution task; A certain number of first candidate tasks are selected from the first candidate task group as the second candidate task group to obtain the second candidate task group; Perform task scheduling operations according to the second alternative task group.

2. The method according to claim 1, wherein, The method further includes: In response to detecting a fourth selection operation on the object-oriented task type in the task type selection box, an object-oriented task configuration page is displayed, wherein the object-oriented task configuration page displays an object task submission control, and the object task name input box, a priority selection box, and a task execution script input box; In response to detecting a fifth selection operation applied to the object task submission control, the task name entered into the object task name input box, the priority selected in the priority selection box, and the task execution script entered into the task execution script input box are stored in the target database.

3. The method according to claim 1, wherein, The method further includes: In response to detecting a sixth selection operation on the distributed task type in the task type selection box, the task resource file management interface is displayed, wherein the task resource file management interface displays a task resource file input box and a distributed task configuration control; In response to the detection of an input operation of a task resource file into the task resource file input box, and the detection of a seventh selection operation on the distributed task configuration control, a distributed task configuration page is displayed, wherein the distributed task configuration page displays a submit control, a distributed task name input box, a distributed task queue selection box, a distributed task priority selection box, and a task parameter input box; In response to detecting an eighth selection operation applied to the submission control, the distributed task name entered into the distributed task name input box, the distributed task queue selected in the distributed task queue selection box, the distributed task priority selected in the distributed task priority selection box, and the task parameters entered into the task parameter input box are stored in the target database, wherein the distributed task name is the file name of the task resource file.

4. A task configuration device, comprising: The first display unit is configured to display a task creation page in response to receiving a task creation instruction sent by a target user, wherein the task creation page displays at least one of the following controls: multi-type task page control, periodic task page control, and associated task page control; The second display unit is configured to display a multi-type task configuration page in response to detecting a first selection operation applied to the multi-type task page control, wherein the multi-type task configuration page displays a task type selection box, and the task type selection box includes at least one of the following task types: data warehouse task type, object-oriented task type, and distributed task type. The third display unit is configured to display a data warehouse task configuration page in response to detecting a second selection operation on the data warehouse task type in the task type selection box. The data warehouse task configuration page displays a task submission control, and also displays a task name input box, a task queue selection box, a task priority selection box, and a task execution statement input box. The storage unit is configured to, in response to detecting a third selection operation performed on the task submission control, store the task name entered into the task name input box, the task queue name selected in the task queue selection box, the task priority selected in the task priority selection box, and the task execution statement entered into the task execution statement input box into the target database. The first selection unit is configured to select tasks whose corresponding task execution resources are less than or equal to the user's actual available task resources from the task queue corresponding to the target user as tasks to be executed, thereby obtaining a group of tasks to be executed. The task queue corresponding to the target user refers to each task to be executed that the target user has created in advance. The first scheduling unit is configured to perform a task scheduling operation based on the task group to be executed, wherein the tasks to be executed in the task group include: submission time and task priority; The sorting unit is configured to sort the task group to be executed in descending order according to the task priority of the task group to be executed, to obtain a first task sequence to be executed; and to sort the first tasks to be executed with the same task priority in the first task sequence according to the submission time of the first task sequence to obtain a second task sequence to be executed as the target task sequence to be executed. The second scheduling unit is configured to perform a scheduling operation for each target execution task in the target execution task sequence; The resource update unit is configured to update the user's actual available task resources based on the task resources occupied by the target execution task, thereby obtaining updated user available task resources. The second selection unit is configured to, in response to determining that there are candidate execution tasks in the candidate execution task sequence whose corresponding task resource usage is less than or equal to the available task resources of the updated user, determine the candidate execution tasks in the candidate execution task sequence whose corresponding task resource usage is less than or equal to the available task resources of the updated user as first candidate execution tasks, thereby obtaining a first candidate execution task group, wherein the candidate execution task sequence is a target execution task sequence excluding the target execution task; and select a certain number of first candidate execution tasks from the first candidate execution task group as a second candidate execution task group, thereby obtaining a second candidate execution task group; The third scheduling unit is configured to perform task scheduling operations based on the second alternative task group.

5. An electronic device, comprising: One or more processors; A storage device on which one or more programs are stored; When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-3.

6. A computer-readable medium having a computer program stored thereon, wherein, When the program is executed by the processor, it implements the method as described in any one of claims 1-3.

Images