Data offloading method and device for enterprise-level data, electronic device and storage medium

Abstract

The application provides a data unloading method and device for enterprise-level data, an electronic device and a storage medium. The application relates to data processing technology, and is particularly suitable for an enterprise-level data unloading scenario. The method comprises the following steps: acquiring a source data group in a source data layer of a data warehouse, so as to determine an enterprise-level data dictionary followed by the source data group; then, acquiring an application data version of a business component in a business system; and according to the application data version and the enterprise-level data dictionary, unloading enterprise-level data to the source data group, so that the data types of the business component and the source data group are consistent. The application can solve the problems that the data unloading transition in the prior art depends on specific databases and the business component is not connected with the enterprise-level data dictionary.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, in particular to a data unloading method and device for enterprise-level data, an electronic device and a storage medium. BACKGROUND

[0002] In a large enterprise application architecture, the business components in the enterprise-level business system and the data warehouse are in an upstream-downstream relationship. Unloading data for the data warehouse is a common technical requirement for the development of the business system and is very important.

[0003] In the prior art, when data is unloaded for the data warehouse, there is a common problem that the data unloading transition depends on a specific database, which causes the data unloading function to be almost in a paralyzed state when the specific database is changed. In addition, many business components are disconnected from the enterprise-level data dictionary, which causes the data to be unable to be loaded into the data warehouse when unloaded. SUMMARY

[0004] The present application provides a data unloading method and device for enterprise-level data, an electronic device and a storage medium, to solve the problems that the data unloading transition depends on a specific database and the business components are disconnected from the enterprise-level data dictionary, and to achieve the technical effect that the data unloading transition no longer depends on a specific database and the data types of the business components and the data groups in the source data layer of the data warehouse are consistent based on the enterprise-level data dictionary.

[0005] In one aspect, the present application provides a data unloading method for enterprise-level data, comprising:

[0006] obtaining a source data group in a source data layer of a data warehouse;

[0007] determining an enterprise-level data dictionary followed by the source data group;

[0008] obtaining an application data version of a business component in a business system;

[0009] unloading enterprise-level data to the source data group according to the application data version and the enterprise-level data dictionary, so that the data types of the business component and the source data group are consistent.

[0010] Further, the unloading of the enterprise-level data to the source data group according to the application data version and the enterprise-level data dictionary comprises:

[0011] obtaining enterprise-level data consistent with the data type of the source data group from the enterprise-level data dictionary according to the application data version;

[0012] running a data unloading program using a structured query language to unload the enterprise-level data from the business system to the data warehouse.

[0013] Further, the unloading of the enterprise-level data from the business system to the data warehouse comprises:

[0014] obtaining component feature information of the business component;

[0015] obtaining a predetermined data interface of the data warehouse and the business system;

[0016] unloading the enterprise-level data from the business system to the data warehouse according to the component feature information and the data interface.

[0017] Further, the method further comprises:

[0018] customizing the structured query language and customizing an output format of the enterprise-level data.

[0019] Further, the unloading of the enterprise-level data from the business system to the data warehouse comprises:

[0020] obtaining a last update timestamp of the enterprise-level data;

[0021] unloading the enterprise-level data from the business system to the data warehouse in a streaming manner according to the last update timestamp.

[0022] Further, the data interface comprises an extraction data interface and an unloading data interface, and the method further comprises:

[0023] generating a default processing rule of the data interface automatically when the data interface is generated;

[0024] customizing a special processing rule of the data interface for different business components, wherein the special processing rule is used for modifying or deleting fields in the data interface.

[0025] On the other hand, the application provides a data unloading device of enterprise-level data, and the device comprises:

[0026] a first obtaining module, configured to obtain a source data group in a data warehouse;

[0027] a determining module, configured to determine an enterprise-level data dictionary followed by the source data group;

[0028] a second obtaining module, configured to obtain an application data version of a business component in a business system;

[0029] a data unloading module, configured to unload enterprise-level data to the source data group according to the application data version and the enterprise-level data dictionary, so that the data types between the business component and the source data group are consistent.

[0030] Further, the data unloading module comprises:

[0031] an acquisition unit, configured to acquire enterprise data consistent with the data type of the data group from the enterprise data dictionary according to the application data version;

[0032] an unloading unit, configured to run a data unloading program by using the structured query language to unload the enterprise data from the business system to the data warehouse.

[0033] Further, the unloading unit comprises:

[0034] a first acquisition sub-module, configured to acquire component feature information of the business component;

