Palantir Technologies Inc.

David Vogelbacher

Helen Yu

Jeremy Liu

Natacha Gabbamonte

Christopher Dugan

Eoin Morgan

Aditya Chaturvedi

Joseph Kane

Jiawei Wu

Systems and methods are provided for providing an interface for accessing a data analysis workbook through which data can be accessed and manipulated using a plurality of programming languages and application programming interfaces (APIs). Input data on which one or more data transformations are to be performed within the data analysis workbook can be accessed, wherein the input data corresponds to a first object representation of a dataset, and wherein the one or more data transformations require the dataset to be a different, second object representation of the dataset. The second object representation of the dataset can be extracted from the first object representation of the dataset through a first language delegate that manages data associated with the first object representation. The one or more data transformations can be applied to the extracted second object representation of the dataset through a different, second language delegate that manages data associated with the second object representation.

Multi-language object cache

Whether a logical query plan to derive a target dataset from one or more source datasets is available is determined. Responsive to determining that the logical query plan is not available for the transformation code in the first programming language, relationships between the source columns of the one or more source datasets and the respective target columns of the target dataset are inferred. Target column metadata for a target column of the target dataset is generated. The target column metadata reflects the inferred relationships between the source columns of the one or more source datasets and the respective target columns. The target column metadata for the target column of the target dataset is stored.

Column lineage and metadata propagation

A logical query plan to derive a target dataset from one or more source datasets is identified. The logical query plan defines source columns of the one or more source datasets and respective target columns of the target dataset. The logical query plan is parsed to derive relationships between the source columns of the one or more source datasets and the respective target columns of the target dataset. Target column metadata is generated for a target column of the target dataset. The target column metadata reflects a derived relationship between one or more source columns and the target column and existing source column metadata of each of the one or more source columns. The target column metadata is stored for the target column of the target dataset.

Growing community of inventors

New York, NY, United States of America

David Vogelbacher