Granted Patent B2

US 12,602,392 · App. 17/670,896 · Granted Apr 14, 2026

Inventor: Dirk Renick (Albany, CA)

Assignee: Insight Direct USA, Inc.

G06F16/254G06F16/2358G06F16/258G06F21/604G06F21/6218

Abstract

Claims (106)

1 . A method of ingesting data into a data lake, the method comprising:

consolidating pre-entered metadata enabling an identification of multiple data sources of multiple data pipelines, and a connection to each of the multiple data sources, into a common metadata table for an overarching data pipeline prior to initiating the overarching data pipeline, wherein the pre-entered metadata of the metadata table includes values associated with each of the multiple data sources that specify, for each of the multiple data sources, at least one of:

a data source identification;

a data source name;

whether a respective one of the multiple data sources is enabled; and

a key value that is associated with access credentials for the respective one of the multiple data sources;

initiating, by a computer device, the overarching data pipeline by performing a lookup activity, the lookup activity including querying the metadata table that includes the pre-entered metadata, wherein the querying specifies a plurality of data sources from among the multiple data sources;

creating an overarching pipeline start log corresponding to a start of the overarching data pipeline when the overarching data pipeline is initiated;

retrieving, based on the querying, respective metadata from the metadata table that corresponds to the specified plurality of data sources of the multiple data sources; and

performing, by the computer device, a sequence of activities for each data source of the specified plurality of data sources, the sequence of activities including:

creating a data source pipeline start log corresponding to a start of the sequence of activities for a respective one of the specified plurality of data sources before forming a connection to the respective one of the specified plurality of data sources;

connecting to the respective one of the specified plurality of data sources using a portion of the metadata from the metadata table that corresponds to the respective one of the specified plurality of data sources to form the connection to the respective one of the specified plurality of data sources by:

providing connection information to a linked services module based on the portion of the metadata from the metadata table that corresponds to the respective one of the specified plurality of data sources;

forming the connection to the respective one of the specified plurality of data sources via the linked services module;

connecting, via the linked services module, to a secure storage that contains the associated access credentials for the respective one of the specified plurality of data sources;

obtaining the access credentials for the respective one of the specified plurality of data sources from the secure storage by passing the key value to the secure storage via the linked services module; and

using the access credentials for the respective one of the specified plurality of data sources in forming the connection to the respective one of the specified plurality of data sources via the linked services module;

accessing, from the respective one of the specified plurality of data sources via the connection, a data object specified by the portion of the metadata that corresponds to the respective one of the specified plurality of data sources; and

storing the data object in the data lake, the data lake being remote from each of the multiple data sources;

creating a data source pipeline end log corresponding to an end of the sequence of activities for the respective one of the specified plurality of data sources when the data object is stored in the data lake; and

creating an overarching data pipeline end log corresponding to an end of the overarching data pipeline after the sequence of activities has been performed for each of the specified plurality of data sources.

2 . The method of claim 1 , wherein initiating the overarching data pipeline further comprises initiating the overarching data pipeline manually by passing arguments to parameters of the overarching data pipeline at a runtime of the overarching data pipeline.

3 . The method of claim 1 , wherein initiating the overarching data pipeline further comprises initiating the overarching data pipeline by scheduling an instance of the overarching data pipeline to occur automatically after a defined period elapses or after an occurrence of a trigger event.

4 . The method of claim 1 , wherein connecting to the respective one of the specified plurality of data sources further comprises:

connecting to a secure storage that contains access credentials for the respective one of the specified plurality of data sources;

obtaining the access credentials for the respective one of the specified data sources from the secure storage; and

using the access credentials for the respective one of the specified plurality of data sources in forming the connection to the respective one of the specified plurality of data sources.

5 . The method of claim 1 and further comprising:

transforming the data object from the data lake into a different format such that the data object is compatible with a different database.

6 . The method of claim 1 , wherein the data structure is stored in an SQL database.

7 . The method of claim 1 , wherein the pre-entered metadata of the metadata table further includes values associated with each of the multiple data sources that specify, for each of the multiple data sources, at least one of:

a data object name; and

a last execution date.

8 . The method of claim 1 , wherein storing the data object in the data lake further comprises incorporating values from the portion of the metadata that corresponds to the respective one of the specified plurality of data sources into a file name of the data object to enable identifying the data object in the data lake.

