Cross-ontology multi-master replication

• US 8,688,749 B1
• Filed: 03/31/2011
• Issued: 04/01/2014
• Est. Priority Date: 03/31/2011
• Status: Active Grant

• Current Assignee: Palantir Technologies Incorporated
• Original Assignee: Palantir Technologies Incorporated
• Inventors: Garrod, John Kenneth, Carrino, John Antonio, Brainard, Katherine, Ducott, Richard Allen III
• Primary Examiner(s): LIAO, JASON G
• Application Number:
  US13/076,804
• Time in Patent Office: 1,097 Days
• Field of Search: None
• US Class Current: 707/803
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: G06F 7/00 Methods or arrangements for processing data by operating upon the order or content of the data handled logic circuits H03K19/00
• CPC Class Codes: G06N 5/02 Knowledge representation; Symbolic representation

Abstract

A system and method providing cross-ontology multi-master replication is described. In a first embodiment a method for cross-ontology multi-master replication comprising the steps of: obtaining, at an importing site, an exporting site ontology and a set of one or more database changes; wherein the exporting site ontology defines a set of one or more data types; and after mapping the exporting site ontology to an importing site ontology, incorporating the set of one or more database changes into a database including mapping each of one or more data types of the set of data types to a data type defined by the importing site ontology using an ontology map.

Claims

1. A method comprising:

modeling for implementing object-centric data models;

obtaining, at an importing site, an exporting site ontology and a set of one or more database changes associated with an exporting site;

wherein the exporting site ontology defines one or more first object types and one or more first link types relating two or more objects of the one or more first object types in a first object-centric data model;

obtaining an ontology map comprising at least one object rule for mapping the one or more first object types of the first object-centric data model one or more second object types in a second object-centric data model defined by an importing site ontology and at least one link rule for mapping the one or more first link types of the first object-centric data model to one or more second link types in the second object-centric data model;

incorporating the set of one or more database changes into a database at the importing site based on the at least one object rule and the at least one link rule, wherein at least one link represented in the set of one or more database changes is reversed based on the at least one link rule;

wherein object data for at least one object is represented by different object types in the first object-centric data model and the second object-centric data model;

wherein the method is performed by one or more computing devices.

2. The method of claim 1, wherein at least one database change of the set of one or more database changes comprises (a) a data item representing a change to a database copy at the exporting site and (b) data representing an object type of the data item according to the exporting site ontology.

3. The method of claim 1, wherein obtaining, at the importing site, the exporting site ontology and the set of one or more database changes comprises obtaining, at the importing site, a database update comprising the exporting site ontology and the set of one or more database changes.

4. The method of claim 1, further comprising:

obtaining, at the importing site, a digest of an ontology map at the exporting site;

computing a digest of an ontology map at the importing site;

comparing the obtained digest of the ontology map at the exporting site with the computed digest of the ontology map at the importing site.

5. The method of claim 1,

wherein the ontology map comprises a one-to-one mapping between a first particular data type defined by the exporting site ontology and a second particular data type defined by the importing site ontology;

and

wherein incorporating the set of one or more database changes into a database at the importing site based on the at least one object rule comprises mapping the first particular data type to the second particular data type using the ontology map.

6. The method of claim 1,

wherein the ontology map comprises a one-to-many mapping between a first particular data type defined by the exporting site ontology and a plurality data types defined by the importing site ontology;

and

wherein incorporating the set of one or more database changes into a database at the importing site based on the at least one object rule comprises mapping the first particular data type to one of the plurality of data types defined by the importing site ontology using the ontology map.

7. The method of claim 1, wherein the ontology map specifies a list of data types to be dropped when exporting database changes from the exporting site.

8. The method of claim 1,

wherein the ontology map comprises a one-to-one mapping between a first particular link data type defined by the exporting site ontology and a second particular link data type defined by the importing site ontology;

wherein a particular rule of the at least one link rule further specifies that a link represented by data of the first particular link data type should be reversed before data representing the link is incorporated into the database;

wherein incorporating the set of one or more database changes into the database comprises reversing a link represented by a particular database change of the set of database changes before incorporating the particular database change into the database.

9. A system comprising:

models for implementing object-centric data models;

one or more processors;

one or more non-transitory computer readable storage media; and

logic configured for;

obtaining, at an importing site, an exporting site ontology and a set of one or more database changes associated with an exporting site;

wherein the exporting site ontology defines one or more first object types and one or more first link types relating two or more objects of the one or more first object types in a first object-centric data model;

obtaining an ontology map comprising at least one rule for mapping the one or more first object types of the first object-centric data model to one or more second object types and one or more second link types in a second object-centric data model defined by an importing site ontology and at least one link rule for mapping the one or more first link types of the first object-centric data model to one or more second link types in the second object-centric data model;

incorporating the set of one or more database changes into a database at the importing site based on the at least one object rule and the at least one link rule, wherein at least one link represented in the set of one or more database changes is reversed based on the at least one rule;

wherein object data for at least one object is represented by different object types in the first object-centric data model and the second object-centric data model.

