Detecting schema incompatibilities for generating views at target data stores

Patent metadata

Field	Value
Publication number	US-2022171759-A1
Application number	US-202117362729-A
Country	US
Kind code	A1
Filing date	Jun 29, 2021
Priority date	Nov 28, 2020
Publication date	Jun 2, 2022
Grant date	—

Abstract

Schema incompatibilities are generating views at target data stores are detected. A view definition may be received at a view management system that specifies data to obtain from source data stores and identifies a target data store to store the view. The view management system may identify an incompatibility between a schema for the data, specified in the view definition, with a type system for the target data store. The view management system may provide an indication of the incompatibility with the type system for the target data store.

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, the materialized view management service configured to:
receive, via an interface, a view definition for a materialized view, the view definition specifying data to obtain from one or more source data stores that store the data of the materialized view and identifying a target data store to store the data of the materialized view;
detect an incompatibility between a schema for the data specified in the view definition with a type system for the target data store; and
provide, via the interface, an indication of the incompatibility of the schema specified in the view definition with the type system for the target data store.

2 . The system of claim 1 , wherein the materialized view management service is further configured to:
determine one or more suggested modifications to the view definition to resolve the incompatibility; and wherein the one or more suggested modifications are provided with the indication of the incompatibility of the data type.

3 . The system of claim 1 , wherein the view definition includes a function mapping an item in the data to a data type in the type system for the target data store and wherein to detect the incompatibility between the schema for the data, specified in the view definition with the type system for the target data store, the materialized view management service is configured to detect a missing data type when evaluating the function specified in the view definition mapping the item to the data type in the type system for the target data store.

4 . The system of claim 1 , wherein the view definition is a mapping view definition, wherein the mapping view definition identifies a schema for the view specified in a different view definition that identifies a different target data store to store the view.

5 . A method, comprising:
receiving, by an interface of a view management system, a view definition for a view, the view definition specifying data to obtain from one or more source data stores that store the data for the view and identifying a target data store to store the data for the view; identifying, by the view management system, an incompatibility between a schema for the data, specified in the view definition with a type system for the target data store; and providing, via the interface of the view management system, an indication of the incompatibility of the schema specified in the view definition with the type system for the target data store.

6 . The method of claim 5 , further comprising:
determining one or more suggested modifications to the view definition to resolve the incompatibility; and wherein the one or more suggested modifications are provided with the indication of the incompatibility.

7 . The method of claim 5 , wherein the view definition includes a function mapping an item in the data to a data type in the type system for the target data store and wherein identifying the incompatibility between the schema for the data, specified in the view definition with the type system for the target data store comprises receiving a missing data type response for the function specified in the view definition mapping the item to the data type in the type system for the target data store when generating an execution plan for the view by the view management system.

8 . The method of claim 5 , wherein the view definition is a mapping view definition, wherein the mapping view definition identifies a schema for the view specified in a different view definition that identifies a different target data store to store the view.

9 . The method of claim 5 , wherein the view definition is specified according to a query language.

10 . The method of claim 5 , wherein the one or more data stores store data according to a first data model, wherein the target data store stores data according to a second data model, wherein the view management system implements a hub data model, and wherein the first data model and the second data model are respective extensions of the hub data model.

11 . The method of claim 10 , wherein view definition further specifies a different source data store in addition to the one or more source data stores to obtain further data from the different source data store to store in the target data store as part of the view, wherein the further data stored in the different source data store is stored according to a third data model different from the first data model.

12 . The method of claim 5 , wherein the view management system is a materialized view management service offered as part of a provider network that offers a plurality of different data storage services, wherein the target data store is implemented as part of one of the plurality of data storage services different than the one or more source data stores.

13 . A non-transitory, computer-readable storage medium, storing program instructions that when executed on or across one or more computing devices, cause the one or more computing devices to implement
receiving, by a view management system, a view definition that specifies one or more source data stores and a target data store, wherein the view definition is specified according to a query language, and wherein the view management system implements a hub data model that is extensible to include a first data model for the one or more source data stores and a second data model for the target data store; evaluating, by the view management system, the view definition according to the hub data model to determine a plan to generate a view according to the view definition; and executing, by the view management system, the plan to generate the view.

14 . The method of claim 13 , wherein evaluating the view definition according to the hub data model to determine the plan to generate the view, comprises:
identifying an incompatibility between the one or more source data stores and the target data store; and determining a resolution for the incompatibility.

15 . The method of claim 14 , wherein determining the resolution for the incompatibility comprises:
providing, via an interface of the view management system, an indication of the incompatibility; and receiving, via the interface of the view management system, the resolution for the incompatibility.

16 . The method of claim 15 , further comprising:
determining one or more suggested modifications to the view definition to resolve the incompatibility; and wherein the one or more suggested modifications are provided with the indication of the incompatibility.

17 . The method of claim 16 , wherein the resolution is a selected one of the one or more suggested modifications.

18 . The method of claim 14 , further comprising:
receiving a request to create a mapping view definition to a different target data store than the target data store in the view definition; and automatically creating the mapping view definition to the different target data store based on the view definition.

19 . The method of claim 18 , wherein automatically creating the mapping view definition comprises determining a resolution to an identified incompatibility between the one or more source data stores and the different target data store.

20 . The method of claim 14 , wherein the view management system is a materialized view managem

Assignees

• Amazon Tech Inc

Inventors

• Jindal Himanshu
• Ummenthala Shivateja Reddy
• Goo Almann Tsutomu
• Papakonstantinou Yannis
• Bruck Lewis
• Certain Tate Andrew
• Maheshwari Pulkit

Classifications

• G06F16/2445 Primary

  Data retrieval commands; View definitions · CPC title

• G06F16/2358 Primary

  Change logging, detection, and notification (replication G06F16/27) · CPC title