G06F16/1873

Methods and apparatus for efficiently implementing a fast-copyable database

A fast-copyable database apparatus includes a processor and a memory in electronic communication with the processor. The memory stores a database table with multiple records each having a compound key including a version identifier. The memory also stores instructions executable to cause the processor to generate a first virtual clone of the database table and a second virtual clone of the database table, receive a query at the first virtual clone, and modify the query so that it includes a version identifier of the first virtual clone. The processor can query the database table using the modified query to generate a response based in part on each record from the set of records having a version identifier associated with an ancestral path of the version identifier of the first virtual clone, and send the response. Each compound key includes a version identifier and a data portion.

Hyperscaler independent versioning of cloud storage objects

A system and method to receive, by a backup service layer of a database service instance, a request to create a data backup; create, in response to the request and internally of the backup service, a backup having a filename including a version identifier; and transmit the created backup to a hyperscaler to be stored in a cloud object storage of the hyperscaler, the filename of the backup being a key for the storage of the backup in the cloud object storage.

Extensible version history and comparison within a backup

Described is a system for providing quick and efficient identification of a desired version of content from an editing history of the content. The system receives a search index identifying versions of content from an editing history of the content. The system sorts the search index according to sort criteria and receives a selection from the sorted search index of a first version of the content and a second version of the content. The system identifies and displays one or more content differences between the first and second versions of the content.

Model object management and storage system

A model management system provides a centralized repository for storing and accessing models. The model management system receives an input to store a model object in a first model state generated based on a first set of known variables. The model management system generates a first file including a first set of functions defining the first model state and associates the first file with a model key identifying the model object. The model management system receives an input to store the model object in a second model state having been generated based on the first model state and a second set of known variables. The model management system generates a second file including a second set of functions defining the second model state and associates the second file with the model key. The model management system identifies available versions of the model object based on the model key.

Data correlation using file object cache
11526371 · 2022-12-13 · ·

Some examples relate generally to computer architecture software for data classification and information security and, in some more particular aspects, to verifying audit events in a file system.

FILE MANAGEMENT SYSTEM, INFORMATION PROCESSING APPARATUS, IMAGE CAPTURING APPARATUS, AND FILE MANAGEMENT METHOD
20220394149 · 2022-12-08 ·

The present technology relates to a file management system, an information processing apparatus, an image capturing apparatus, and a file management method that enable a start of an image capturing operation before issuance of a formal file name.

The image capturing apparatus saves an image file including a captured image, with a temporary file name irrespective of whether or not the image capturing apparatus is connected to the information processing apparatus, and transmits the temporary file name to the information processing apparatus at an image capturing timing. The information processing apparatus fires a formal file name for the image file when the temporary file name is received. The present technology is applicable to, for example, a file management system that saves image files with sequential file names in a plurality of image capturing apparatuses.

Deduplicated data distribution techniques

In connection with a data distribution architecture, client-side “deduplication” techniques may be utilized for data transfers occurring among various file system nodes. In some examples, these deduplication techniques involve fingerprinting file system elements that are being shared and transferred, and dividing each file into separate units referred to as “blocks” or “chunks.” These separate units may be used for independently rebuilding a file from local and remote collections, storage locations, or sources. The deduplication techniques may be applied to data transfers to prevent unnecessary data transfers, and to reduce the amount of bandwidth, processing power, and memory used to synchronize and transfer data among the file system nodes. The described deduplication concepts may also be applied for purposes of efficient file replication, data transfers, and file system events occurring within and among networks and file system nodes.

Method to model server-client sync conflicts using version trees
11507541 · 2022-11-22 · ·

A file server and a method of operating a file server where version identifiers for documents on the server are maintained as a branched tree. When a client computer attempts to sync up a new version of a file, it must upload the version identifier that it received when it synced down the file. The file server compares this version identifier to the numbers in its version tree for the file and may place the document in the correct place in the tree structure, which may not be as the “latest version” of the document. If the client is using an outdated version of the document, the server may also sync down the latest version of the file. The user may view the changes to the version tree and reconcile different versions to create an authoritative version, and this review and reconciliation may occur at any time, instead of being performed at the moment that the file is saved or forking the file into a new filename.

DEDUPLICATED DATA DISTRIBUTION TECHNIQUES

In connection with a data distribution architecture, client-side “deduplication” techniques may be utilized for data transfers occurring among various file system nodes. In some examples, these deduplication techniques involve fingerprinting file system elements that are being shared and transferred, and dividing each file into separate units referred to as “blocks” or “chunks.” These separate units may be used for independently rebuilding a file from local and remote collections, storage locations, or sources. The deduplication techniques may be applied to data transfers to prevent unnecessary data transfers, and to reduce the amount of bandwidth, processing power, and memory used to synchronize and transfer data among the file system nodes. The described deduplication concepts may also be applied for purposes of efficient file replication, data transfers, and file system events occurring within and among networks and file system nodes.

INFORMATION PROCESSING DEVICE, INFORMATION PROCESSING SYSTEM, AND NON-TRANSITORY COMPUTER READABLE MEDIUM

An information processing device includes a processor configured to acquire: when an electronic document is posted to a message exchange service, information on a person who has posted the electronic document and information on update history of the electronic document; specify, based on the acquired information on the person who has posted the electronic document and the acquired information on the update history, a notification destination to whom a notification indicating that the electronic document has been posted is to be provided; and perform control for providing notification information containing at least information indicating the specified notification destination to the notification destination.