Patent classifications
G06F16/122
Methods, systems and apparatuses to configure a flight management system (FMS)
Methods, systems, and apparatuses are provided for flight management to configure an aircraft configuration (config) file accessible by the avionic system wherein an avionic service is implemented by a flight management system (FMS) for corroborating allowance of access using one of a set of validation procedures for corroboration prior to execution of a request for content to the config file including validating that a user request for a session is authorized based on user identification data, that a client request by an Electronic Flight Bag (EFB) application for a session is authorized based on client identification data, and in response to the client request, determining that an EFB application request is encrypted and performing a decrypt procedure of the EFB application request based on private key data of a private key; and encrypting an EFB application response based on public key data of a public key from the config file.
Lightweight extension of core data services
Implementations of the present disclosure include receiving, by a parser, a view source file and an extension source file, the view source file defining a view on data stored in a database, the extension source file defining an extension to the view, parsing, by the parser, the view source file to provide a view abstract syntax tree (AST) and the extension source file to provide an extension AST, providing, by the parser, a merged AST based on the view AST and the extension AST, generating a mixed runtime data object using the merged AST, and providing the mixed runtime data object for consumption by at least one runtime component.
UPGRADING THE FILE SYSTEM OF OBJECTS IN A DISTRIBUTED STORAGE SYSTEM
An example method of upgrading a distributed storage object from a first version to a second version includes: querying metadata of a first component configured according to the first version of the distributed storage object, the metadata defining extents of data on a disk group of the first component; populating, for a second component configured according to the second version of the distributed storage object, logical and middle maps based on the metadata such that initial entries in the logical map point to initial entries in the middle map, and the initial entries in the middle map point to physical addresses of the disk group of the first component; and reading the data from the disk group of the first component and writing the data to a disk group of the second component while updating the initial entries in the middle map.
DATA MANAGEMENT
A computer-implemented method is provided for managing data stores. The method comprises performing a discovery process to discover a plurality of data stores. Each data store is identified, metadata associated with each data store is determined, and the metadata associated with each data store is stored in a configuration database. A user interface is operable to select at least one discovered and identified data store and initiate a change request to modify the selected data store. The change request is executed, based on an instruction received via the user interface, to modify the selected data storage set, and, upon execution of the change request, an update of the metadata in the configuration database associated with the selected data storage set is triggered.
Scalable architectures for reference signature matching and updating
Methods, apparatus, systems and articles of manufacture are disclosed for scalable architectures for reference signature matching and updating. An example method for scalable architectures for reference signature matching and updating includes accessing site signatures to be compared to reference signatures from a first group of media sources. The example method also include determining if a first reference node is an owner of a first one of the site signatures, comparing a neighborhood of site signatures including the first site signature to reference signatures in a first subset of reference signatures when the first reference node is the owner of the first site signature, the first subset of references signatures stored in a first memory partition associated with the first reference node, and not comparing site signature to reference signatures when the first reference node is not the owner of the first one of the site signatures.
Metadata control in a load-balanced distributed storage system
A plurality of computing devices are communicatively coupled to each other via a network, and each of the plurality of computing devices is operably coupled to one or more of a plurality of storage devices. A plurality of failure resilient address spaces are distributed across the plurality of storage devices such that each of the plurality of failure resilient address spaces spans a plurality of the storage devices. The plurality of computing devices maintains metadata that maps each failure resilient address space to one of the plurality of computing devices. The metadata is grouped into buckets. Each bucket is stored in a group of computing devices. However, only the leader of the group is able to directly access a particular bucket at any given time.
SYSTEMS AND METHOD FOR BOOTUP ACTIVATION OF FIRMWARE IMAGES
A storage device is disclosed. The storage device may include a first storage. The first storage may include a primary firmware slot to store a first firmware, a secondary firmware slot to store a second firmware, a primary file system slot to store an existing file system, and a secondary file system slot. The storage device may include a processor configured to execute the first firmware or the second firmware. The storage device may include a second storage for user data, the second storage configured to use the existing file system. The second firmware may include a tag indicating that the second firmware is subject to bootup activation.
META-FORMAT AND TECHNIQUE TO PRODUCE TUTORIALS FOR MULTIPLE PUBLISHING FORMATS
The present disclosure provides new and innovative systems and methods for publishing standardized data in a variety of formats. In an example, a computer-implemented method includes obtaining source data, wherein the source data is in a standardized format, obtaining target platform data comprising a target platform address and a target format, generating a directory structure based on the source data and the target format, generating target data based on the source data and the target format, wherein the target data is in the target format, packaging the target data in the directory structure, generating instructions based on the target platform data and the packaged data, and transmitting the packaged data and the instructions to a third-party server system identified by the target platform address.
Optimized content object storage service for large scale content
Provided are techniques for optimized content object storage service for large scale content. A content object file is created. An index entry for the content object file is created with a content object key and a content object location. The content object file is appended to an aggregated file on a storage node. In response to a request to retrieve the content object file from the aggregated file, the content object key is used to access the content object location that describes the storage node, a name of the aggregated file, an offset into the aggregated file, and a size of the content object file to retrieve the content object file.
Rule generation in a data governance framework
A computer system, computer program product, and a computer-implemented method for supplementing a data governance framework with one or more new data governance technical rules is disclosed. The method comprises providing a plurality of expressions and a first mapping. The expressions assign natural language patterns to technical language patterns. The first mapping maps first terms to data sources. A rule generator receives a new natural language (NL) rule comprising one or more natural-language patterns and one or more first terms. The rule generator resolves the new NL rule into one or more new technical rules interpretable by a respective rule engine and stores the one or more technical rules in a rule repository.