CN113535352B - Test method for realizing automatic batch running based on blood relationship generated by scheduling configuration - Google Patents
Test method for realizing automatic batch running based on blood relationship generated by scheduling configuration Download PDFInfo
- Publication number
- CN113535352B CN113535352B CN202110716454.9A CN202110716454A CN113535352B CN 113535352 B CN113535352 B CN 113535352B CN 202110716454 A CN202110716454 A CN 202110716454A CN 113535352 B CN113535352 B CN 113535352B
- Authority
- CN
- China
- Prior art keywords
- running
- batch
- scheduling configuration
- blood relationship
- program
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3664—Environments for testing or debugging software
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
- G06F9/5038—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention belongs to the field of software development and software testing, and particularly relates to a testing method for realizing automatic batch running based on a blood relationship generated by scheduling configuration, aiming at solving the problems of long batch running time, complex operation and low efficiency in the test process in the prior art; the invention solves the problems by adopting the following technical scheme: acquiring actual scheduling configuration content of a current production environment; acquiring configuration change frequency according to the online frequency; determining a synchronous frequency according to the configuration change frequency; synchronizing the production scheduling configuration content to a test environment according to the configuration synchronization frequency; generating a blood relationship according to the synchronized scheduling configuration content; packaging an automatic batch running program according to the blood relationship; calling the end program to initiate automatic batch running program execution; the package calling of the batch running program can support the calling at any time and remove the triggering time limit. And the calling mode is simple and unique, the running batch execution complexity is reduced, flexible running batch is finally realized, and running batch is completed in minimum time.
Description
Technical Field
The invention belongs to the field of software development and software testing, and particularly relates to a testing method for realizing automatic batch running based on blood relationship generation based on scheduling configuration.
Background
Enterprises build big data systems that utilize big data for analysis decisions. The data warehouse is built firstly and is used for summarizing a plurality of data source data, and hierarchical ETL processing is carried out, so that target data are finally obtained and used in various business scenes.
The ETL processing often involves dependency relationships, and the input of the dependency in the data processing process is the corresponding blood edge, so that all blood edge relationships are formed through dependency among layers or dependency of the same layer.
Because of the complicated dependency of blood edges, the program execution needs to be executed according to the dependency sequence, so that the task configuration needs to be uniformly carried out by a dispatching system, and the task execution is uniformly allocated by the dispatching system.
The bottom task execution mode of the existing dispatching system is mostly time-triggered, the time-triggered test is limited in the test process, the test cannot be supported at any time, and if the test is temporarily performed, all task trigger time needs to be manually modified. The test process has long batch running time, complex operation and low efficiency.
Disclosure of Invention
The invention provides a test method for realizing automatic batch running based on a blood relationship generated by scheduling configuration, which aims to solve the problems of long batch running time, complex operation and low efficiency in the test process in the prior art.
In order to achieve the above purpose, the present invention provides the following technical solutions:
a test method for realizing automatic running batch based on generating blood relationship by scheduling configuration comprises the following steps:
step 1: acquiring actual scheduling configuration content of a current production environment;
step 2: acquiring configuration change frequency according to the online frequency; determining a synchronous frequency according to the configuration change frequency;
step 3: synchronizing the production scheduling configuration content to a test environment according to the configuration synchronization frequency;
step 4: generating a blood relationship according to the synchronized scheduling configuration content in the step 3;
step 5: packaging an automatic batch running program according to the blood relationship;
step 6: calling the end program to initiate automatic batch running program execution;
step 7: executing test check on the result after batch running;
step 8: summarizing the execution result and the problem repairing result of the step 7, and writing a quality report.
Compared with the prior art, the invention has the beneficial effects that: 1. by synchronizing the production scheduling configuration to the test environment, the scheduling configuration is guaranteed to be updated timely and the complete effectiveness of the scheduling configuration is guaranteed.
2. By configuring the generated blood relationship, the minimum and the smallest running batch program set can be obtained according to the requirement for the target file, and the running batch program set is not missed or repeated.
3. The package calling of the batch running program can support the calling at any time and remove the triggering time limit. And the calling mode is simple and unique, the running batch execution complexity is reduced, flexible running batch is finally realized, and running batch is completed in minimum time.
4. The concurrency number can be flexibly adjusted by encapsulating and calling the running batch program, the CPU is fully utilized, and the running batch execution efficiency is improved.
5. The running execution process can be simplified and the running complexity can be reduced by the same call of the calling end program.
Detailed Description
The technical solutions of the embodiments of the present invention will be clearly and completely described below, and it is obvious that the described embodiments are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The preferred embodiments of the present invention will be described in detail below.
A test method for realizing automatic running batch based on generating blood relationship by scheduling configuration comprises the following steps:
step 1: acquiring actual scheduling configuration content of a current production environment; selecting a data synchronization mode according to a storage form of the actual scheduling configuration content;
step 2: acquiring configuration change frequency according to the online frequency; determining a synchronous frequency according to the configuration change frequency; the synchronous change frequency is higher than the configuration change frequency so as to ensure that the configuration change can be synchronized to the detection environment in time; the synchronization time is later than the change time, so that the synchronization time is prevented from being changed in advance; for example: the configuration frequency is changed to Monday and Monday, and the synchronous configuration frequency can be changed to Monday and Monday.
Step 3: synchronizing the production scheduling configuration content to a test environment according to the configuration synchronization frequency;
the step 3 comprises the following steps of 3.1: determining a test environment scheduling configuration storage position;
step 3.2: configuring a timing synchronization task according to the synchronization frequency;
step 3.3: timing the synchronous task to run to the point for execution, and triggering the synchronous action to run to the point for execution;
step 3.4: detecting whether the configuration content of the test environment is the same as that of the generation environment, if not, continuing to execute the synchronous operation in the step 3; if the two are the same, executing the step 4.
Step 4: generating a blood relationship according to the synchronized scheduling configuration content in the step 3;
the generation of the blood relationship in the step 4 comprises the following steps:
step 4.1: reading the content of all scheduling configurations; reading all configuration contents, namely, in a dispatching system, reading all the latest synchronized configurations, including the contents of new dispatching configuration and the contents of old dispatching configuration;
step 4.2: determining a unique attribute of the task;
step 4.3: determining unique attributes of all target tasks of the tested program;
step 4.4: extracting unique attributes of the front task according to the unique attributes of each target task;
step 4.5: continuously extracting the unique pre-task attribute of the unique pre-task attribute in the step 4.4;
step 4.6: circularly executing the step 4.5; extracting all unique task attributes of the bottommost layer;
step 4.7: arranging all the extracted task unique attributes in reverse order according to the extraction sequence, and obtaining the blood relationship of each target task;
step 4.8: traversing all the unique attributes of the target tasks in the step 4.3, and sequentially executing the steps 4.4 to 4.7; obtaining the blood relationship of all target tasks;
step 4.9: aiming at the blood relationship of all target tasks, if the same dependency relationship exists, merging is carried out, and after merging, reservation is carried out; if the same-layer dependency relationship exists, the same-layer dependency separation is required.
Step 5: packaging an automatic batch running program according to the blood relationship;
said step 5 comprises the steps of: step 5.1: obtaining running batch programs to be executed according to one-to-one mapping relations among different task attributes; the different task attributes comprise a task number, a task name and a task execution program; the step 5.1 is understood to be a one-to-one mapping relationship between task numbers, task names and task executions according to the one-to-one mapping relationship between task attributes.
Step 5.2: determining a program language based on the program name suffix of the running program to be executed, which is obtained in the step 5.1, so as to determine a running program execution command;
step 5.3: and according to the blood margin dependency relationship sequence, each running batch program execution command is packaged into different files in a layered manner.
Step 6: calling the end program to initiate automatic batch running program execution;
the step 6 comprises the following steps: step 6.1: determining a calling end program code language;
step 6.2: determining the function to be realized by the calling end program based on the file content packaged in the step 5.3; the file content packaged in the step 5.3 is a batch command; the calling end program supports a starting batch command; meanwhile, in order to realize the personalized batch running function, other configuration parameters such as concurrency parameters for adjusting the CPU utilization rate, such as date parameters for determining batch running date, can be designed in the batch running command.
According to the step 4.9, the requirement on the same-layer dependency relationship is implemented on the same-layer dependency separation; according to the step 5.3, according to the blood edge dependency relationship sequence, each running batch program execution command is packaged into different files in a layering manner; preferably, in step 6.2, the processing of the run-batch program belonging to the same layer but without dependency is involved; the invention aims at running batch programs which are on the same layer and have no dependency relationship with each other, and can be executed by concurrency, so that the execution time is reduced, and the efficiency is improved.
Step 6.3: executing the batch running program according to the calling end program determined in the step 6.2 and the running mode of the calling end program;
step 6.4: if the batch running process is executed in error, positioning and correcting error reasons;
step 6.5: evaluating the concurrency number according to the resources and the consumed time and adjusting the concurrency number; the CPU utilization rate is maximized, the minimum time is used, and the maximum batch is run out.
Step 7: executing test check on the result after batch running;
the step 7 comprises the following steps: step 7.1: writing a test case;
step 7.2: after the batch running is completed in the step 6, executing test checking on the result after the batch running according to the writing content of the test case, and marking whether the test case passes or not;
step 7.3: and 7.2, positioning the problem reasons if the test check fails, and performing bug classification according to the problem influence range and the importance.
Step 8: summarizing the execution result and the problem repairing result of the step 7, and writing a quality report.
The explanation about the unique attribute in step 4 is as follows: the unique attribute represents an attribute that does not produce duplication; for example, the unique attribute adopts a task number, and the generation of the blood relationship in the corresponding step 4 comprises the following steps:
step 4.1: reading the content of all scheduling configurations;
step 4.2: determining the unique attribute of the task as a task number;
step 4.3: determining all target task numbers of the tested program;
step 4.4: extracting a front task number according to each target task number;
step 4.5: continuously extracting the prepositive task number of the prepositive task number in the step 4.4;
step 4.6: circularly executing the step 4.5; extracting all task numbers of the bottommost layer;
step 4.7: all the extracted task numbers are arranged in reverse order according to the extraction sequence, and the blood relationship of each target task can be obtained;
step 4.8: traversing all target task numbers in the step 4.3, and sequentially executing the steps 4.4 to 4.7; obtaining the blood relationship of all target tasks;
step 4.9: aiming at the blood relationship of all target tasks, if the same dependency relationship exists, merging is carried out, and after merging, reservation is carried out; if the same-layer dependency relationship exists, the same-layer dependency separation is required.
Of course, the task number is not limited to the present invention, and other non-duplicate attributes may be used as the unique attribute.
It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein.
Furthermore, it should be understood that although the present disclosure describes embodiments, not every embodiment is provided with a separate embodiment, and that this description is provided for clarity only, and that the disclosure is not limited to the embodiments described in detail below, and that the embodiments described in the examples may be combined as appropriate to form other embodiments that will be apparent to those skilled in the art.
Claims (8)
1. A test method for realizing automatic batch running based on a blood relationship generated by scheduling configuration is characterized in that: the method comprises the following steps:
step 1: acquiring actual scheduling configuration content of a current production environment;
step 2: acquiring configuration change frequency according to the online frequency; determining a synchronous frequency according to the configuration change frequency;
step 3: synchronizing the production scheduling configuration content to a test environment according to the configuration synchronization frequency;
step 4: generating a blood relationship according to the synchronized scheduling configuration content in the step 3;
step 5: packaging an automatic batch running program according to the blood relationship;
step 6: calling the end program to initiate automatic batch running program execution;
step 7: executing test check on the result after batch running;
step 8: summarizing the execution result and the problem repairing result of the step 7, and writing a quality report;
the generation of the blood relationship in the step 4 comprises the following steps:
step 4.1: reading the content of all scheduling configurations;
step 4.2: determining a unique attribute of the task;
step 4.3: determining unique attributes of all target tasks of the tested program;
step 4.4: extracting unique attributes of the front task according to the unique attributes of each target task;
step 4.5: continuously extracting the unique pre-task attribute of the unique pre-task attribute in the step 4.4;
step 4.6: circularly executing the step 4.5; extracting all unique task attributes of the bottommost layer;
step 4.7: arranging all the extracted task unique attributes in reverse order according to the extraction sequence, and obtaining the blood relationship of each target task;
step 4.8: traversing all the unique attributes of the target tasks in the step 4.3, and sequentially executing the steps 4.4 to 4.7; obtaining the blood relationship of all target tasks;
step 4.9: aiming at the blood relationship of all target tasks, if the same dependency relationship exists, merging is carried out, and after merging, reservation is carried out; if the same-layer dependency relationship exists, the same-layer dependency separation is required.
2. The method for implementing automatic run-out testing based on the blood relationship generated by the scheduling configuration according to claim 1, wherein the method comprises the following steps: step 1 also requires selecting a data synchronization method according to the storage form of the scheduling configuration content.
3. The method for implementing automatic run-out testing based on the blood relationship generated by the scheduling configuration according to claim 1, wherein the method comprises the following steps: the synchronization frequency should be higher than the configuration change frequency; the synchronization time should be later than the change time.
4. The method for implementing automatic run-out testing based on the blood relationship generated by the scheduling configuration according to claim 1, wherein the method comprises the following steps: the step 3 comprises the following steps of 3.1: determining a test environment scheduling configuration storage position;
step 3.2: configuring a timing synchronization task according to the synchronization frequency;
step 3.3: timing the synchronous task to run to the point for execution, and triggering the synchronous action to run to the point for execution;
step 3.4: detecting whether the configuration content of the test environment is the same as that of the generation environment, if not, continuing to execute the synchronous operation in the step 3; if the two are the same, executing the step 4.
5. The method for implementing automatic run-out testing based on the blood relationship generated by the scheduling configuration according to claim 1, wherein the method comprises the following steps: said step 5 comprises the steps of: step 5.1: obtaining running batch programs to be executed according to one-to-one mapping relations among different task attributes;
step 5.2: determining a program language based on the program name suffix of the running program to be executed, which is obtained in the step 5.1, so as to determine a running program execution command;
step 5.3: and according to the blood margin dependency relationship sequence, each running batch program execution command is packaged into different files in a layered manner.
6. The method for implementing automatic run-out based on the blood relationship generated by the scheduling configuration according to claim 5, wherein the method comprises the following steps: the step 6 comprises the following steps: step 6.1: determining a calling end program code language;
step 6.2: determining the function to be realized by the calling end program based on the file packaged in the step 5.3;
step 6.3: executing the batch running program according to the calling end program determined in the step 6.2 and the running mode of the calling end program;
step 6.4: if the batch running process is executed in error, positioning and correcting error reasons;
step 6.5: and evaluating the concurrency number according to the resources and the consumed time and adjusting the concurrency number.
7. The method for implementing automatic run-out based on the blood relationship generated by the scheduling configuration according to claim 6, wherein the method comprises the following steps: the step 7 comprises the following steps: step 7.1: writing a test case;
step 7.2: after the batch running is completed in the step 6, executing test checking on the result after the batch running according to the writing content of the test case, and marking whether the test case passes or not;
step 7.3: and 7.2, positioning the problem reasons if the test check fails, and performing bug classification according to the problem influence range and the importance.
8. The method for implementing automatic run-out based on the blood relationship generated by the scheduling configuration according to claim 6, wherein the method comprises the following steps: step 6.2 further comprises executing the running batch program concurrently on the same layer and without dependency relationship.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110716454.9A CN113535352B (en) | 2021-06-28 | 2021-06-28 | Test method for realizing automatic batch running based on blood relationship generated by scheduling configuration |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110716454.9A CN113535352B (en) | 2021-06-28 | 2021-06-28 | Test method for realizing automatic batch running based on blood relationship generated by scheduling configuration |
Publications (2)
Publication Number | Publication Date |
---|---|
CN113535352A CN113535352A (en) | 2021-10-22 |
CN113535352B true CN113535352B (en) | 2023-06-06 |
Family
ID=78096841
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202110716454.9A Active CN113535352B (en) | 2021-06-28 | 2021-06-28 | Test method for realizing automatic batch running based on blood relationship generated by scheduling configuration |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN113535352B (en) |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106484520A (en) * | 2016-10-17 | 2017-03-08 | 北京集奥聚合科技有限公司 | A kind of intelligent dispatching method based on data blood relationship and system |
CN107545030A (en) * | 2017-07-17 | 2018-01-05 | 阿里巴巴集团控股有限公司 | Processing method, device and the equipment of data genetic connection |
CN111158990A (en) * | 2019-12-31 | 2020-05-15 | 重庆富民银行股份有限公司 | Data warehouse intelligent scheduling task batch running system and method |
CN111858065A (en) * | 2020-07-28 | 2020-10-30 | 中国平安财产保险股份有限公司 | Data processing method, device, storage medium and device |
CN112015722A (en) * | 2020-11-02 | 2020-12-01 | 浙江大华技术股份有限公司 | Database management method, data blood relationship analysis method and related device |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10664316B2 (en) * | 2017-01-31 | 2020-05-26 | Hewlett Packard Enterprise Development Lp | Performing a computation using provenance data |
-
2021
- 2021-06-28 CN CN202110716454.9A patent/CN113535352B/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106484520A (en) * | 2016-10-17 | 2017-03-08 | 北京集奥聚合科技有限公司 | A kind of intelligent dispatching method based on data blood relationship and system |
CN107545030A (en) * | 2017-07-17 | 2018-01-05 | 阿里巴巴集团控股有限公司 | Processing method, device and the equipment of data genetic connection |
CN111158990A (en) * | 2019-12-31 | 2020-05-15 | 重庆富民银行股份有限公司 | Data warehouse intelligent scheduling task batch running system and method |
CN111858065A (en) * | 2020-07-28 | 2020-10-30 | 中国平安财产保险股份有限公司 | Data processing method, device, storage medium and device |
CN112015722A (en) * | 2020-11-02 | 2020-12-01 | 浙江大华技术股份有限公司 | Database management method, data blood relationship analysis method and related device |
Non-Patent Citations (2)
Title |
---|
"基于数据血缘构建数据分析方法";李春梅 等;《中国新通信》;第50-51页 * |
Anila Sahar Butt 等."A provenance model for control-flow driven scientific workflows".《Data & Knowledge Engineering》.2021,第1-8页. * |
Also Published As
Publication number | Publication date |
---|---|
CN113535352A (en) | 2021-10-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN106970921B (en) | Data migration method and device | |
CN106156278B (en) | Database data reading and writing method and device | |
CN107168879B (en) | Method and device for generating test report of centralized configuration management system | |
US9632769B2 (en) | Software build optimization | |
CN107515874B (en) | Method and equipment for synchronizing incremental data in distributed non-relational database | |
US20180081956A1 (en) | Method for automatically synchronizing multi-source heterogeneous data resources | |
CN114741375A (en) | Rapid and automatic data migration system and method for multi-source heterogeneous database | |
CN112559525B (en) | Data checking system, method, device and server | |
CN112131315A (en) | Database synchronization method and device under multi-task parallel development | |
CN106445618A (en) | Automatic database updating method | |
CN109165210A (en) | A kind of method and device of cluster Hbase Data Migration | |
CN113535352B (en) | Test method for realizing automatic batch running based on blood relationship generated by scheduling configuration | |
CN102880473A (en) | Method and device for task execution based on quartz framework | |
CN109471901B (en) | Data synchronization method and device | |
CN112035444B (en) | Method and device for transferring image data among heterogeneous systems without stopping | |
CN116627609A (en) | Hive batch processing-based scheduling method and device | |
CN116414914A (en) | Data synchronization method and device, processor and electronic equipment | |
CN116069765A (en) | Data migration method, device, electronic equipment and storage medium | |
CN115114275A (en) | Data acquisition method, device and medium | |
CN109144486A (en) | A kind of workflow implementation method statelessly changed | |
CN110096292B (en) | Method and system for refreshing BIOS firmware of server in self-adaptive manner | |
CN113742125A (en) | Lightweight high-throughput computing mode and fault-tolerant method thereof | |
US8892519B2 (en) | Command interpreter | |
CN115237573B (en) | Data processing method, device, electronic equipment and readable storage medium | |
CN114443292B (en) | Client management method, device and system based on workflow task scheduling system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |