CN117216135A - A method for generating ETL execution templates - Google Patents
A method for generating ETL execution templates Download PDFInfo
- Publication number
- CN117216135A CN117216135A CN202311001775.6A CN202311001775A CN117216135A CN 117216135 A CN117216135 A CN 117216135A CN 202311001775 A CN202311001775 A CN 202311001775A CN 117216135 A CN117216135 A CN 117216135A
- Authority
- CN
- China
- Prior art keywords
- execution
- etl
- template
- logic
- factory
- 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.)
- Pending
Links
Landscapes
- Stored Programmes (AREA)
Abstract
The application relates to a method for generating an ETL execution template, which generates an ETL execution context through an ETL execution context factory; resolving execution logic in the ETL execution context: operator dependencies, lifecycles, and basic properties; sending the execution logic to a preview plant; and generating an ETL service execution template corresponding to the service logic and the ETL execution context by the preview factory. An execution logic template can be constructed according to the DRY principle, the template can be used for carrying out operator analysis and execution and preview on the input operator graphs, and massive input operator graphs can be subjected to operation according to a unified service logic mode, so that the ETL execution template is repeatedly called, the execution and preview of the ETL are realized, and unified processing smoothness is expected to be realized for the execution and preview of the ETL. And uniformly utilizing the ETL execution template to perform spam processing on a large number of calculation graphs, so that the ETL task execution efficiency is improved.
Description
Technical Field
The disclosure relates to the technical field of ETL task execution, and in particular relates to a method, a system and electronic equipment for generating an ETL execution template.
Background
The ETL task execution schematic diagram shown in FIG. 1 mainly refers to task execution in a JobEngine task factory of an ETL module, and the ETL task execution mainly refers to analysis operation on an operator graph input by a user, so as to generate a corresponding task engine universal script for execution in a task engine. The ETL execution context factory generates an ETL execution context, and provides operator operation methods of some basic contexts based on BaseETLContext.
The ETL execution context has two functions:
one is to convert parameters into DataFlow and BaseCommand topology ordering;
the other is to isolate the other domains. The ETL is not in direct contact with other domains, preventing direct coupling of the two.
The ETL execution context thus corresponds to an appearance model, with the purpose of hiding the complexity of external calls, providing delegated calls for ETL domains to interact with other domains.
And the ETL task mainly comprises an ETL task execution flow and a corresponding ETL task preview. The ETL task execution flow refers to executing the constructed ETL task according to preset execution logic, and analyzing and executing an operator diagram in the ETL task according to business logic; and previewing the ETL task, and displaying the execution result of the ETL task to a user according to certain business logic.
From the above, the execution process and the preview process are logically very similar in the execution flow of ETL execution and preview.
Therefore, in order to follow the DRY principle, the user and the like do not want to repeatedly implement the same business logic, that is, want to repeatedly call and implement the execution and preview of the ETL according to a uniform business logic mode, and want to implement uniform processing smoothness for the execution and preview of the ETL.
Therefore, the application is to extract a unified ETL execution template between preview and execution, and the template factory generates a standard execution template, thereby the unified exception handling flow is in the process of being used.
Disclosure of Invention
In order to solve the problems, the application provides a method, a system and electronic equipment for generating an ETL execution template.
In one aspect of the present application, a method for generating an ETL execution template is provided, including the following steps:
generating an ETL execution context-ETL Execution Contextx by the ETL execution context factory-ETL Execution Context Factory;
analyzing the ETL execution context-ETL Execution Contextx to obtain execution logic in the ETL execution context: operator dependencies, lifecycles, and basic properties;
sending the execution logic to a preview plant-ET LPreview Factory;
and generating an ETL business execution template-Abstract ETL Business Template corresponding to the business logic and the ETL execution context by the preview factory-ET LPreview Factory according to the execution logic.
As an optional embodiment of the application, optionally, the operator relying comprises:
supporting relevant encapsulation logic analyzed by operators;
the operator analysis needs to use the expression construction to the outside;
the complex functions needed for operator analysis are packaged in the operator dependence so as to be convenient for operator analysis.
As an alternative embodiment of the present application, optionally, the life cycle includes:
creating/updating a data set in the ETL executing process;
acquiring an input/output data set;
examining the output dataset;
inheritance of the dataset;
a completion notification of the operation;
it is checked whether the input data set is available.
As an optional embodiment of the present application, optionally, the basic attribute includes:
basic attributes required by the ETL in running are provided, including operator networks, versions, split node information, domains, owners, priority settings, additional task parameters and trigger paths.
As an optional implementation manner of the present application, optionally, generating, by the preview factory-ET LPreview Factory, an ETL service execution template-Abstract ETL Business Template corresponding to the ETL execution context and service logic according to the execution logic, includes:
the preview factory-ET LPreview Factory executes logic in accordance with the ETL execution context: operator dependence, lifecycle and basic attributes, the following template contents are constructed:
(1) Generating an execution task module-spawn for:
generating an ETL execution task and submitting task management execution;
(2) Building a return information module, namely a build Response, for:
constructing return information, including task ID, error reporting information and front end display;
(3) Task execution pre-check module-before Execute Task for
(3.1), pre-logic check at task execution:
judging whether the execution is fused or not according to the parameters;
judging whether a timeout mark is set, if so, indicating that the ETL has serious performance problem, and not allowing execution;
judging whether the operation is in operation or not, and preventing repeated operation;
judging whether the BI is scheduled by the workflow, if yes, indicating that the BI has lost the scheduling authority of the ETL;
judging whether the BI is scheduled by the workflow, if yes, indicating that the BI has lost the scheduling authority of the ETL;
checking whether a generated catalog of the output dataset is available/valid;
judging whether ETL is being modified, if so, prohibiting execution when the structure is being modified;
(3.2), pre-logic check at preview:
whether the number of lines after Join exceeds a set limit;
(4) A task execution post-processing module-after Execute Task for:
performing some subsequent processing after the task is executed;
(5) Execution task module-execution for:
defining an actual execution body of a task, comprising the following logic: subtask generation and operator analysis;
after construction, generating the ETL service execution template-Abstract ETL Business Template;
and configuring and operating the ETL business execution template-Abstract ETL Business Template.
In another aspect of the present application, a system for implementing the method for generating the ETL execution template is provided, including:
an ETL execution context generation module for generating an ETL execution context-ETL Execution Contextx via the ETL execution context factory-ETL Execution Context Factory;
the analysis module is used for analyzing the ETL execution context-ETL Execution Contextx to obtain execution logic in the ETL execution context: operator dependencies, lifecycles, and basic properties;
a sending module for sending the execution logic to a preview factory-ET LPreview Factory;
and the template generation module is used for generating an ETL business execution template-Abstract ETL Business Template corresponding to the business logic and the ETL execution context by the preview factory-ET LPreview Factory according to the execution logic.
On the other hand, the application also provides the ETL execution template generated by adopting the ETL execution template generation method.
In another aspect of the present application, an application method of the ETL execution template is further provided, including the following steps:
acquiring an operator graph input by a user;
calling one ETL execution template from the background;
inputting the operator graph into the ETL execution template, executing the analysis task of the operator graph according to the template content, and previewing and outputting an analysis result.
In another aspect, the present application further provides an electronic device, including:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to implement an application method of the ETL execution template when executing the executable instructions.
The application has the technical effects that:
the application generates the ETL execution context through the ETL execution context factory; analyzing the ETL execution context-ETL Execution Contextx to obtain execution logic in the ETL execution context: operator dependencies, lifecycles, and basic properties; sending the execution logic to a preview plant; and generating an ETL business execution template corresponding to the business logic and the ETL execution context by the preview factory according to the execution logic. The execution logic template of the operator graph can be constructed according to the DRY principle, the operator analysis and execution and preview can be carried out on the input operator graph by utilizing the execution logic template, the ETL execution template can be repeatedly called according to a uniform business logic mode on a large number of input operator graphs, the execution and preview of the ETL are realized, and uniform processing smoothness is expected to be realized on the execution and preview of the ETL. And between preview and execution, uniformly utilizing the ETL execution template to perform spam processing uniform exception processing flow on a large number of operator graphs, unifying ETL task execution and preview logic, and improving ETL task execution efficiency.
Other features and aspects of the present disclosure will become apparent from the following detailed description of exemplary embodiments, which proceeds with reference to the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments, features and aspects of the present disclosure and together with the description, serve to explain the principles of the disclosure.
FIG. 1 illustrates a schematic diagram of task execution for ETL;
FIG. 2 is a schematic diagram of the flow chart of the method for generating ETL execution templates according to the present application;
FIG. 3 is a schematic diagram showing the composition of an ETL execution template according to the present application;
fig. 4 shows a schematic application diagram of the electronic device of the application.
Detailed Description
Various exemplary embodiments, features and aspects of the disclosure will be described in detail below with reference to the drawings. In the drawings, like reference numbers indicate identical or functionally similar elements. Although various aspects of the embodiments are illustrated in the accompanying drawings, the drawings are not necessarily drawn to scale unless specifically indicated.
The word "exemplary" is used herein to mean "serving as an example, embodiment, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.
In addition, numerous specific details are set forth in the following detailed description in order to provide a better understanding of the present disclosure. It will be understood by those skilled in the art that the present disclosure may be practiced without some of these specific details. In some instances, well known means, elements, and circuits have not been described in detail so as not to obscure the present disclosure.
As shown in fig. 1, the required translator parameters can be generated by acquiring the input operator graph and according to the operator graph; generating a corresponding ETL context according to the operator graph, and inputting the ETL context to a translator; the translator translates the operator graph by utilizing the translator parameters to generate a corresponding operator intermediate representation; and converting the operator intermediate representation into a task engine universal script, and sending the task engine universal script to a task engine factory for execution. The operator graph can be subjected to topological sorting and translation by using the translator, after the operator graph is translated, the corresponding task engine universal script is generated by using the intermediate representation conversion of the operator with the corresponding topology construction, so that the task engine factory can flexibly execute the task engine universal script generated by the operator graph, flexibly schedule and queue the execution, and the execution flexibility of the operator graph is improved.
According to the technical scheme, in order to realize ETL execution and preview of the operator graph, the ETL execution and preview can be repeatedly invoked and realized according to a uniform business logic mode, and uniform processing smoothness is expected to be realized for the ETL execution and preview. Therefore, to extract a unified ETL execution template between preview and execution, a template factory generates a canonical execution template, which trails some unified exception handling procedures.
Example 1
As shown in fig. 2, in one aspect of the present application, a method for generating an ETL execution template is provided, including the following steps:
s1, generating an ETL execution context-ETL Execution Contextx through an ETL execution context factory-ETL Execution Context Factory;
s2, analyzing the ETL execution context-ETL Execution Contextx to obtain execution logic in the ETL execution context: operator dependencies, lifecycles, and basic properties;
s3, sending the execution logic to a preview factory-ET LPreview Factory;
s4, generating an ETL business execution template-Abstract ETL Business Template corresponding to the business logic and the ETL execution context by the preview factory-ET LPreview Factory according to the execution logic.
The scheme mainly relates to the following two main bodies:
ETL execution context factory-ETL Execution Context Factory;
preview plant-ET LPreview Factory.
The ETL execution context factory is used for generating an ETL execution context, the preview factory is used for analyzing the text structure of the ETL execution context, acquiring the execution logic structure of the ETL execution context, and constructing a corresponding ETL execution template according to the execution logic structure.
For the overall execution process of the ETL execution template, reference may be made to the operator parsing and task execution flow of fig. 1.
Wherein, as shown in fig. 3:
a context is first generated by I-ETL Execution Context Factory and sent to C-ET LPreview Factor.
ET LPreview Factory constructs an abstract ETL business template by deriving preview templates (translator parameters) (Abstract ET LBusinessTemplate).
ET LPreview Factory by template creation, an ETL execution template is generated that is capable of generating and executing contextual tasks, the ETL execution template comprising the following parts:
spawn, build Response, before Execute Task, after Execute Task and execute.
Preview plant-ET LPreview Factory, the main task is to build corresponding ETL execution templates according to the execution logic structure.
It is therefore necessary to obtain, from the generated ETL context, ETL task execution logic that is divided into three parts according to behavior: operator dependencies, lifecycles, and basic attributes.
Operator dependencies, lifecycles, and basic attributes, the main application logic for the three parts, see below for details:
as an optional embodiment of the application, optionally, the operator relying comprises:
supporting relevant encapsulation logic analyzed by operators;
the operator analysis needs to use the expression construction to the outside;
the complex functions needed for operator analysis are packaged in the operator dependence so as to be convenient for operator analysis.
As an alternative embodiment of the present application, optionally, the life cycle includes:
creating/updating a data set in the ETL executing process;
acquiring an input/output data set;
examining the output dataset;
inheritance of the dataset;
a completion notification of the operation;
it is checked whether the input data set is available.
As an optional embodiment of the present application, optionally, the basic attribute includes:
basic attributes required by the ETL in running are provided, including operator networks, versions, split node information, domains, owners, priority settings, additional task parameters and trigger paths.
The preview factory (ET LPreview Factory), after deriving its execution logic from the generated ETL execution context, may generate a corresponding business execution template (Abstract ET LBusiness Template) according to its execution logic.
The method comprises the following steps:
as an optional implementation manner of the present application, optionally, generating, by the preview factory-ET LPreview Factory, an ETL service execution template-Abstract ETL Business Template corresponding to the ETL execution context and service logic according to the execution logic, includes:
the preview factory-ET LPreview Factory executes logic in accordance with the ETL execution context: operator dependence, lifecycle and basic attributes, the following template contents are constructed:
(1) Generating an execution task module-spawn for:
generating an ETL execution task and submitting task management execution;
(2) Building a return information module, namely a build Response, for:
constructing return information, including task ID, error reporting information and front end display;
(3) Task execution pre-check module-before Execute Task for
(3.1), pre-logic check at task execution:
judging whether the execution is fused or not according to the parameters;
judging whether a timeout mark is set, if so, indicating that the ETL has serious performance problem, and not allowing execution;
judging whether the operation is in operation or not, and preventing repeated operation;
judging whether the BI is scheduled by the workflow, if yes, indicating that the BI has lost the scheduling authority of the ETL;
judging whether the BI is scheduled by the workflow, if yes, indicating that the BI has lost the scheduling authority of the ETL;
checking whether a generated catalog of the output dataset is available/valid;
judging whether ETL is being modified, if so, prohibiting execution when the structure is being modified;
(3.2), pre-logic check at preview:
whether the number of lines after Join exceeds a set limit;
(4) A task execution post-processing module-after Execute Task for:
performing some subsequent processing after the task is executed;
(5) Execution task module-execution for:
defining an actual execution body of a task, comprising the following logic: subtask generation and operator analysis;
after construction, generating the ETL service execution template-Abstract ETL Business Template;
the ETL business execution template-Abstract ETL Business Template is configured and stored on the background.
Five template function modules (respectively: generating, constructing a return value, processing a front task, processing a rear task and executing a task) of the spline, the build Response, before Execute Task, after Execute Task, the execution and the like are generated through the template function construction, and the functions of the function modules are described in detail in the description.
And the five template function modules respond to the ETL task execution logic according to the operator dependence, the life cycle and the logic execution sequence of the basic attribute in the original ETL execution process.
On the other hand, the application also provides the ETL execution template generated by adopting the ETL execution template generation method. See the above described method for generating ETL execution templates for details.
Therefore, the application can repeatedly call the ETL execution template and realize the execution and preview of the ETL according to the unified business logic mode for the operator graphs with massive inputs, and is expected to realize unified processing smoothness for the execution and preview of the ETL. And uniformly utilizing the ETL execution template to perform spam processing on a large number of calculation graphs, so that the ETL task execution efficiency is improved.
It should be apparent to those skilled in the art that implementing all or part of the above-described embodiments may be accomplished by computer programs to instruct related hardware, and the programs may be stored in a computer readable storage medium, which when executed may include the processes of the embodiments of the controls described above. It will be appreciated by those skilled in the art that implementing all or part of the above-described embodiments may be accomplished by computer programs to instruct related hardware, and the programs may be stored in a computer readable storage medium, which when executed may include the processes of the embodiments of the controls described above. The storage medium may be a magnetic disk, an optical disc, a Read-only memory (ROM), a random access memory (RandomAccessMemory, RAM), a flash memory (flash memory), a hard disk (HDD), or a Solid State Drive (SSD); the storage medium may also comprise a combination of memories of the kind described above.
Example 2
Based on the implementation principle of embodiment 1, in another aspect of the present application, a system for implementing the method for generating the ETL execution template is provided, including:
an ETL execution context generation module for generating an ETL execution context-ETL Execution Contextx via the ETL execution context factory-ETL Execution Context Factory;
the analysis module is used for analyzing the ETL execution context-ETL Execution Contextx to obtain execution logic in the ETL execution context: operator dependencies, lifecycles, and basic properties;
a sending module for sending the execution logic to a preview factory-ET LPreview Factory;
and the template generation module is used for generating an ETL business execution template-Abstract ETL Business Template corresponding to the business logic and the ETL execution context by the preview factory-ET LPreview Factory according to the execution logic.
The modules or steps of the application described above may be implemented in a general-purpose computing device, they may be centralized in a single computing device, or distributed across a network of computing devices, or they may alternatively be implemented in program code executable by a computing device, such that they may be stored in a memory device and executed by a computing device, or they may be separately fabricated into individual integrated circuit modules, or multiple modules or steps within them may be fabricated into a single integrated circuit module. Thus, the present application is not limited to any specific combination of hardware and software.
Example 3
In another aspect of the present application, an application method of the ETL execution template is further provided, including the following steps:
acquiring an operator graph input by a user;
calling one ETL execution template from the background;
inputting the operator graph into the ETL execution template, executing the analysis task of the operator graph according to the template content, and previewing and outputting an analysis result.
For the above application method, please refer to the description of the functional module of the ETL execution template in embodiment 1, and meanwhile, the description may be understood with reference to the ETL execution flow of the operator diagram in fig. 1.
Example 4
As shown in fig. 4, in still another aspect, the present application further provides an electronic device, including:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to implement an application method of the ETL execution template when executing the executable instructions.
Embodiments of the present disclosure provide for an electronic device that includes a processor and a memory for storing processor-executable instructions. Wherein the processor is configured to implement the application method of the ETL execution template described above when executing the executable instructions.
Here, it should be noted that the number of processors may be one or more. Meanwhile, in the electronic device of the embodiment of the disclosure, an input device and an output device may be further included. The processor, the memory, the input device, and the output device may be connected by a bus, or may be connected by other means, which is not specifically limited herein.
The memory is a computer-readable storage medium that can be used to store software programs, computer-executable programs, and various modules, such as: the ETL of the embodiment of the disclosure executes a program or a module corresponding to an application method of the template. The processor executes various functional applications and data processing of the electronic device by running software programs or modules stored in the memory.
The input device may be used to receive an input number or signal. Wherein the signal may be a key signal generated in connection with user settings of the device/terminal/server and function control. The output means may comprise a display device such as a display screen.
The foregoing description of the embodiments of the present disclosure has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the various embodiments described. The terminology used herein was chosen in order to best explain the principles of the embodiments, the practical application, or the technical improvement of the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
Claims (9)
1. The ETL execution template generation method is characterized by comprising the following steps:
generating an ETL execution context-ETL Execution Contextx by the ETL execution context factory-ETL Execution Context Factory;
analyzing the ETL execution context-ETL Execution Contextx to obtain execution logic in the ETL execution context: operator dependencies, lifecycles, and basic properties;
sending the execution logic to a preview plant-ET LPreview Factory;
and generating an ETL business execution template-Abstract ETL Business Template corresponding to the business logic and the ETL execution context by the preview factory-ET LPreview Factory according to the execution logic.
2. The method of generating ETL execution templates according to claim 1, wherein the operator dependencies comprise:
supporting relevant encapsulation logic analyzed by operators;
the operator analysis needs to use the expression construction to the outside;
the complex functions needed for operator analysis are packaged in the operator dependence so as to be convenient for operator analysis.
3. The method of generating ETL execution templates according to claim 1, wherein the lifecycle comprises:
creating/updating a data set in the ETL executing process;
acquiring an input/output data set;
examining the output dataset;
inheritance of the dataset;
a completion notification of the operation;
it is checked whether the input data set is available.
4. The method for generating an ETL execution template according to claim 1, wherein the basic attributes include:
basic attributes required by the ETL in running are provided, including operator networks, versions, split node information, domains, owners, priority settings, additional task parameters and trigger paths.
5. The method of claim 1, wherein generating, by the preview plant-ET LPreview Factory, an ETL service execution template-Abstract ETL Business Template corresponding to the ETL execution context and service logic according to the execution logic, comprises:
the preview factory-ET LPreview Factory executes logic in accordance with the ETL execution context: operator dependence, lifecycle and basic attributes, the following template contents are constructed:
(1) Generating an execution task module-spawn for:
generating an ETL execution task and submitting task management execution;
(2) Building a return information module, namely a build Response, for:
constructing return information, including task ID, error reporting information and front end display;
(3) Task execution pre-check module-before Execute Task for
(3.1), pre-logic check at task execution:
judging whether the execution is fused or not according to the parameters;
judging whether a timeout mark is set, if so, indicating that the ETL has serious performance problem, and not allowing execution;
judging whether the operation is in operation or not, and preventing repeated operation;
judging whether the BI is scheduled by the workflow, if yes, indicating that the BI has lost the scheduling authority of the ETL;
judging whether the BI is scheduled by the workflow, if yes, indicating that the BI has lost the scheduling authority of the ETL;
checking whether a generated catalog of the output dataset is available/valid;
judging whether ETL is being modified, if so, prohibiting execution when the structure is being modified;
(3.2), pre-logic check at preview:
whether the number of lines after Join exceeds a set limit;
(4) A task execution post-processing module-after Execute Task for:
performing some subsequent processing after the task is executed;
(5) Execution task module-execution for:
defining an actual execution body of a task, comprising the following logic: subtask generation and operator analysis;
after construction, generating the ETL service execution template-Abstract ETL Business Template;
and configuring and operating the ETL business execution template-Abstract ETL Business Template.
6. A system for implementing the method for generating an ETL execution template according to any one of claims 1-5, comprising:
an ETL execution context generation module for generating an ETL execution context-ETL Execution Contextx via the ETL execution context factory-ETL Execution Context Factory;
the analysis module is used for analyzing the ETL execution context-ETL Execution Contextx to obtain execution logic in the ETL execution context: operator dependencies, lifecycles, and basic properties;
a sending module for sending the execution logic to a preview factory-ET LPreview Factory;
and the template generation module is used for generating an ETL business execution template-Abstract ETL Business Template corresponding to the business logic and the ETL execution context by the preview factory-ET LPreview Factory according to the execution logic.
7. An ETL execution template generated using the ETL execution template generation method of any one of claims 1-5.
8. A method of applying the ETL execution template of claim 7, comprising the steps of:
acquiring an operator graph input by a user;
calling one ETL execution template from the background;
inputting the operator graph into the ETL execution template, executing the analysis task of the operator graph according to the template content in claim 5, and previewing and outputting the analysis result.
9. An electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to implement the method of application of the ETL execution template of claim 8 when executing the executable instructions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311001775.6A CN117216135A (en) | 2023-08-10 | 2023-08-10 | A method for generating ETL execution templates |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311001775.6A CN117216135A (en) | 2023-08-10 | 2023-08-10 | A method for generating ETL execution templates |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117216135A true CN117216135A (en) | 2023-12-12 |
Family
ID=89047011
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311001775.6A Pending CN117216135A (en) | 2023-08-10 | 2023-08-10 | A method for generating ETL execution templates |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117216135A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN119168596A (en) * | 2024-11-20 | 2024-12-20 | 浙江兴丰智能科技有限公司 | Panoramic operation early warning analysis method and system for EMS full life cycle management |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080046803A1 (en) * | 2002-09-06 | 2008-02-21 | Beauchamp Tim J | Application-specific personalization for data display |
| CN103309904A (en) * | 2012-03-16 | 2013-09-18 | 阿里巴巴集团控股有限公司 | Method and device for generating data warehouse ETL (Extraction, Transformation and Loading) codes |
| CN111159266A (en) * | 2019-12-05 | 2020-05-15 | 江苏艾佳家居用品有限公司 | ETL task batch generation method based on metadata |
| CN114036183A (en) * | 2021-11-24 | 2022-02-11 | 杭州安恒信息技术股份有限公司 | A data ETL processing method, device, equipment and medium |
-
2023
- 2023-08-10 CN CN202311001775.6A patent/CN117216135A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080046803A1 (en) * | 2002-09-06 | 2008-02-21 | Beauchamp Tim J | Application-specific personalization for data display |
| CN103309904A (en) * | 2012-03-16 | 2013-09-18 | 阿里巴巴集团控股有限公司 | Method and device for generating data warehouse ETL (Extraction, Transformation and Loading) codes |
| CN111159266A (en) * | 2019-12-05 | 2020-05-15 | 江苏艾佳家居用品有限公司 | ETL task batch generation method based on metadata |
| CN114036183A (en) * | 2021-11-24 | 2022-02-11 | 杭州安恒信息技术股份有限公司 | A data ETL processing method, device, equipment and medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN119168596A (en) * | 2024-11-20 | 2024-12-20 | 浙江兴丰智能科技有限公司 | Panoramic operation early warning analysis method and system for EMS full life cycle management |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109542399B (en) | Software development method and device, terminal equipment and computer readable storage medium | |
| CN108304201B (en) | Object updating method, device and equipment | |
| CN111078315A (en) | Microservice orchestration, execution method and system, architecture, device, storage medium | |
| CN112748908A (en) | Restful service development method and device based on SSM framework | |
| CN102109984B (en) | State machine processing method and system | |
| CN110188135A (en) | File generation method and device | |
| WO2018036342A1 (en) | Csar-based template design visualization method and device | |
| CN113867600A (en) | Development method, apparatus and computer equipment for processing streaming data | |
| CN112948110B (en) | Topology and arrangement system and method of cloud application, storage medium and electronic equipment | |
| CN113448678A (en) | Application information generation method, deployment method, device, system and storage medium | |
| CN114205230A (en) | Method, system, medium and electronic device for configuring cloud native network element | |
| KR20240078292A (en) | System for automating business process and method thereof | |
| CN110750307B (en) | Micro-service architecture construction method and device | |
| CN117573758A (en) | Data stream arrangement method based on BI platform | |
| CN113885844A (en) | Business service arranging method and related device | |
| CN115858205B (en) | Simulation component interaction method, device and equipment based on memory blackboard mechanism | |
| CN113656001A (en) | Platform component development method, apparatus, computer equipment and storage medium | |
| CN117216135A (en) | A method for generating ETL execution templates | |
| CN111158797A (en) | Method, system and engine device for operating artificial intelligence application | |
| CN117111894A (en) | Method for converting data based on ETL module of low code development | |
| CN113220586A (en) | Automatic interface pressure test execution method, device and system | |
| CN114356462B (en) | A visual inspection method, device, equipment and medium based on flowchart | |
| CN111324332A (en) | Big data task processing method and system, electronic device and storage medium | |
| CN111124386B (en) | Animation event processing method, device, equipment and storage medium based on Unity | |
| CN115756419A (en) | Heterogeneous algorithm model processing system, method, equipment and medium |
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 |