9 . The method of claim 8 , wherein the file name of the data object includes at least one of:

a data source name that corresponds to the respective one of the specified plurality of data sources; and

a data object name that corresponds to the data object in the respective one of the specified plurality of data sources.

10 . The method of claim 1 , wherein storing the data object in the data lake further comprises storing the data object in a Parquet format.

11 . The method of claim 10 and further comprising:

transforming the data object from the Parquet format into a different format such that the data object is compatible with a different database that is separate from the data lake.

12 . The method of claim 1 , wherein storing the data object in the data lake further comprises creating a copy of the data object from the respective one of the specified plurality of data sources and storing the copy of the data object in the data lake.

13 . The method of claim 12 , wherein storing the copy of the data object in the data lake further comprises writing the copy of the data object to a container within the data lake, the container being a destination for respective copies of data objects accessed from each of the specified plurality of data sources.

14 . The method of claim 13 , wherein writing the copy of the data object to the container within the data lake further comprises incorporating values from the portion of the metadata that corresponds to the respective one of the specified plurality of data sources into a file name of the copy of the data object to enable identifying the copy of the data object in the data lake.

15 . The method of claim 1 , wherein storing the data object in the data lake further comprises writing the data object to a container within the data lake, the container being a destination for respective data objects accessed from each of the specified plurality of data sources.

16 . The method of claim 1 and further comprising:

storing the overarching data pipeline start log and the overarching data pipeline end log in a log table on a database.

17 . The method of claim 16 and further comprising sending a notification corresponding to the end of the overarching data pipeline after the sequence of activities has been performed for each of the specified plurality of data sources, wherein the notification is an email.

18 . The method of claim 1 and further comprising:

storing the data source pipeline start log and the data source pipeline end log for each of the specified plurality of data sources in a log table on a database.

19 . The method of claim 1 and further comprising:

creating an error log and sending a notification if an error occurs while initiating the overarching data pipeline or while performing the sequence of activities, wherein the notification is an email; and

storing the error log in a log table on a database.

20 . The method of claim 1 , wherein the data object comprises a new or updated portion of data stored in the respective one of the specified plurality of data sources.

21 . The method of claim 20 , wherein storing the data object in the data lake further comprises creating a copy of the new or updated portion of the data from the respective one of the specified plurality of data sources and storing the copy in the data lake.

22 . The method of claim 21 , wherein storing the copy in the data lake further comprises writing the copy to a container within the data lake, the container being a destination for respective copies of new or updated portions of data accessed from each of the specified plurality of data sources.

23 . The method of claim 22 , wherein writing the copy to the container within the data lake further comprises incorporating values from the portion of the metadata that corresponds to the respective one of the specified plurality of data sources into a file name of the copy to enable identifying the copy in the data lake.

24 . A method of ingesting data into a data lake, the method comprising:

consolidating pre-entered metadata enabling an identification of multiple data sources of multiple data pipelines, and a connection to each of the multiple data sources, into a common metadata table for an overarching data pipeline prior to initiating the overarching data pipeline, wherein the pre-entered metadata of the metadata table includes values associated with each of the multiple data sources that specify, for each of the multiple data sources, at least one of:

a data source identification;

a data source name;

whether a respective one of the multiple data sources is enabled; and

a key value that is associated with access credentials for the respective one of the multiple data sources;

initiating, by a computer device, the overarching data pipeline by performing a lookup activity, the lookup activity including querying the metadata table that includes the pre-entered metadata, wherein the querying specifies at least one attribute of a plurality of data sources of the multiple data sources;

creating an overarching pipeline start log corresponding to a start of the overarching data pipeline when the overarching data pipeline is initiated;

retrieving, based on the querying, respective metadata from the metadata table that corresponds to the specified plurality of data sources of the multiple data sources corresponding to the at least one attribute; and

performing, by the computer device, a sequence of activities for each data source of the specified plurality of data sources, the sequence of activities including:

creating a data source pipeline start log corresponding to a start of the sequence of activities for a respective one of the specified plurality of data sources before forming a connection to the respective one of the specified plurality of data sources;

connecting to the respective one of the specified plurality of data sources using a portion of the metadata from the metadata table that corresponds to the respective one of the specified plurality of data sources to form the connection to the respective one of the specified plurality of data sources by:

