Abstract: A version control interface for data provides a layer of abstraction that permits multiple readers and writers to access data lakes concurrently. An overlay file system, based on a data structure such as a tree, is used on top of one or more underlying storage instances to implement the interface. Each tree node tree is identified and accessed by means of any universally unique identifiers. Copy-on-write with the tree data structure implements snapshots of the overlay file system. The snapshots support a long-lived master branch, with point-in-time snapshots of its history, and one or more short-lived private branches. As data objects are written to the data lake, the private branch corresponding to a writer is updated. The private branches are merged back into the master branch using any merging logic, and conflict resolution policies are implemented. Readers read from the updated master branch or from any of the private branches.

Abstract: A version control interface provides for time travel with metadata management under a common transaction domain as the data. Examples generate a time-series of master branch snapshots for data objects stored in a data lake, with the snapshot comprising a tree data structure such as a hash tree and associated with a time indication. Readers select a master branch snapshot from the time-series, based on selection criteria (e.g., time) and use references in the selected master branch snapshot to read data objects from the data lake. This provides readers with a view of the data as of a specified time.

Abstract: A version control interface provides for accessing a data lake with transactional semantics. Examples generate a plurality of tables for data objects stored in the data lake. The tables each comprise a set of name fields and map a space of columns or rows to a set of the data objects. Transactions read and write data objects and may span a plurality of tables with properties of atomicity, consistency, isolation, durability (ACID). Performing the transaction comprises: accumulating transaction-incomplete messages, indicating that the transaction is incomplete, until a transaction-complete message is received, indicating that the transaction is complete. Upon this occurring, a master branch is updated to reference the data objects according to the transaction-incomplete messages and the transaction-complete message. Tables may be grouped into data groups that provide atomicity boundaries so that different groups may be served by different master branches, thereby improving the speed of master branch updates.

Abstract: A version control interface for data provides a layer of abstraction that permits multiple readers and writers to access data lakes concurrently. An overlay file system, based on a data structure such as a tree, is used on top of one or more underlying storage instances to implement the interface. Each tree node tree is identified and accessed by means of any universally unique identifiers. Copy-on-write with the tree data structure implements snapshots of the overlay file system. The snapshots support a long-lived master branch, with point-in-time snapshots of its history, and one or more short-lived private branches. As data objects are written to the data lake, the private branch corresponding to a writer is updated. The private branches are merged back into the master branch using any merging logic, and conflict resolution policies are implemented. Readers read from the updated master branch or from any of the private branches.

Abstract: Methods, apparatus, and systems are disclosed for determining a duration and/or risk estimate of performing a maintenance operation in a networked computing environment. An example apparatus includes a client data datastore to store telemetry data, associated with the maintenance operation, system configuration data, and a first secret, all received from a first virtual computing component operating in a virtual computing environment. The apparatus further includes a configuration comparator to identify configuration changes between a previous and current configuration of the virtual computing environment. A client data analyzer selects, based on the changes, an analysis model, and applies the model to generate results including the duration estimate or a risk of failure.

Abstract: Methods, apparatus, systems and articles of manufacture are disclosed for analyzing telemetry data in a networked computing environment. An example apparatus includes a client data datastore to store telemetry data and a first secret, the telemetry data and the first secret received from first computing environment; a client data analyzer to: apply a previously trained model to the telemetry data to determine an analysis result; and store the analysis result in association with the first secret; and a result interface to, in response to a request including a second secret: retrieve the stored result associated with the first secret that matches the second secret; transmit the stored results to the source of the request.

Abstract: Methods, apparatus, systems and articles of manufacture are disclosed for analyzing telemetry data in a networked computing environment. An example apparatus includes a client data datastore to store telemetry data and a first secret, the telemetry data and the first secret received from first computing environment; a client data analyzer to: apply a previously trained model to the telemetry data to determine an analysis result; and store the analysis result in association with the first secret; and a result interface to, in response to a request including a second secret: retrieve the stored result associated with the first secret that matches the second secret; transmit the stored results to the source of the request.

Abstract: Methods, apparatus, and systems are disclosed for determining a duration and/or risk estimate of performing a maintenance operation in a networked computing environment. An example apparatus includes a client data datastore to store telemetry data, associated with the maintenance operation, system configuration data, and a first secret, all received from a first virtual computing component operating in a virtual computing environment. The apparatus further includes a configuration comparator to identify configuration changes between a previous and current configuration of the virtual computing environment. A client data analyzer selects, based on the changes, an analysis model, and applies the model to generate results including the duration estimate or a risk of failure.

Abstract: Distributed locks (e.g., among a plurality of database management services) can be used for accessing a database to ensure data consistency in the database during concurrent continuous data processing and schema or data administration of the database. An exclusive lock of the database may not be held for all operations of an extract, transform, load (ETL) process to load data from a data source into the database. Schema changes that occur to a database schema of the database in the middle of the ETL process when the exclusive lock is not held can be resolved.

Abstract: The current document is directed to methods and systems that collect data within computing facilities according to data-collection specifications contained in data-collection manifests and that export a specified portion of the collected data to remote data-processing and data-analysis systems based on data-export specifications encoded within data-export whitelists. In a disclosed implementation, collected data is hierarchically encoded within a file or document that is efficiently processed, using one or more regular expressions that comprise a data-export whitelist, to extract the specified portion of the collected data for export to a remote data-processing and data-analysis system.

Abstract: Embodiments of the present disclosure relate to techniques for using distributed locks (e.g., among a plurality of database management services) for accessing a database to ensure data consistency in the database during concurrent continuous data processing and schema or data administration of the database. In particular, certain embodiments relate to not holding an exclusive lock of the database for all operations of an extract, transform, load (ETL) process to load data from a data source into the database. Further, certain embodiments relate to resolving schema changes that occur to a database schema of the database in the middle of the ETL process when the exclusive lock is not held.