[0035] a second acquisition sub-module, configured to acquire a data interface determined in advance by the data warehouse and the business system;

[0036] an unloading sub-module, configured to unload the enterprise data from the business system to the data warehouse according to the component feature information and the data interface.

[0037] Further, the device further comprises:

[0038] a customizing module, configured to customize the structured query language and customize an output format of the enterprise data.

[0039] Further, the unloading sub-module is specifically configured to acquire a last update timestamp of the enterprise data, and unload the enterprise data from the business system to the data warehouse by using a streaming processing mode according to the last update timestamp.

[0040] Further, the data interface comprises an extraction data interface and an unloading data interface, and the device further comprises:

[0041] a first generation module, configured to automatically generate a default processing rule of the data interface when the data interface is generated, wherein the default processing rule is used to represent that an original field or format is used by default;

[0042] a first generation module, configured to custom-generate a special processing rule of the data interface for different business components, wherein the special processing rule is used to modify or delete a field in the data interface.

[0043] In another aspect, the present application provides an electronic device, comprising: a processor, and a memory connected with the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement the method according to any one of the preceding aspects.

[0044] In another aspect, the present application provides a computer-readable storage medium, the computer-readable storage medium stores computer-executable instructions, the computer-executable instructions are executed by a processor to implement the method according to any one of the preceding aspects.

[0045] In another aspect, the present application provides a computer program product, comprising a computer program, the computer program is executed by a processor to implement the method according to any one of the preceding aspects.

[0046] The present application provides a data unloading method, device and electronic equipment for enterprise-level data, and a storage medium. The data unloading method for enterprise-level data provided by the present application comprises the following steps: obtaining a source data group in a source data layer of a data warehouse to determine an enterprise-level data dictionary followed by the source data group; then, obtaining an application data version of a business component in a business system; and according to the application data version and the enterprise-level data dictionary, unloading enterprise-level data to the source data group to make the data types of the business component and the source data group consistent.

[0047] Therefore, the embodiments of the present application can solve the problems that the data unloading transition depends on specific databases and the business component is disconnected from the enterprise-level data dictionary in the prior art, and achieve the technical effect that the data unloading transition no longer depends on specific databases, and the data types of the business component and the source data group of the data warehouse are guaranteed to be consistent based on the enterprise-level data dictionary. BRIEF DESCRIPTION OF DRAWINGS

[0048] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0049] Figure 1 is a flowchart of a data unloading method for enterprise-level data provided by an embodiment of the present application;

[0050] Figure 2 is a flowchart of an optional data unloading method for enterprise-level data provided by an embodiment of the present application;

[0051] Figure 3 is a flowchart of an optional data unloading method for enterprise-level data provided by an embodiment of the present application;

[0052] Figure 4A structural block diagram of a data unloading device for enterprise-level data provided by an embodiment of the present application;

[0053] Figure 5 A structural schematic diagram of an electronic device provided by an embodiment of the present application.

[0054] The specific embodiments of the present application have been shown by the above-described drawings, and will be described in more detail hereinafter. These drawings and the written description are not intended to restrict the scope of the present application concept in any way, but to illustrate the present application concept to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0055] The exemplary embodiments will be described in detail herein with reference to the attached drawings. In the following description, the same numbers are used to indicate the same or similar components. The embodiments described in the following exemplary embodiments are not meant to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the appended claims.

[0056] First, the terms involved in the present application are explained:

[0057] On-line transaction processing (OLTP), also known as transaction-oriented processing, is characterized by the fact that user data received in the foreground can be immediately transmitted to the computing center for processing and the processing result is given in a very short time, which is one of the ways to quickly respond to user operations.

[0058] Data unloading refers to the function of providing the table structure and table data of each business component of the OLTP type to the data warehouse.

[0059] Data transmission protocol refers to the data format and specifications that should be followed during data unloading.

[0060] Enterprise-level data dictionary refers to a management system for all domains, data items, and physical models used in data governance during enterprise development.

[0061] Streaming processing refers to opening a data stream when reading massive data, controlling the flow in a relatively small range, and processing the incoming data as soon as possible, rather than reading all the data and then processing it to prevent memory overflow.

[0062] Low-code development platform refers to a development platform that can quickly build various application systems through visual means without or with a small amount of code writing.

[0063] Operational Data Store (ODS): The ODS layer is also called the operational data layer, which collects and aggregates data from various business systems, retains original business process data as much as possible, and is basically consistent with the business system, only performs simple integration, unstructured data structuring, or adds identification data, and does not perform deep cleaning and processing.