providing connection information to a linked services module based on the portion of the metadata that corresponds to the respective one of the specified plurality of data sources;

forming the connection to the respective one of the specified plurality of data sources via the linked services module;

connecting, via the linked services module, to a secure storage that contains the associated access credentials for the respective one of the specified plurality of data sources;

obtaining the access credentials for the respective one of the specified plurality of data sources from the secure storage by passing the key value to the secure storage via the linked services module; and

using the access credentials for the respective one of the specified plurality of data sources in forming the connection to the respective one of the specified plurality of data sources via the linked services module;

accessing, from the respective one of the specified plurality of data sources via the connection, a data object specified by the portion of the metadata that corresponds to the respective one of the specified plurality of data sources; and

storing the data object in the data lake, the data lake being remote from each of the multiple data sources;

creating a data source pipeline end log corresponding to an end of the sequence of activities for the respective one of the specified plurality of data sources when the data object is stored in the data lake; and

creating an overarching pipeline end log corresponding to an end of the overarching data pipeline after the sequence of activities has been performed for each of the specified plurality of data sources.

25 . The method of claim 24 and further comprising:

configuring the overarching data pipeline to be initiated manually by passing arguments to parameters of the overarching data pipeline at a runtime of the overarching data pipeline; or

configuring the overarching data pipeline to be initiated by scheduling an instance of the overarching data pipeline to occur automatically after a defined period elapses or after an occurrence of a trigger event.

26 . The method of claim 24 and further comprising:

defining a first connection to a database that stores the metadata table via a linked services module; and

defining a second connection to the data lake via the linked services module.

27 . A data pipeline system for ingesting data into cloud storage, the system comprising:

one or more processors; and

computer-readable memory encoded with instructions that, when executed by the one or more processors, cause the data pipeline system to:

consolidate pre-entered metadata enabling an identification of multiple data sources of multiple data pipelines, and a connection to each of the multiple data sources, into a common metadata table for an overarching data pipeline prior to initiating the overarching data pipeline, wherein the pre-entered metadata of the metadata table includes values associated with each of the multiple data sources that specify, for each of the multiple data sources, at least one of:

a data source identification;

a data source name;

whether a respective one of the multiple data sources is enabled; and

a key value that is associated with access credentials for the respective one of the multiple data sources;

initiate the overarching data pipeline by performing a lookup activity, the lookup activity including querying the metadata table that includes the pre-entered metadata, wherein the querying specifies a plurality of data sources of the multiple data sources;

create an overarching pipeline start log corresponding to a start of the overarching data pipeline when the overarching data pipeline is initiated;

retrieve, based on the querying, metadata that corresponds to the specified plurality of data sources of the multiple data sources; and

perform a sequence of activities for each data source of the specified data sources, the sequence of activities including:

creating a data source pipeline start log corresponding to a start of the sequence of activities for a respective one of the specified plurality of data sources before forming a connection to the respective one of the specified plurality of data sources;

connecting to the respective one of the specified plurality of data sources using a portion of the metadata from the metadata table that corresponds to the respective one of the specified plurality of data sources to form the connection to the respective one of the specified data sources by:

providing connection information to a linked services module based on the portion of the metadata that corresponds to the respective one of the specified data sources;

forming the connection to the respective one of the specified data sources via the linked services module;

connecting, via the linked services module, to a secure storage that contains the associated access credentials for the respective one of the specified plurality of data sources;

obtaining the access credentials for the respective one of the specified plurality of data sources from the secure storage by passing the key value to the secure storage via the linked services module; and

using the access credentials for the respective one of the specified plurality of data sources in forming the connection to the respective one of the specified plurality of data sources via the linked services module;

accessing, from the respective one of the specified plurality of data sources via the connection, a data object specified by the portion of the metadata that corresponds to the respective one of the specified plurality of data sources; and

storing the data object in the data lake, the data lake being remote from each of the multiple data sources;

creating a data source pipeline end log corresponding to an end of the sequence of activities for the respective one of the specified plurality of data sources when the data object is stored in the data lake; and

create an overarching pipeline end log corresponding to an end of the overarching data pipeline after the sequence of activities has been performed for each of the specified plurality of data sources.

Assignments (1)

Continuity (1)

References Cited (123)