Schema evolution in multi-tenant environment

• US 10,078,676 B2
• Filed: 06/11/2015
• Issued: 09/18/2018
• Est. Priority Date: 04/06/2015
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Bhagat, Prashant, Bengali, Ketan, Prasad, Sushant, Lee, Dennis, Chavan, Harshad, Gangadharappa, Kiran, Shahane, Dinesh
• Primary Examiner(s): Ly, Anh
• Application Number:
  US14/737,332
• Publication Number:
  US 20160292192A1
• Time in Patent Office: 1,195 Days
• CPC Class Codes: G06F 16/211 Schema design and management
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database

Abstract

In an example embodiment, primary data is received from a first tenant in a computer network, the primary data formatted based on a first version of a schema. Then a schema definition for the first version of the schema is obtained. The primary data is then parsed, the parsing including storing a schema version number for the first version of the schema. The primary data is indexed, by obtaining, using the schema version number for the first version of the schema, a schema definition for a most recent version of the schema; applying schema evolution to the primary data by applying one or more transforms to the primary data, the one or more transforms created using the schema definition for the first and most recent versions of the schema, causing the primary data to be converted to the most recent version of the schema; and indexing the converted primary data.

Claims

1. A method comprising:

receiving primary data from a first tenant in a computer network, the primary data formatted based on a first version of a schema for a database;

obtaining a schema definition for the first version of the schema, the schema definition providing a set of integrity constraints imposed on the database;

parsing, using at least one hardware processor, the primary data, the parsing including storing a schema version number for the first version of the schema; and

indexing, using the at least one hardware processor, the primary data, the indexing comprising;

obtaining, using the schema version number for the first version of the schema, a schema definition for a most recent version of the schema, the schema definition for the most recent version of the schema being obtained prior to obtaining the schema definition for older versions of the schema;

applying schema evolution to the primary data by applying one or more transforms to the primary data, the one or more transforms defining one or more rules that, when executed, transform the primary data into the most recent version of the schema, the one or more transforms created using the schema definition for the most recent version of the schema and the schema definition for the first version of the schema; and

indexing, using the at least one hardware processor, the converted primary data.

2. The method of claim 1, wherein the receiving and obtaining a schema definition are performed by an application program interface (API).

3. The method of claim 1, wherein the schema definition for the first version of the schema is obtained from a distributed database.

4. The method of claim 1, wherein the parsing is performed by a record parser that stores the primary data along with the schema version number.

5. The method of claim 1, wherein the storing of the schema version number is performed using a row key.

6. The method of claim 5, wherein the row key is created by subtracting a major number of the schema version number from 999 and subtracting a minor number of the schema version number from 99999.

7. The method of claim 5, wherein the row key is created so that when the schema version number is stored, a latest schema version number is always stored as being first in a resulting data structure.

8. A system comprising:

a distributed database;

an index and search manager executable on one or more hardware processors, the index and search manager comprising;

a versioning control component configured to;

receive primary data from a first tenant in as computer network, the primary data formatted based on a first version of a schema for a database;

obtain a schema definition for the first version of the schema, the schema definition providing a set of integrity constraints imposed on the database, the schema definition for the most recent version of the schema being obtained prior to obtaining the schema definition for older versions of the schema; and

store a schema version number for the first version of the schema;

a record parser configured to obtain, using the schema version number for the first version of the schema, a schema definition for a most recent version of the schema,

at transformation component configured to apply schema evolution to the primary data by applying one or more transforms to the primary data, the one or more transforms defining one or more rules that, when executed, transform the primary data into the most recent version of the schema, the one or more transforms created using the schema definition for the most recent version of the schema and the schema definition for the first version of the schema; and

an indexer configured to index the converted primary data.

9. The system of claim 8, wherein the schema definition of the first version of the schema is obtained from a distributed database.

10. The system of claim 8, wherein the storing of the schema version number is preferred using a row key.

11. The system of claim 10, wherein the row key is created by subtracting a major number of the schema version number from 999 and subtracting a minor number of the schema version number from 99999.

12. The system of claim 10, wherein the row key is created so that when the schema version number is stored, a latest schema version number is always stored as being first in a resulting data structure.

13. The system of claim 8, wherein the versioning control component is part of a publish API.

14. A non-transitory machine readable storage medium comprising instructions, which when implemented by one or more machines, cause the one or more machines to perform operations comprising:

receiving primary data from a first tenant in a computer network, the primary data formatted based on a first version of a schema for a database;

obtaining a schema definition for the first version of the schema, the schema definition providing a set of integrity constraints imposed on the database;

parsing, using at least one hardware processor, the primary data, the parsing including storing a schema version number for the first version of the schema, and

indexing, using the at least one hardware processor, the primary data, the indexing comprising;

obtaining, using the schema version number for the first version of the schema, a schema definition for a most recent version of the schema, the schema definition for the most recent version of the schema being obtained prior to obtaining the schema definition for older versions of the schema;

applying schema evolution to the primary data by applying one or more transforms to the primary data, the one or more transforms defining one or more rules that, when executed, transform the primary data into the most recent version of the schema, the one or more transforms created using the schema definition for the most recent version of the schema and the schema definition for the first version of the schema; and

indexing, using the at least one hardware processor, the converted primary data.

15. The non-transitory machine-readable storage medium of claim 14, wherein the receiving and obtaining, a schema definition are performed by an application program interface (API).

16. The non-transistor machine-readable storage medium of claim 14, wherein the schema definition for the first version of the schema is obtained from a distributed database.

17. The non-transitory machine-readable storage medium of claim 14, wherein the parsing is performed by a record parser that stores the primary data along with the schema version number.

18. The non-transitory machine-readable storage medium of claim 14, wherein the storing of the schema version number is performed using a row key.

19. The non-transitory machine-readable storage medium of claim 18, wherein the row key is created by subtracting a major number of the schema version number from 999 and subtracting a minor number of the schema version number from 99999.

20. The non-transitory machine-readable storage medium of claim 18, wherein the row key is created so that when the schema version number is stored, a latest schema version number is always stored as being first in a resulting data structure.