Replicating materialized views across heterogeneous target systems

Patent metadata

Field	Value
Publication number	US-2021165803-A1
Application number	US-201916699547-A
Country	US
Kind code	A1
Filing date	Nov 29, 2019
Priority date	Nov 29, 2019
Publication date	Jun 3, 2021
Grant date	—

Abstract

A materialized view created by a materialized view management platform may be replicated across many different target systems. The materialized view management platform allows users to specify different target systems. To create the materialized view in the different target systems, the materialized view management platform can translate the materialized view into different formats in order to store the materialized view in the different formats. Updates to the different instances of the materialized view are then made to keep the different materialized view formats in the different target systems up-to-date.

First claim

What is claimed is:

1 . A system, comprising:
at least one processor; and a memory, to store program instructions that when executed by the at least one processor, cause the at least on processor to implement a materialized view management platform:
create a materialized view from one or more data sources according to a definition received as part of a request to create the materialized view at a plurality of different target data stores, the request received at the materialized view management platform;
after creating the materialized view at the different target data stores:
determine changes to a materialized view from one or more data sources according to a definition received at the materialized view management platform; and
send one or more requests formatted according to respective interfaces for the different target data stores to store respective target-specific versions of the materialized view to the plurality of different target data stores that are determined from the changes to the materialized view.

2 . The system of claim 1 , wherein the materialized view management platform is further configured to determine which ones of the plurality of different target data stores has performance of updates to the materialized view enabled before sending the one or more requests.

3 . The system of claim 1 , wherein the materialized view management platform is further configured to:
receive a request to add a target data store to the plurality of different target data stores for the materialized view; assign a target connector to the target data store; store a version of the materialized view in the target data store; and enable performance of updates to the materialized view by the assigned target connector.

4 . The system of claim 1 , wherein the materialized view management platform is offered as part of a provider network and wherein at least one of the plurality of target data stores is implemented external to the provider network.

5 . A method, comprising:
determining, by a materialized view management platform, changes to a materialized view from one or more data sources according to a definition received at the materialized view management platform; identifying, by the materialized view management platform, a plurality of different target data stores for the materialized view; and storing, by the materialized view management platform, respective target-specific versions of the materialized view to the plurality of different target data stores that are determined from the changes to the materialized view.

6 . The method of claim 5 , wherein determining the changes to the materialized view from one or more data sources is based on an internal view of the materialized view generated at the materialized view management platform.

7 . The method of claim 6 , further comprising:
detecting, by the materialized view management platform, an event to disable performance of updates to one of the target data stores; and disabling, by the materialized view management platform, performance of updates to the one target data store at a target connector assigned to the one target data store.

8 . The method of claim 5 , further comprising:
detecting, by the materialized view management platform, an event to enable performance of updates to one of the target data stores; and enabling, by the materialized view management platform, performance of updates to the one target data store at a target connector assigned to the one target data store.

9 . The method of claim 5 , further comprising:
receiving a request to add a target data store for the materialized view; assigning a target connector to the target data store; storing a version of the materialized view in the target data store; and enabling performance of updates to the materialized view by the assigned target connector.

10 . The method of claim 5 , further comprising:
receiving a request to remove one of the different target data stores from a materialized view; disabling performance of updates to the materialized view to the one target data store; and deleting the materialized view at the one target data store.

11 . The method of claim 5 , further comprising:
receiving, by the materialized view management platform, a request to disable performance of updates to one of the target data stores; and disabling, by the materialized view management platform, performance of updates to the one target data store at a target connector assigned to the one target data store.

12 . The method of claim 5 , further comprising:
receiving, by the materialized view management platform, a request to enable performance of updates to one of the target data stores; and enabling, by the materialized view management platform, performance of updates to the one target data store at a target connector assigned to the one target data store.

13 . The method of claim 5 , further comprising creating the materialized view at the plurality of different data stores in response to a request to create the materialized view that includes the definition that specifies the plurality of different data stores.

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 platform that implements a materialized view management platform that implements:
determining changes to a materialized view from one or more data sources according to a definition received at the materialized view management platform; identifying a plurality of different target data stores for the materialized view; and sending one or more requests formatted according to respective interfaces for the different target data stores to store respective target-specific versions of the materialized view to the plurality of different target data stores that are determined from the changes to the materialized view.

15 . The one or more non-transitory, computer-readable storage media of claim 14 , wherein, in identifying plurality of different target data stores for the materialized view, the program instructions cause materialized view management platform to implement determining which ones of the plurality of different target data stores has performance of updates to the materialized view enabled before sending the one or more requests.

16 . The one or more non-transitory, computer-readable storage media of claim 14 , wherein the one or more non-transitory, computer-readable storage media store further program instructions that when executed on or across the at least one or more computing devices cause the materialized view management platform to further implement:
receiving a request to add a target data store for the materialized view; assigning a target connector to the target data store; storing a version of the materialized view in the target data store; and enabling performance of updates to the materialized view by the assigned target connector.

17 . The one or more non-transitory, computer-readable storage media of claim 14 , wherein the one or more non-transitory, computer-readable storage media store further program instructions that when executed on or across the at least one or more computing devices cause the materialized view management platform to further implement:
detecting, by the materialized view management platform, an event to disable performance of updates to one of the target data stores; and disabling, by the materialized vi

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/26 Primary

  Visual data mining; Browsing structured data · CPC title