[0064] Java Database Connectivity (JDBC): It is an application programming interface in Java language used to standardize how client programs access databases, and provides methods such as querying and updating data in databases.

[0065] In a large enterprise application architecture, the business components in the enterprise-level business system and the data warehouse are in an upstream and downstream relationship, and unloading data for the data warehouse is a common technical requirement for the development of the business system, and is very important.

[0066] Some common shortcomings of the prior art when unloading data for the data warehouse mainly include:

[0067] The business components are bound to specific databases, which causes the data unloading function to be almost paralyzed when the database is changed; many business components are disconnected from the enterprise-level data dictionary, which causes the data to be unable to be loaded into the data warehouse when unloaded to the data warehouse; some open source data export software (for example, the open source data export software Sqluldr) lacks high-performance concurrent data unloading functions, is more suitable for small data volume Oracle databases, and the storage process of the data warehouse is bound to the Oracle database, and the portability is poor.

[0068] The enterprise-level data unloading method provided by the present application aims to solve the above technical problems of the prior art. The enterprise-level data unloading method can be applied to the data unloading scene of enterprise-level data.

[0069] The technical solutions of the present application and how the technical solutions of the present application solve the above technical problems will be described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes can not be described in detail in some embodiments. The embodiments of the present application will be described below with reference to the accompanying drawings.

[0070] Figure 1 is a flowchart of an enterprise-level data unloading method provided by an embodiment of the present application, as shown in Figure 1 The method comprises the following steps.

[0071] S101, obtaining the source data group in the source data layer of the data warehouse.

[0072] S102, Determine the enterprise-level data dictionary followed by the above-mentioned source data group.

[0073] S103, obtain the application data version of the business components in the business system.

[0074] S104, based on the application data version and the enterprise-level data dictionary, unload the enterprise-level data to the source data group to make the data types of the business components consistent with those of the source data group.

[0075] It should be noted that the data offloading method for enterprise-level data provided in this embodiment of the invention specifically provides a data offloading implementation scheme that is independent of a specific database. That is, the data offloading implementation scheme involved in this application is not bound to a specific database product, and can directly realize the offloading of enterprise-level data from business components to the source data group in the data warehouse.

[0076] Optionally, in this embodiment of the application, the business components in the above-mentioned business system are business components based on the Online Transaction Processing (OLTP) type, that is, the user data received by the front end can be immediately transmitted to the computing center for processing and the processing result can be given in a very short time, which is one of the ways to respond quickly to user operations.

[0077] Optionally, in this embodiment of the application, the data offloading scheme can be understood as a scheme to provide (e.g., data replication, data synchronization) the table structure and table data in each business component of the OLTP type to the data warehouse based on the data transmission protocol.

[0078] In this embodiment, the source data layer can collect and aggregate data from various business systems, retain the original business process data as much as possible, keep it basically consistent with the business system, and only perform simple integration, unstructured data structuring, or add identification data, etc., without performing deep cleaning and processing, that is, store it in the source data group in the source data layer.

