Managed materialized views created from heterogenous data sources

Patent metadata

Field	Value
Publication number	US-11874828-B2
Application number	US-202117466347-A
Country	US
Kind code	B2
Filing date	Sep 3, 2021
Priority date	Nov 29, 2019
Publication date	Jan 16, 2024
Grant date	Jan 16, 2024

Abstract

Managed materialized views may be generated from across heterogeneous data sources. A request to create a materialized view may be received and performed by a materialized view management platform, which may obtain and generate the materialized view from different data sources and store the materialized view in a target system. Changes to the data sources may be obtained at the materialized view management platform and updates to the materialized view may be determined. The materialized view in the target system may be updated.

First claim

What is claimed is:

1. A system, comprising:
at least one processor; and
a memory, storing program instructions that when executed by the at least one processor, cause the at least one processor to implement a materialized view management service, wherein the materialized view management service that performs materialized view management is configured to:
receive, via an interface of the materialized view management service, a request to create a materialized view using data from a data source ingested by a connector corresponding to the data source, wherein the materialized view is specified in a definition received for the materialized view, wherein the materialized view management service is capable of creating the materialized view from a plurality of different types of data sources using respective ones of a plurality of different connectors implemented as part of the materialized view management service, and wherein the materialized view is stored by the materialized view management service in a data store accessible to queries;
obtain, from the data source using the connector corresponding to the data source, one or more changes made at the at least one data source;
determine one or more updates to the materialized view that satisfies the definition of the materialized view from the respective one or more changes obtained from the data source; and
perform the one or more updates to the materialized view to make the one or more updates accessible in subsequent queries to the materialized view.

2. The system of claim 1 , wherein the materialized view management service is further configured to collect performance metrics to monitor performance of the materialized view.

3. The system of claim 1 , wherein one or more changes are written to a delta table.

4. The system of claim 1 , wherein the materialized view management service is offered as part of a provider network and wherein-the data source is another service offered by the provider network.

5. A method, comprising:
receiving, via an interface of the materialized view management service, a request to create a materialized view using data from a data source ingested by a connector corresponding to the data source, wherein the materialized view is specified in a definition received for the materialized view, wherein the materialized view management service is capable of creating the materialized view from a plurality of different types of data sources using respective ones of a plurality of different connectors implemented as part of the materialized view management service, and wherein the materialized view is stored by the materialized view management service in a data store accessible to queries;
obtaining, by the connector for the data source, one or more changes from the data source;
determining, by the materialized view management service, one or more updates to the materialized view that satisfies the definition of the materialized view from the one or more changes obtained from the data source; and
updating, by the materialized view management service, the materialized view to make the one or more updates accessible in subsequent queries to the materialized view.

6. The method of claim 5 , wherein the definition of the materialized view includes an aggregation.

7. The method of claim 5 , further comprising collecting performance metrics to monitor performance of the materialized view.

8. The method of claim 5 , further comprising determining, by the materialized view management service, a last time the materialized view was updated.

9. The method of claim 5 , wherein the one or more changes are written to a delta table.

10. The method of claim 5 , wherein the materialized view management service is offered as part of a provider network and wherein the data source is a relational database service.

11. The method of claim 5 , further comprising dropping, by the materialized view management service, responsive to a request to drop the materialized view received via the materialized view management service.

12. The method of claim 5 , wherein a second data source is used to create the materialized view and wherein a second connector of the plurality of connectors for the different types of data sources corresponding to the second data source is used to ingest further data from the second data source.

13. The method of claim 5 , wherein the data source is a streaming data source.

14. One or more non-transitory, computer-readable storage media, storing program instructions that when executed on or across one or more computing devices cause the one or more computing devices to implement a materialized view management service that implements:
receiving, via an interface of the materialized view management service, a request to create a materialized view using data from a data source ingested by a connector corresponding to the data source, wherein the materialized view is specified in a definition received for the materialized view, wherein the materialized view management service is capable of creating the materialized view from a plurality of different types of data sources using respective ones of a plurality of different connectors implemented as part of the materialized view management service, and wherein the materialized view is stored by the materialized view management service in a data store accessible to queries;
obtaining, by the connector for the data source, one or more changes from the data source;
determining one or more updates to the materialized view that satisfies the definition of the materialized view from the one or more changes obtained from the data source; and
performing the one or more updates to update the materialized view to make the one or more updates accessible in subsequent queries to the materialized view.

15. The one or more non-transitory, computer-readable storage media of claim 14 , wherein the definition of the materialized view includes an aggregation.

16. The one or more non-transitory, computer-readable storage media of claim 14 , storing further program instructions that when executed on or across the one or more computing devices cause the materialized view management service to further implement determining a last time the materialized view was updated.

17. The one or more non-transitory, computer-readable storage media of claim 14 , wherein the one or more changes are written to a delta table.

18. The one or more non-transitory, computer-readable storage media of claim 14 , storing further program instructions that when executed on or across the one or more computing devices cause the materialized view management service to further implement dropping, by the materialized view management service, responsive to a request to drop the materialized view received via the materialized view management service.

19. The one or more non-transitory, computer-readable storage media of claim 14 , storing further program instructions that when executed on or across the one or more computing devices cause the materialized view management service to further implement collecting performance metrics to monitor performance of the materialized view.

20. The one or more non-transitory, computer-readable storage media of claim 14 , wherein the materialized view management service is offered as part of a provider network and wherein-the data source is a non-relational database service offered by the provider network.

Assignees

• Amazon Tech Inc

Inventors

• Deshpande Rohan
• Papakonstantinou Yannis
• Zaki Omer Ahmed
• Bharathy Karthik Gurumoorthy Subramanya
• Dugar Rajib
• Ummenthala Shivateja Reddy

Classifications

• G06F16/2393 Primary

  Updating materialised views · CPC title

• G06F16/219

  Managing data history or versioning (querying versioned data G06F16/2474; querying temporal data G06F16/2477) · CPC title

• G06F16/2445

  Data retrieval commands; View definitions · CPC title