Granted Patent B2

US 12,210,532 · App. 17/011,847 · Granted Jan 28, 2025

Inventors: Aaron David Colcord (Mequon, WI); Kevin Richard Mellott (Muskego, WI); David Vincente Favela (Penngrove, CA); Jeffrey Chee-Keong Neong (Windsor, CA)

Assignee: Fidelity Information Services, LLC

G06F16/2457G06F9/3005G06F9/3867G06F9/541G06F9/544G06F16/211G06F16/221G06F16/24573G06F16/2465G06F16/2471G06F16/285G06F21/31G06F21/54G06F21/602G06F21/6227G06F21/6254G06F2221/2141

Abstract

Claims (78)

1. A data analytics system comprising:

at least one processor; and

at least one non-transitory computer-readable medium containing instructions that, when executed by the at least one processor cause the data analytics system to perform operations comprising:

receiving, at a first storage location, input data;

configuring a flow service to execute a flow, flow execution comprising:

creating a pipeline using the flow and metadata associated with the flow, the pipeline configured to perform a data transformation specified in the flow;

extracting, by the pipeline, identifying characteristics of the input data from the input data;

providing the identifying characteristics of the input data to an identity service;

receiving, from the identity service, a tenancy identifier associated with the input data using the flow, the tenancy identifier associated with the input data representing an ownership of the input data;

generating output data from the input data by performing the data transformation on the input data using the pipeline;

storing, using the pipeline, the output data in a second storage location associated with the tenancy identifier;

creating a tenancy object for the output data which is generated by performing the data transformation on the input data, based on the tenancy identifier associated with the input data received from the identify service, the tenancy object for the output data representing an ownership of the output data;

storing the tenancy object created for the output data in a metadata repository according to a hierarchical data object ownership graph which comprises a plurality of tenancy objects arranged as parent objects and child objects, wherein the storing the tenancy object including associating the tenancy object created for the output data with a parent object in the hierarchical data object ownership graph; and

determining whether to authorize a request to display at least a portion of the output data based at least in part on the association between the tenancy object and the parent object in the hierarchical data object ownership graph.

2. The data analytics system of claim 1 , wherein:

the tenancy is determined during execution of the pipeline based on values of a specified column in the input data, the column specified in the flow.

3. The data analytics system of claim 2 , wherein:

records in the input dataset have different values of the specified column;

the pipeline generates multiple output datasets, each data set corresponding to one of the different values; and

the pipeline stores each of the multiple output datasets in locations corresponding to differing tenancies.

4. The data analytics system of claim 1 , wherein:

the configuring a flow service to execute a flow comprises obtaining the metadata associated with the flow; and

wherein the execution of the flow depends on the obtained metadata.

5. The data analytics system of claim 4 , wherein:

the metadata specifies a schema of the input data or rules for associating semantics with the input data.

6. The data analytics system of claim 1 , wherein:

the configuring a flow service to execute a flow comprises obtaining an artifact implementing the data transformation; and executing the flow comprises executing the artifact.

7. The data analytics system of claim 6 , wherein:

the artifact comprises a script, executable binary, or module.

8. The data analytics system of claim 1 , wherein:

the flow comprises a JSON or YAML object.

9. The data analytics system of claim 1 , wherein:

the flow specifies that the output data can be accessed using at least one of GraphQL, SOAP, Odata, or OpenAPI.

10. The data analytics system of claim 1 , wherein:

an append-only data store includes the first storage location; and

a data-lake includes the second location.

11. A data analytics method comprising:

receiving, at a first storage location, input data;

configuring a flow service to execute a flow, flow execution comprising:

obtaining metadata associated with the flow, the metadata specifying a schema of the input data or rules for associating semantics with the input data;

creating a pipeline using the flow and the metadata associated with the flow, the pipeline configured to perform a data transformation specified in the flow and execution of the flow dependent on the obtained metadata;

determining a tenancy associated with the input data using the flow, the tenancy associated with the input data representing an ownership of the input data, and the determining comprising:

extracting identifying characteristics of the input data from the input data;

providing the identifying characteristics of the input data to an identity service; and

receiving a tenancy identifier of the input data from the identity service;

generating output data from the input data by performing the data transformation on the input data using the pipeline;

storing, using the pipeline, the output data in a second storage location associated with the tenancy;

creating a tenancy object for the output data which is generated by performing the data transformation on the input data, based on the tenancy identifier of the input data received from the identity service, the tenancy object for the output data representing an ownership of the output data;

storing the tenancy object created for the output data in a metadata repository according to a hierarchical data object ownership graph which comprises a plurality of tenancy objects arranged as parent objects and child objects, wherein the storing the tenancy object including associating the tenancy object created for the output data with a parent object in the hierarchical data object ownership graph; and

determining whether to authorize a request to display at least a portion of the output data based at least in part on the association between the tenancy object and the parent object in the hierarchical data object ownership graph.

12. The data analytics method of claim 11 , wherein:

the tenancy is determined during execution of the pipeline based on values of a specified column in the input data, the column specified in the flow;

records in the input dataset have different values of the specified column;

the pipeline generates multiple output datasets, each data set corresponding to one of the different values; and

the pipeline stores each of the multiple output datasets in locations corresponding to differing tenancies.

13. The data analytics method of claim 11 , wherein:

configuring a flow service to execute a flow comprises obtaining an artifact implementing the data transformation; and executing the flow comprises executing the artifact, wherein the artifact comprises a script, executable binary, or module.

14. The data analytics method of claim 11 , wherein:

the flow comprises a JSON or YAML object.

15. The data analytics method of claim 11 , wherein:

the flow specifies that the output data can be accessed using at least one of GraphQL, SOAP, Odata, or OpenAPI.

16. The data analytics method of claim 11 , wherein:

an append-only data store includes the first storage location; and

a data-lake includes the second location.

17. A data analytics method comprising:

receiving, at a first storage location, input data;

configuring a flow service to execute a flow, the flow comprises a JSON or YAML object and specifies that output data generated by the flow can be accessed using at least one of GraphQL, SOAP, Odata, or OpenAPI, flow execution comprising:

obtaining metadata associated with the flow, the metadata specifying a schema of the input data or rules for associating semantics with the input data;

creating a pipeline using the flow and the metadata associated with the flow, the pipeline configured to perform a data transformation specified in the flow and execution of the flow dependent on the obtained metadata;

determining a tenancy associated with the input data using the flow, the tenancy associated with the input data representing an ownership of the input data, the determining comprising:

extracting identifying characteristics of the input data from the input data;

providing the identifying characteristics of the input data to an identity service; and

receiving a tenancy identifier of the input data from the identity service;

generating the output data from the input data by performing the data transformation on the input data using the pipeline;

storing, using the pipeline, the output data in a second storage location associated with the tenancy;

creating a tenancy object for the output data which is generated by performing the data transformation on the input data, based on the tenancy identifier of the input data received from the identity service, the tenancy object for the output data representing an ownership of the output data;

storing the tenancy object created for the output data in a metadata repository according to a hierarchical data object ownership graph which comprises a plurality of tenancy objects arranged as parent objects and child objects, wherein the storing the tenancy object including associating the tenancy object created for the output data with a parent object in the hierarchical data object ownership graph; and

determining whether to authorize a request to display at least a portion of the output data based at least in part on the association between the tenancy object and the parent object in the hierarchical data object ownership graph.

Assignments (1)

Continuity (2)

References Cited (19)

Cited By (1)

US 12,699,674