[0079] For example, a data warehouse acts as a data buffer. The goal of the source data layer in a data warehouse is to aggregate enterprise-level data (e.g., all of the enterprise's raw data) into the data warehouse in order to prepare for the construction of subsequent unified data warehouse layers, tagged data layers, and application data layers in the data layering process.

[0080] Optionally, the aforementioned enterprise-level data dictionary can be understood as a management system for all domains, data items, and physical models used in data governance during the enterprise development process.

[0081] By determining the enterprise-level data dictionary followed by the aforementioned source data group, and ensuring that the business system also adopts the same enterprise-level data dictionary, the source data groups of the business system and the data warehouse both follow the enterprise-level data dictionary. This guarantees data type consistency and prevents the business components from becoming disconnected from the enterprise-level data dictionary.

[0082] By obtaining the application data version of the business component (for example, to improve efficiency, the business component can be a core business component in the business system), and based on the application data version, obtaining enterprise-level data with the same data type as the source data group from the enterprise-level data dictionary, the business component and the data warehouse are made consistent during the design phase. This avoids the technical problem of data not being able to be loaded into the data warehouse due to subsequent data type inconsistencies.

[0083] Therefore, the embodiments of this application can solve the problems of data offloading transition relying on specific databases and the disconnect between business components and enterprise-level data dictionaries in the prior art, realize the technical effect of data offloading transition no longer relying on specific databases, and ensure the consistency of data types between the source data groups of business components and data warehouses based on enterprise-level data dictionaries.

[0084] According to one or more embodiments of this application, Figure 2 This is a flowchart illustrating an optional enterprise-level data offloading method provided in an embodiment of the present invention, as shown below. Figure 2 As shown, based on the application data version and the enterprise-level data dictionary, the enterprise-level data is unloaded from the source data group, including:

[0085] S201, based on the application data version mentioned above, obtain enterprise-level data from the enterprise-level data dictionary that is consistent with the data type of the source data group mentioned above.

[0086] S202, using Structured Query Language to run the data unloading program to unload the enterprise-level data from the aforementioned business systems to the aforementioned data warehouse.

[0087] In this embodiment of the application, enterprise-level data with the same data type as the source data group is obtained from the enterprise-level data dictionary according to the application data version. This ensures that the business components and the data warehouse are consistent during the design phase, thus avoiding the technical problem of data not being able to be loaded into the data warehouse due to subsequent data type inconsistencies.

[0088] Furthermore, in this embodiment, not only are the business components and the data warehouse designed to be consistent, but subsequent process control can be adopted. Upstream data changes and application version upgrades must be carried out only after the downstream is notified and aware of the changes, thereby achieving data collaboration and avoiding technical problems that prevent data from being loaded into the data warehouse.

[0089] This application embodiment can also realize the unloading of enterprise-level data on a low-code development platform with a small amount of code. Specifically, the data unloading program is run using the Structured Query Language (SQL) standard, and the data unloading program is designed based on the SQL standard rather than the database standard, without the need to be bound to a specific database.

[0090] In one example, the unloading of the enterprise-level data from the aforementioned business system to the aforementioned data warehouse includes:

[0091] S301, obtain the last update timestamp of the above enterprise-level data.

[0092] S302, based on the last update timestamp, use streaming processing to unload the enterprise-level data from the business system to the data warehouse.

[0093] Optionally, in this embodiment, the data offloading scheme implemented based on the data extraction method can adopt a streaming processing approach. Based on the last update timestamp of the enterprise-level data, new enterprise-level data can be started from the business system and unloaded into the aforementioned data warehouse. For example, a cursor can be used in a Java Database Connectivity (JDBC) to control and implement forced extraction.

[0094] In an optional embodiment, the method further includes:

[0095] Customize the structured query language and the output format of the enterprise-level data.

[0096] In addition, in this embodiment of the application, the naming and data type of the unloaded enterprise-level data can also be determined using the Structured Query Language (SQL).

[0097] In another example, Figure 3 This is a flowchart illustrating an optional enterprise-level data offloading method provided in an embodiment of the present invention, as shown below. Figure 3 As shown, the unloading of the enterprise-level data from the aforementioned business system to the aforementioned data warehouse includes:

[0098] S401, Obtain the component characteristic information of the above-mentioned business components.

[0099] S402, Obtain the pre-determined data interfaces of the aforementioned data warehouse and the aforementioned business system.

[0100] S403, Based on the aforementioned component feature information and the aforementioned data interface, the aforementioned enterprise-level data is unloaded from the aforementioned business system to the aforementioned data warehouse.

[0101] Based on the component characteristic information of each business component, namely the characteristics of the component itself, and the data interfaces pre-agreed upon by the data warehouse and business system, customized offloading processing of enterprise-level data is performed, which has excellent scalability. In addition, in this embodiment, the SQL for extracting data and the output format can also be customized and tailored.

[0102] Using the embodiments of this application, under normal circumstances, business components do not need to be modified to achieve full table and full field output, as well as uniformly formatted strings, based on the data transmission protocol that should be followed during the data unloading process.

[0103] In this embodiment, the data interface design for unloading data is highly abstract and flexible. For example, based on the data unloading scheme implemented using the data extraction method or the data unloading method, the data interface can be set as both a data extraction interface and a data unloading interface.

[0104] According to one or more embodiments of this application, the above method further includes:

[0105] S601, when generating the above data interface, the default processing rules of the above data interface are automatically generated, wherein the above default processing rules are used to characterize the use of the original field or format by default.

[0106] S602, for different business components mentioned above, special processing rules are generated for the data interface mentioned above. The special processing rules are used to modify or delete fields in the data interface mentioned above.

[0107] Optionally, both data extraction and data unloading can have default and custom implementations. That is, certain fields can be specially processed or deleted for the data interface. The default processing rules are used to indicate that the original fields or formats are used by default and are automatically generated when the business system code is generated. The special processing rules refer to the modifications made according to the individual business components.

[0108] As an optional implementation, the data unloading process can be implemented concurrently using a partitioning strategy.

[0109] In another alternative embodiment, different templates can be provided for each specific database product, and different algorithms can generate personalized parts of different databases.

[0110] This application's embodiments start from the data lifecycle, integrating upstream and downstream processes to ensure that the specifications are strongly implemented in the functional code; furthermore, considering the diversity of product architectures, it is not bound to specific database products, enabling differentiated sales and implementation at minimal cost, and also freeing it from dependence on specific databases; considering the large scale of enterprise development and the varying skill levels of developers, most functions are implemented by default, requiring only some customization of business logic.

[0111] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0112] According to one or more embodiments of this application, a data offloading device for enterprise-level data is provided. Figure 4 A structural block diagram of an enterprise-level data offloading device provided in this application embodiment is shown below. Figure 4 As shown, the above-mentioned device includes:

