SUPPORTING COMBINATION OF FLOW BASED ETL AND ENTITY RELATIONSHIP BASED ETL

• US 20140344211A1
• Filed: 10/02/2013
• Published: 11/20/2014
• Est. Priority Date: 05/17/2013
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Allan, David, Lau, Kwok-hung (Thomas), Gong, Yu (Jeff)
• Granted Patent: US 10,216,814 B2
• Time in Patent Office: Days
• US Class Current: 707/602
• CPC Class Codes: G06F 16/254 Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06F 8/433 Dependency analysis; Data or control flow analysis

Abstract

A data integration system is disclosed that incorporates one or more techniques for eases the design and maintenance of a mapping. As components are added to an existing design, the data integration system removes the need to specify all input and output attributes. In one aspect, components types are implement that allow entity relationships to be added and/or edited in a flow view of a logical design. Therefore, attributes of components representing datasets can be added and propagated to downstream components with minimal effort on the part of a map designer.

Claims

1. A method facilitating generation of a data mapping, the method comprising:

receiving, at the one or more computer systems, information specifying a set of entity relationships as a component of the logical design;

determining, with one or more processors associated with the one or more computer systems, an equivalent data flow model based on the set of entity relationships; and

generating, with the one or more processors associated with the one or more computer systems, information indicative of the equivalent data flow model in the logical flow design.

2. The method of claim 1 further comprising deriving one or more attributes of a dataset representing the set of entity relationships based on information declaring relationships between attributes of data sources.

3. The method of claim 1 further comprising receiving information specifying one or more components of the logical design that includes information indicative of an operation that changes shape of the information flowing through the logical design.

4. The method of claim 1 further comprising receiving information specifying one or more components of the logical design that includes information indicative of an operation that controls the flow of information flowing through the logical design but does not change shape of the information flowing through the logical design.

5. The method of claim 1 further comprising receiving information specifying one or more components of the logical design that includes information indicative of a target component having one or more attributes of data to be stored in a target datastore.

6. The method of claim 1 wherein generating the information indicative of the equivalent data flow model in the logical flow design comprises exporting a list of attributes to a downstream component.

7. The method of claim 1 further comprising:

receiving, at the one or more computer systems, a change in the logical design through the introduction of one or more relationships; and

determining, with the one or more processors associated with the one or more computer systems, an updated equivalent data flow model.

8. A non-transitory computer-readable medium storing computer-executable code for facilitating generation of a data mapping, the non-transitory computer-readable medium comprising:

code for receiving information specifying a set of entity relationships as a component of the logical design;

code for determining an equivalent data flow model based on the set of entity relationships; and

code for generating information indicative of the equivalent data flow model in the logical flow design.

9. The non-transitory computer-readable medium of claim 8 further comprising code for deriving one or more attributes of a dataset representing the set of entity relationships based on information declaring relationships between attributes of data sources.

10. The non-transitory computer-readable medium of claim 8 further comprising code for receiving information specifying one or more components of the logical design that includes information indicative of an operation that changes shape of the information flowing through the logical design.

11. The non-transitory computer-readable medium of claim 8 further comprising code for receiving information specifying one or more components of the logical design that includes information indicative of an operation that controls the flow of information flowing through the logical design but does not change shape of the information flowing through the logical design.

12. The non-transitory computer-readable medium of claim 8 further comprising code for receiving information specifying one or more components of the logical design that includes information indicative of a target component having one or more attributes of data to be stored in a target datastore.

13. The non-transitory computer-readable medium of claim 8 wherein the code for generating the information indicative of the equivalent data flow model in the logical flow design comprises code for exporting a list of attributes to a downstream component.

14. The non-transitory computer-readable medium of claim 8 further comprising:

code for receiving a change in the logical design through the introduction of one or more relationships; and

code for determining an updated equivalent data flow model.

15. A system facilitating generation of a data mapping, the system comprising:

a processor; and

a memory storing instructions which when executed by the processor configure the processor to;

receive information specifying a set of entity relationships as a component of the logical design;

determine an equivalent data flow model based on the set of entity relationships; and

generate information indicative of the equivalent data flow model in the logical flow design.

16. The system of claim 15 wherein the processor is further configured to derive one or more attributes of a dataset representing the set of entity relationships based on information declaring relationships between attributes of data sources.

17. The system of claim 15 wherein the processor is further configured to receive information specifying one or more components of the logical design that includes information indicative of an operation that changes shape of the information flowing through the logical design.

18. The system of claim 15 wherein the processor is further configured to receive information specifying one or more components of the logical design that includes information indicative of an operation that controls the flow of information flowing through the logical design but does not change shape of the information flowing through the logical design.

19. The system of claim 15 wherein the processor is further configured to receive information specifying one or more components of the logical design that includes information indicative of a target component having one or more attributes of data to be stored in a target datastore.

20. The system of claim 15 wherein to generate the information indicative of the equivalent data flow model in the logical flow design the processor is configured to export a list of attributes to a downstream component.

21. The system of claim 15 wherein the processor is further configured to:

receive a change in the logical design through the introduction of one or more relationships; and

determine an updated equivalent data flow model.