Systems and methods herein describe embodiments for handling a data drift. An example system accesses the data pipeline, which is comprised of a plurality of stages. For each stage of the plurality of stages in the data pipeline, the system identifies stage schema fields for processing data in the data pipeline and generates a set of stage schema fields comprising the identified stage schema fields in the stage. In response to detecting an origin stage, the system generates a set of pipeline schema fields, whereby the set of pipeline schema fields comprise a union of the generated sets of stage schema fields. The set of pipeline schema fields are then stored.

A system and method of query processing in a multi-level storage system having a unified table architecture. A query is received by a common query execution engine connected with the unified table architecture, the query specifying a data record. The common query execution engine performs a look-up for the data record based on the query at the first level storage structure. If the data record is not present at the first level storage structure, the common query execution engine performs separate look-ups in each of the second level storage structure and the main store.

A system can present a first graph visual representation of data of a first database in a first user interface. The system can receive user data at the first user interface that is indicative of interacting with the first graph visual representation of the data. The system can determine graph metadata for the data of the first database from the user data. The system can store the graph metadata in a second database, wherein the first database is separate from the second database. The system can determine a second graph visual representation that comprises a combination of the data of the first database and the graph metadata of the second database. The system can present the second graph visual representation in a second user interface, wherein the second user interface comprises the first user interface or another user interface other than the first user interface.

Systems and methods include reception of an indication of a first data object to transmit from a first database tenant to a second database tenant, the first data object comprising user configuration settings metadata of a database application and associated with a first data object type, determination of whether a dependent data object may be associated with a data object of the first data object type, determination, if it is determined that a dependent data object may be associated with a data object of the first data object type, of whether a dependent object is dependent on the first data object, and automatic determination, if it is determined that a dependent object is dependent on the first data object, to transmit the dependent object from the first database tenant to the second database tenant.

This application relates to systems, methods, devices, and other techniques for a novel database schema change, recording and version control.

Various implementations of the present application set forth a method comprising generating a host extended reality (XR) environment representing a physical space that includes a real-world asset, generating, based on sensor data captured by a depth sensor on a mobile device, three-dimensional data representing the physical space, generating, based on sensor data captured by an image sensor on the mobile device, two-dimensional data representing the physical space, generating, based on the three-dimensional data and the two-dimensional data, an adaptable three-dimensional (3D) representation of the physical space, transforming the adaptable 3D representation into geometry data comprising a set of vertices, a set of faces comprising edges between pairs of vertices, and texture data, transmitting the geometry data to a set of one or more remote devices for at least a partial reconstruction of the adaptable 3D representation of the physical space in a set of one or more remote environments.

Various embodiments provide for replicating a share across deployments of a data platform, where the share can be on a source deployment and the share can be replicated on one or more target deployments, and where the share is replicated with one or more database objects of the source deployment associated with the share. Some embodiments analyze the share to be replicated and, based on the analysis, determine one or more database objects that would be replicated to the one or more target deployments to enable a replica of the share on the one or more target deployments.

A global secondary index method for a distributed database, includes: obtaining original data to be written in response to a database writing request; writing the original data into the distributed database; performing global secondary index processing on the original data written into the distributed database to obtain global secondary index data; establishing global secondary index tables between the global secondary index data and data table primary keys in the distributed database; and writing the global secondary index tables into an index shards based on an asynchronous processing manner.

Some embodiments provide a non-transitory machine-readable medium that stores a program. The program determines a set of data associated with a set of database schemas. The program further compares a first schema definition configured for a first application and a second schema definition configured for a second application. Based on the comparison, the program also generates a set of database commands for upgrading the set of schemas from the first schema definition to the second schema definition. Based on the set of commands and the set of data, the program further upgrades the set of database schemas from the first schema definition to the second schema definition.

A system and method for generating a column-oriented data structure repository for columns of single data types. The method includes: receiving instructions to generate a new column of a single data type for a first data structure, wherein the first data structure is a column oriented data structure; and storing, based on the instructions, the new column within the column-oriented data structure repository, wherein the column-oriented data structure repository is accessible to at least a second user account.