10. The system of claim 9, wherein at least one database change of the set of one or more database changes comprises (a) a data item representing a change to a database copy at the exporting site and (b) data representing an object type of the data item according to the exporting site ontology.

11. The system of claim 9, wherein obtaining, at the importing site, the exporting site ontology and the set of one or more database changes comprises obtaining, at the importing site, a database update comprising the exporting site ontology and the set of one or more database changes.

12. The system of claim 9, further comprising logic for:

obtaining, at the importing site, a digest of an ontology map at the exporting site;

computing a digest of an ontology map at the importing site;

comparing the obtained digest of the ontology map at the exporting site with the computed digest of the ontology map at the importing site.

13. The system of claim 9, wherein the ontology map comprises a one-to-one mapping between a first particular data type defined by the exporting site ontology and a second particular data defined by the importing site ontology;

and wherein incorporating the set of one or more database changes into a database at the importing site based on the at least one object rule comprises mapping the first particular data type to the second particular data type using the ontology map.

14. The system of claim 9,

wherein the ontology map comprises a one-to-many mapping between a first particular data type defined by the exporting site ontology and a plurality of data types defined by the importing site ontology;

and

wherein incorporating the set of one or more database changes into a database at the importing site based on the at least one object rule comprises mapping the first particular data type to one of the plurality of data types defined by the importing site ontology using the ontology map.

15. The system of claim 9, wherein the ontology map specifies a list of data types to be dropped when exporting database changes from the exporting site.

16. The system of claim 9,

wherein the ontology map comprises a one-to-one mapping between a first particular link data type defined by the exporting site ontology and a second particular link data type defined by the importing site ontology;

wherein a particular rule of the at least one link rule further specifies that a link represented by data of the first particular link data type should be reversed before data representing the link is incorporated into the database;

wherein incorporating the set of one or more database changes into the database comprises reversing a link represented by a particular database change of the set of database changes before incorporating the particular database change into the database.

17. A non-transitory computer readable medium storing computer-executable instructions which, when executed by one or more processors, cause the one or more processors to carry out steps comprising:

modeling for implementing for object-centric data models;

obtaining, at an importing site, an exporting site ontology and a set of one or more database changes associated with an exporting site;

wherein the exporting site ontology defines one or more first object types and one or more first link types relating two or more objects of the one or more first object types in a first object-centric data model;

obtaining an ontology map comprising at least one object rule for mapping the one or more first object types of the first object-centric data model to one or more second object types in a second object-centric data model defined by an importing site ontology and at least one link rule for mapping the one or more first link types of the first object-centric data model to one or more second link types in the second object-centric data model;

incorporating the set of one or more database changes into a database at the importing site based on the at least one object rule and the at least one link rule, wherein at least one link represented in the set of one or more database changes is reversed based on the at least one link rule;

wherein object data for at least one object is represented by different object types in the first object-centric data model and the second object-centric data model.

18. The non-transitory computer readable medium of claim 17, wherein at least one database change of the set of one or more database changes comprises (a) a data item representing a change to a database copy at the exporting site and (b) data representing an object type of the data item according to the exporting site ontology.

19. The non-transitory computer readable medium of claim 17, wherein obtaining, at the importing site, the exporting site ontology and the set of one or more database changes comprises obtaining, at the importing site, a database update comprising the exporting site ontology and the set of one or more database changes.

20. The non-transitory computer readable medium of claim 17, the steps further comprising:

obtaining, at the importing site, a digest of an ontology map at the exporting site;

computing a digest of an ontology map at the importing site;

comparing the obtained digest of the ontology map at the exporting site with the computed digest of the ontology map at the importing site.

21. The non-transitory computer readable medium of claim 17 the steps further comprising,

wherein the ontology map comprises a one-to-one mapping between a first particular data type defined by the exporting site ontology and a second particular data type defined by the importing site ontology;

and

wherein incorporating the set of one or more database changes into a database at the importing site based on the at least one object rule comprises mapping the first particular data type to the second particular data type using the ontology map.

22. The non-transitory computer readable medium of claim 17,

wherein the ontology map comprises a one-to-many mapping between a first particular data type defined by the exporting site ontology and a plurality data types defined by the importing site ontology;

and

wherein incorporating the set of one or more database changes into a database at the importing site based on the at least one object rule comprises mapping the first particular data type to one of the plurality of data types defined by the importing site ontology using the ontology map.

23. The non-transitory computer readable medium of claim 17, wherein the ontology map specifies a list of data types to be dropped when exporting database changes from the exporting site.

24. The non-transitory computer readable medium of claim 17,

wherein the ontology map comprises a one-to-one mapping between a first particular link data type defined by the exporting site ontology and a second particular link data type defined by the importing site ontology;

wherein a particular rule of the at least one link rule further specifies that a link represented by data of the first particular link data type should be reversed before data representing the link is incorporated into the database;

wherein incorporating the set of one or more database changes into the database comprises reversing a link represented by a particular database change of the set of database changes before incorporating the particular database change into the database.