System and methods for object version tracking and read-time/write-time data federation

Patent metadata

Field	Value
Publication number	US-2026079902-A1
Application number	US-202519402984-A
Country	US
Kind code	A1
Filing date	Nov 27, 2025
Priority date	Dec 8, 2017
Publication date	Mar 19, 2026
Grant date	—

Abstract

Systems and methods are provided in order to avoid ingesting the entire contents of one or more data sources. An object may be associated with one or more pieces/fragments of data that can be stored in different data sources. When a request for the object is initiated, a search for those pieces/fragments of data can be performed. Nodes associated with each data source may generate data queries appropriate for its corresponding data source, retrieve, and if needed transform the data into an object-based data structure. Any pieces/fragments of data that have been discovered and retrieved can be joined, e.g., by an application programming interface server, and forwarded to a requesting client or application. In this way, only data relevant to the object is obtained. Moreover, object versioning can be employed so that the most up-to-date data is obtained.

First claim

1 . A system for analyzing data, comprising:
one or more processors, the processors comprising adapter nodes; and a memory storing instructions that, when executed by the one or more processors, cause the system to:
receive a request, from an application, for an object;
retrieve, from a first datastore using a first adapter node, first data fragments making up or associated with the requested object, wherein retrieving the first data fragments comprises generating, by the first adapter node, a first query according to a first query type based on a first data type of the first data fragments;
generate a second adapter node configured to retrieve second data fragments making up or associated with the requested object from a second datastore;
retrieve, from the second datastore using the second adapter node, the second data fragments, wherein retrieving the second data fragments comprises generating, by the second adapter node, a second query according to a second query type based on a second data type of the second data fragments, wherein the first query type is incompatible with retrieval of the second data fragments;
join the first and second data fragments; and
transmit the joined data fragments to the application.

2 . The system of claim 1 , wherein the instructions that, when executed by the one or more processors, cause the system to:
receive, from the first datastore, an indication of a new version of a first data fragment, the new version of the first data fragment making up or associated with the requested object; in response to receiving the indication of the new version of the first data fragment, generate a third adapter node to retrieve the new version of the first data fragment; and retrieve, from the first datastore, using the third adapter node, the new version of the first data fragment; join the new version of the first data fragment to the second data fragments; and transmit the joined new version to the application.

3 . The system of claim 1 , wherein the instructions that, when executed by the one or more processors, cause the system to:
perform, by the first adapter node, a first transformation of a first transformation type following retrieval of the first data fragments according to a first schema of the first datastore or an ontology of the application; and perform, by the second adapter node, a second transformation of a second transformation type following retrieval of the second data fragments according to a second schema of the second datastore or the ontology of the application.

4 . The system of claim 1 , wherein the instructions further cause the system to:
inactivate the first adapter node in response to determining that the first data fragments have changed a version or a data fragment type, and determining that the first data fragments no longer belong to the first data type.

5 . The system of claim 1 , wherein, the instructions further cause the system to:
indicate that the retrieving of the data fragments has been partially completed; and transmit a partial object view to the application.

6 . The system of claim 1 , wherein the instructions further cause the system to:
receive an indication that the first data fragments have updated a version; and in response to receiving the indication, reingesting, at the application, a new version of the first data fragments.

7 . The system of claim 1 , wherein the joining of the data fragments comprises converting a first data fragment of a first data type by a first adapter node and a second data fragment of a second data type by a second adapter node into a standardized data type.

8 . The system of claim 1 , wherein the instructions that, when executed by the one or more processors, cause the system to:
in response to a changed ontology of the application, transforming the retrieved first data fragments and the second data fragments based on the changed ontology prior to joining the first and second data fragments.

9 . A method being implemented by a computing system including one or more physical processors and storage media storing machine-readable instructions, the method comprising:
receiving a request, from an application, for an object; retrieving, from a first datastore using a first adapter node, first data fragments making up or associated with the requested object, wherein retrieving the first data fragments comprises generating, by the first adapter node, a first query according to a first query type based on a first data type of the first data fragments; generating a second adapter node configured to retrieve second data fragments making up or associated with the requested object from a second datastore; retrieving, from the second datastore using the second adapter node, the second data fragments, wherein retrieving the second data fragments comprises generating, by the second adapter node, a second query according to a second query type based on a second data type of the second data fragments, wherein the first query type is incompatible with retrieval of the second data fragments; joining the first and second data fragments; and transmitting the joined data fragments to the application.

10 . The method of claim 9 , further comprising:
receiving, from the first datastore, an indication of a new version of a first data fragment, the new version of the first data fragment making up or associated with the requested object; in response to receiving the indication of the new version of the first data fragment, generating a third adapter node to retrieve the new version of the first data fragment; and retrieving, from the first datastore, using the third adapter node, the new version of the first data fragment; joining the new version of the first data fragment to the second data fragments; and transmitting the joined new version to the application.

11 . The method of claim 9 , further comprising:
performing, by the first adapter node, a first transformation of a first transformation type following retrieval of the first data fragments according to a first schema of the first datastore or an ontology of the application; and performing, by the second adapter node, a second transformation of a second transformation type following retrieval of the second data fragments according to a second schema of the second datastore or the ontology of the application.

12 . The method of claim 9 , further comprising:
inactivating the first adapter node in response to determining that the first data fragments have changed a version or a data fragment type, and determining that the first data fragments no longer belong to the first data type.

13 . The method of claim 9 , further comprising:
indicating that the retrieving of the data fragments has been partially completed; and transmitting a partial object view to the application.

14 . The method of claim 9 , further comprising:
receiving an indication that the first data fragments have updated a version; and in response to receiving the indication, reingesting, at the application, a new version of the first data fragments.

15 . The method of claim 9 , wherein the joining of the data fragments comprises converting a first data fragment of a first data type by a first adapter node and a second data fragment of a second data type by a second adapter node into a standardized data type.

16 . The method of claim 9 , further comprising:
in response to a changed ontology of the application, transforming the retrieved first data fragments and the second data fragments based on the changed ontology prior to joining th

Assignees

• Palantir Technologies Inc

Inventors

• Wilczynski Peter
• Ryan Alexander
• Chang Allen
• Cervelli Daniel
• Tibshirani Julie
• Wilson Timothy

Classifications

• G06F16/2456

  Join operations · CPC title

• G06F16/256

  in federated or virtual databases · CPC title

• G06F16/2474

  Sequence data queries, e.g. querying versioned data · CPC title

• G06F16/219 Primary

  Managing data history or versioning (querying versioned data G06F16/2474; querying temporal data G06F16/2477) · CPC title

• G06F16/2458 Primary

  Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries · CPC title