Transformation method for extract, transform and load (ETL) operation relation graph and implementation system thereof

Abstract

The invention relates to the field of computer software, in particular to a transformation method for an extract, transform and load (ETL) operation relation graph and an implementation system thereof. The method comprises the following steps: requesting task relation data related to the current task node from a background, wherein the current task node is taken as a center; receiving the request by the background, finding logic relation related to the current task node and storing into the corresponding task relation data; returning the task relation data to a foreground; receiving the task relation data by the foreground and drawing the task relation data into a corresponding relation graph; and selecting any one task node as the next current task node and repeating the steps 1 to 4 until all the task nodes are subjected to operation of the steps 1 to 4. A user can observe logic relation graphs of different hierarchies and different angles according to the own wish, so that the work efficiency is improved, fault during configuration is reduced and construction of the ETL and a data warehouse is accelerated.

Description

technical field [0001] The invention relates to the field of computer software, in particular to a method for transforming ETL operation relation diagrams and a system for realizing the same. Background technique [0002] At present, the ETL (Extract-Transform-Load, data extraction, transformation, loading) tools in the software industry describe the relationship between jobs through process configuration or relationship interface configuration, and the relationship between jobs is mostly a tree relationship. , or trigger, dependency. For triggering and dependency tasks, because dependencies and triggering relationships are not based on a standard tree structure or hierarchical structure, there is no better solution for graphical display of ETL task dependencies and triggering relationships. It mainly has the following two defects: [0003] 1. The display of general ETL data extraction, conversion, and loading software is defined and drawn by the user himself, triggering t...

AI Technical Summary

Problems solved by technology

[0003] 1. The display of general ETL data extraction, conversion, and loading software is defined and drawn by the user himself, triggering the relationship diagram. This can certainly solve some problems, but when configuring a large number of tasks, especially The logical relationship between telecommunications and financial industries is usually many and complicated

Higher requirements are put forward for users, and a lot of extra workload is caused, and unnecessary task relationship drawing is required;

[0004] 2. Provide quick configuration of multiple logical relationships, but on the graphical display, often only realize the task relationship tree, or the display method of tabular data. For developers, all the tabular data provided in complex job relationships , like looking for a needle in a haystack, the reference meaning is basically not great, so that users often cannot observe the logical relationship correctly, which leads to the formation of a closed loop of logical relationship configuration

Images