[0113] The first acquisition module 401 is used to acquire the patch source data group in the data warehouse;

[0114] Module 402 is used to determine the enterprise-level data dictionary followed by the above-mentioned source data group;

[0115] The second acquisition module 403 is used to acquire the application data version of the business components in the business system;

[0116] The data unloading module 404 is used to unload enterprise-level data to the above-mentioned source data group according to the above-mentioned application data version and the above-mentioned enterprise-level data dictionary, so as to make the data types of the above-mentioned business components consistent with the above-mentioned source data group.

[0117] According to one or more embodiments of this application, the data offloading module described above includes:

[0118] The acquisition unit is used to acquire enterprise-level data with the same data type as the above-mentioned source data group from the above-mentioned enterprise-level data dictionary according to the above-mentioned application data version.

[0119] The unloading unit is used to run a data unloading program using a structured query language to unload the enterprise-level data from the aforementioned business systems to the aforementioned data warehouse.

[0120] According to one or more embodiments of this application, the unloading unit includes:

[0121] The first acquisition submodule is used to acquire the component feature information of the aforementioned business components;

[0122] The second acquisition submodule is used to acquire the data interfaces of the aforementioned data warehouse and the aforementioned business system that have been predetermined.

[0123] The uninstallation submodule is used to uninstall the enterprise-level data from the above business system to the above data warehouse based on the above component feature information and the above data interface.

[0124] According to one or more embodiments of this application, the above-described apparatus further includes:

[0125] The custom module is used to customize the structured query language and the output format of the enterprise-level data.

[0126] According to one or more embodiments of this application, the above-mentioned unloading submodule is further configured to obtain the last update timestamp of the above-mentioned enterprise-level data; and, based on the last update timestamp, use a streaming processing method to unload the above-mentioned enterprise-level data from the above-mentioned business system to the above-mentioned data warehouse.

[0127] According to one or more embodiments of this application, the data interface includes: a data extraction interface and a data unloading interface, and the apparatus further includes:

[0128] The first generation module is used to automatically generate the default processing rules for the aforementioned data interface when generating the aforementioned data interface.

[0129] The first generation module is used to customize and generate special processing rules for the data interfaces of the above-mentioned business components. The special processing rules are used to modify or delete fields in the data interfaces.

[0130] In an exemplary embodiment, this application also provides an electronic device, including: a processor, and a memory connected to the processor;

[0131] The aforementioned memory stores instructions executed by the computer;

[0132] The processor executes computer execution instructions stored in the memory to implement any of the methods described above.

[0133] In an exemplary embodiment, this application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the methods described above.

[0134] In an exemplary embodiment, this application also provides a computer program product, including a computer program that, when executed by a processor, implements any of the methods described above.

[0135] To implement the above embodiments, this application also provides an electronic device.

[0136] refer to Figure 5The diagram illustrates a structural schematic of an electronic device 700 suitable for implementing embodiments of this application. The electronic device 700 can be a terminal device or a server. The terminal device can include, but is not limited to, mobile terminals such as mobile phones, laptops, digital radio receivers, personal digital assistants (PDAs), portable Android devices (PADs), portable media players (PMPs), and in-vehicle terminals (e.g., in-vehicle navigation terminals), as well as fixed terminals such as digital TVs and desktop computers. Figure 5 The electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0137] like Figure 5 As shown, the electronic device 700 may include a processing unit (e.g., a central processing unit, a graphics processor, etc.) 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage device 708 into a random access memory (RAM) 703. The RAM 703 also stores various programs and data required for the operation of the electronic device 700. The processing unit 701, ROM 702, and RAM 703 are interconnected via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0138] Typically, the following devices can be connected to I / O interface 705: input devices 706 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 707 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 708 including, for example, magnetic tapes, hard disks, etc.; and communication devices 709. Communication device 709 allows electronic device 700 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 5 An electronic device 700 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.

