Systems and methods for providing an object platform for a relational database

Patent metadata

Field	Value
Publication number	US-10691729-B2
Application number	US-201815958853-A
Country	US
Kind code	B2
Filing date	Apr 20, 2018
Priority date	Jul 7, 2017
Publication date	Jun 23, 2020
Grant date	Jun 23, 2020

Abstract

Systems and methods are provided for providing an object platform for datasets A definition of an object may be obtained. The object may be associated with information stored in one or more datasets. The information may be determined based at least in part on the definition of the object. The object may be stored in a cache such that the information associated with the object is also stored in the cache. One or more interfaces through which requests to perform one or more operations on the object are able to be submitted may be provided.

First claim

The invention claimed is:

1. A system comprising:
one or more processors; and
memory storing instructions that, when executed by the one or more processors, cause the system to perform:
obtaining a definition of an object included within an ontology of an object store;
associating the object with information stored in one or more datasets of a relational database, the information being determined based at least in part on the definition of the object;
storing the object in an object cache of the object store such that the information associated with the object is also stored in the object cache;
providing one or more object-oriented interfaces through which requests to perform one or more object-oriented operations on the object are able to be submitted, the one or more object-oriented operations including modifying the object, wherein information about modifications to the object are stored in a commit log, the information including one or more vector clocks associated with the modifications to the object, wherein each of the one or more vector clocks are stored on a per dataset basis, the one or more vector clocks being distinguished, via different identifiers, based on whether the modifications originate from changes in the one or more datasets or from changes made to the object relating to a transaction of the object cache;
receiving, through at least one of the one or more object-oriented interfaces, a first request to perform at least one object-oriented operation on the object stored in the object cache; and
modifying, based on the first request received through the at least one of the one or more object-oriented interfaces, the information stored in the one or more datasets of the relational database.

2. The system of claim 1 , wherein the object-oriented operations include searching for the object, loading the object, or modifying the object.

3. The system of claim 2 , wherein the object is modified within the object cache.

4. The system of claim 3 , wherein the modified object is stored in an object store.

5. The system of claim 1 , wherein the instructions further cause the system to perform:
identifying a change to the definition of the object; and
updating the object in the object cache based on the change to the definition of the object.

6. The system of claim 1 , wherein, the information includes including time stamps associated with the modifications to the object.

7. The system of claim 6 , wherein the instructions further cause the system to perform:
identifying conflicts in the modifications to the object based on the commit log; and
resolving the conflicts.

8. A method implemented by a computing system including one or more processors and storage media storing machine-readable instructions, wherein the method is performed using the one or more processors, the method comprising:
obtaining a definition of an object included within an ontology of an object store;
associating the object with information stored in one or more datasets of a relational database, the information being determined based at least in part on the definition of the object;
storing the object in an object cache of the object store such that the information associated with the object is also stored in the object cache;
providing one or more object-oriented interfaces through which requests to perform one or more object-oriented operations on the object are able to be submitted, the one or more object-oriented operations including modifying the object, wherein information about modifications to the object are stored in a commit log, the information including one or more vector clocks associated with the modifications to the object, wherein each of the one or more vector clocks are stored on a per dataset basis, the one or more vector clocks being distinguished, via different identifiers, based on whether the modifications originate from changes in the one or more datasets or from changes made to the object relating to a transaction of the object cache;
receiving, through at least one of the one or more object-oriented interfaces, a first request to perform at least one object-oriented operation on the object stored in the object cache; and
modifying, based on the first request received through the at least one of the one or more object-oriented interfaces, the information stored in the one or more datasets of the relational database.

9. The method of claim 8 , wherein the object-oriented operations include searching for the object, loading the object, or modifying the object.

10. The method of claim 9 , wherein the object is modified within the object cache.

11. The method of claim 10 , wherein the modified object is stored in an object store.

12. The method of claim 8 , further comprising:
identifying a change to the definition of the object; and
updating the object in the object cache based on the change to the definition of the object.

13. The method of claim 8 , wherein, the information includes including time stamps associated with the modifications to the object.

14. The method of claim 13 , further comprising:
identifying conflicts in the modifications to the object based on the commit log; and
resolving the conflicts.

15. A non-transitory computer readable medium comprising instructions that, when executed, cause one or more processors to perform:
obtaining a definition of an object included within an ontology of an object store;
associating the object with information stored in one or more datasets of a relational database, the information being determined based at least in part on the definition of the object;
storing the object in an object cache of the object store such that the information associated with the object is also stored in the object cache;
providing one or more object-oriented interfaces through which requests to perform one or more object-oriented operations on the object are able to be submitted, the one or more object-oriented operations including modifying the object, wherein information about modifications to the object are stored in a commit log, the information including one or more vector clocks associated with the modifications to the object, wherein each of the one or more vector clocks are stored on a per dataset basis, the one or more vector clocks being distinguished, via different identifiers, based on whether the modifications originate from changes in the one or more datasets or from changes made to the object relating to a transaction of the object cache;
receiving, through at least one of the one or more object-oriented interfaces, a first request to perform at least one object-oriented operation on the object stored in the object cache; and
modifying, based on the first request received through the at least one of the one or more object-oriented interfaces, the information stored in the one or more datasets of the relational database.

16. The non-transitory computer readable medium of claim 15 , wherein the object-oriented operations include searching for the object, loading the object, or modifying the object.

17. The non-transitory computer readable medium of claim 16 , wherein the modified object is stored in an object store.

18. The non-transitory computer readable medium of claim 15 , wherein, the information includes including time stamps associated with the modifications to the object.

19. The system of claim 1 , wherein, if the object is backed by a single row or a single column in a dataset with a single primary key column or a single primary key row, the object is

Assignees

• Palantir Technologies Inc

Inventors

• Ducott Rick
• Goenka Aakash
• Rahill-Marier Bianca
• Wei Tao
• De Holanda Diogo Bonfim Moraes Morant
• Grossman Jack
• Screene Francis
• Harish Subbanarasimhiah
• Inoue Jim
• Kong Jeremy
• Elliot Mark
• Scolnick Myles
• Spencer-Harper Quentin
• Niemi Richard
• Vorel Ragnar
• Mcintyre Thomas
• Powell Thomas
• Chen Andy

Classifications

• G06F16/2358

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

• G06F16/289 Primary

  Object oriented databases · CPC title

• G06F16/25

  Integrating or interfacing systems involving database management systems · CPC title

• G06F16/24552

  Database cache management · CPC title

• G06F16/284

  Relational databases · CPC title