[0139] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application 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 communication device 709, or installed from storage device 708, or installed from ROM 702. When the computer program is executed by processing device 701, it performs the functions defined in the methods of embodiments of this application.

[0140] It should be noted that the computer-readable medium described above in this application can be a computer-readable signal medium, a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor 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 this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution device or apparatus. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may 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 device or apparatus. 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.

[0141] 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.

[0142] The aforementioned computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to perform the methods shown in the above embodiments.

[0143] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof. These programming languages ​​include 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).

[0144] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of methods and computer program products according to various embodiments of this application. 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 the 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.

[0145] The units described in the embodiments of this application can be implemented in software or in hardware. The name of a unit does not necessarily limit the unit itself; for example, the first acquisition unit can also be described as "a unit that acquires at least two Internet Protocol addresses".

[0146] 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.

[0147] In the context of this application, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution apparatus or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor device or device, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

Claims

1. A method for data offloading of enterprise data, the method comprising: The method comprises the following steps: obtaining a data set in a data source layer of a data warehouse; determining an enterprise-level data dictionary followed by the data set, wherein the enterprise-level data dictionary is a management system for all domains, data items and physical models used in data governance in the enterprise development process; obtaining an application data version of a business component in a business system; uninstalling enterprise-level data to the data set according to the application data version and the enterprise-level data dictionary, so that the data types of the business component and the data set are consistent; the step of uninstalling enterprise-level data to the data set according to the application data version and the enterprise-level data dictionary comprises: obtaining enterprise-level data consistent with the data type of the data set from the enterprise-level data dictionary according to the application data version; and running a data uninstallation program by using a structured query language to uninstall the enterprise-level data from the business system to the data warehouse.

2. The method of claim 1, wherein, the step of uninstalling the enterprise-level data from the business system to the data warehouse comprises: obtaining component feature information of the business component; obtaining a data interface predetermined by the data warehouse and the business system; uninstalling the enterprise-level data from the business system to the data warehouse according to the component feature information and the data interface.

3. The method of claim 1, wherein, The method further comprises: customizing the structured query language and the output format of the enterprise-level data.

4. The method of claim 2, wherein, the step of uninstalling the enterprise-level data from the business system to the data warehouse comprises: obtaining a last update timestamp of the enterprise-level data; uninstalling the enterprise-level data from the business system to the data warehouse by using a streaming processing mode according to the last update timestamp.

5. The method of claim 2, wherein, The data interface comprises an extraction data interface and an uninstallation data interface, and the method further comprises: generating a default processing rule of the data interface automatically when the data interface is generated, wherein the default processing rule is used to represent that the original field or format is used by default; generating a special processing rule of the data interface for different business components, wherein the special processing rule is used to modify or delete fields in the data interface.

6. An apparatus for data offloading of enterprise data, the apparatus comprising: The device comprises: a first obtaining module for obtaining a data set in a data warehouse; a determining module for determining an enterprise-level data dictionary followed by the data set, wherein the enterprise-level data dictionary is a management system for all domains, data items and physical models used in data governance in the enterprise development process; a second obtaining module for obtaining an application data version of a business component in a business system; a data uninstallation module for uninstalling enterprise-level data to the data set according to the application data version and the enterprise-level data dictionary, so that the data types of the business component and the data set are consistent; the data uninstallation module comprises: an obtaining unit for obtaining enterprise-level data consistent with the data type of the data set from the enterprise-level data dictionary according to the application data version; An unloading unit is configured to run a data unloading program in a structured query language to unload the enterprise-level data from the business system to the data warehouse.

7. An electronic device, comprising: The method comprises: a processor, and a memory connected to the processor; the memory stores computer-executed instructions; the processor executes the computer-executed instructions stored in the memory to implement the method according to any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executed instructions, and the computer-executed instructions are executed by the processor to implement the method according to any one of claims 1 to 5.

9. A computer program product, characterised in that, The computer program is executed by the processor to implement the method according to any one of claims 1 to 5.

Images