Patent classifications
G06F16/2474
PROFILE DATA EXTENSIONS
A method for providing generating data extensions for a first data profile includes receiving a request for historical data, the data being associated with a first data profile, the first data profile being generated from data supplied by a data source system, creating a data model for obtaining the historical data based on data from at least one of the first data profile, a second data profile, or the data source system, executing the data model to obtain the historical data, and storing the historical data as a data extension of the first data profile. The first data profile and the data extension of the first data profile may be generated and stored separately, and the data extension of the first data profile is generated on the fly at runtime.
SYSTEMS AND METHODS FOR ATOMIC PUBLICATION OF DISTRIBUTED WRITES TO A DISTRIBUTED DATA WAREHOUSE
Systems and methods for managing data. The methods comprise: receiving, by a load driver node of a network, a request for upload of source data associated with a resource name to a data warehouse; generating a publication identifier and a version value for the source data by the load driver node in response to the request; causing, by the load driver node, operations to be performed by load worker nodes to facilitate population of at least one fact table of the data warehouse with the publication identifier and the source data; and causing, by the load driver node, a publication table of the data warehouse to be updated to include the publication identifier and the version value so as to be associated with the resource name.
SYSTEMS AND METHODS FOR CACHING OF MANAGED CONTENT IN A DISTRIBUTED ENVIRONMENT USING A MULTI-TIERED ARCHITECTURE INCLUDING OFF-LINE ACCESS TO CACHED CONTENT
Embodiments as disclosed provide a distributed caching solution that improve the performance and functionality of a content management platform for sites that are physically or logically remote from the primary site of the content management platform. In particular, according to embodiments, a remote cache server may be associated with a remote site to store local copies of documents that are managed by the primary content management platform. Periodically, a portion of the remote site's cache may be synchronized with the content management platform's primary site using an extensible architecture to ensure that content at the remote cache server is current.
METHOD AND APPARATUS FOR STORING AND QUERYING TIME SERIES DATA, AND SERVER AND STORAGE MEDIUM THEREOF
Disclosed are a method and apparatus for storing and querying time series data. The method includes: determining a data type of data to be stored; compressing the data to be stored by a data compression method corresponding to the data type; storing compressed data to a data storage table corresponding to the data type; receiving a query request including a query data type and a query time condition; querying target data that meets the query time conditions from a data storage table corresponding to the query data type. In the embodiments of the present disclosure, different compression methods are adopted for different types of data, which improves the compression efficiency of time series data and save storage resources. Moreover, when performing data query, time series data that meets a query time condition is searched in a data storage table corresponding to a query data type, which improves the query efficiency of different types of time series data.
Efficient real-time hierarchy using change events
Techniques for providing an efficient real-time hierarchy based on change events are disclosed. In some embodiments, a computer-implemented method comprises: storing a hierarchy table comprising hierarchy data that represents a snapshot state of a hierarchy tree of entities at a first point in time and having been last updated at the first point in time; receiving one or more user requests to change entity data representing entities of the hierarchy tree; storing one or more change events in a queue based on the user request(s); receiving a query request for the hierarchy tree; in response to the receiving of the query request, generating a query result based on the hierarchy table stored in the database and the change event(s) stored in the queue; and performing a function of an enterprise application platform using the query result.
Adding a read-only query engine to perform queries to a point-in-time of a write-accessible database
A database system may add a read-only query engine to perform read-only queries associated with points-in-time of a database. In various embodiments, the read-only query engine may be added in response to a manual request, an automatic refresh of a network endpoint, a query specifying a point-in-time, or a connection request. The read-only query engine may perform the point-in-time queries on a version the database at the point-in-time and return results for the queries. Upon completion of the queries or at a determined time, the database system may remove the read-only query engine. The specified point-in-time may refer to a current time, a prior time, or a future time with respect to the current time.
CLOUD APPLICATION MANAGEMENT USING INSTANCE METADATA
Various examples described herein are directed to systems and methods for managing a cloud-implemented database management application, the method comprising. At least one cloud service may receive a request from a first user group to launch a first instance of the database management application. The at least one cloud service may access a version metadata record for the database management application and use the version metadata record to launch the first instance of the database management application. The at least one cloud service may store first instance metadata for first instance of the database management application at a container management metadata persistence associated with the first instance of the database management application. The first instance metadata may comprise an indication of the first container image.
Data versioning in a multi-datacenter topology
Techniques are disclosed relating to data versioning in a multi-datacenter topology. In various embodiments, a computer system at a first datacenter may execute a query at a first point in time against a particular dataset that is maintained at the first datacenter. The particular dataset includes a first data record with a corresponding version number, where the version number is associated with a value of the first data record at the first point in time. In response to the first query, the computer system may receive a first results dataset that includes the first data record with its corresponding version number. The computer system may then store information indicative of the results dataset that is usable to retrieve, at a subsequent time from a historical version of the particular dataset at a second datacenter, the first data record with the same value as at the first point in time.
Asynchronous and parallel application processing
Input records are obtained based on a request to process an application. References to the input records are stored as entries in a queue. A total thread number for threads and a total server number for servers are determined. The threads are initiated on the servers and are asynchronously processed in parallel on the servers. Each thread obtains a reference from a unique entry of the queue, marks that entry as being addressed, processes the input record corresponding to the entry using values provided with a request to process the application, stores results associated with processing the input record in a data store, and iterates back to obtain a next unique entry from the queue until every entry of the queue is marked as having been addressed. When every entry of the queue is marked, a reference is returned to the data store as application results for processing the application.
Methods and systems for optimizing therapy using stimulation mimicking natural seizures
Systems, methods, and devices for automatic generation of a stimulation therapy that mimics electrographic activity in the brain at natural seizure termination define a stimulation therapy to be generated by an implanted component of a medical device system and delivered to a subject through identifying data characterizing a patient's seizures, especially at termination. A machine learning model identifies the seizures or seizure types from which to establish a canonical seizure or seizure type, and an algorithm translates the canonical seizure or seizure type into data that can be used to characterize a stimulation therapy. The systems, methods, and devices, include those configured to deliver the stimulation therapy that emulates the canonical seizure or seizure type when the seizure is detected, with the aim of terminating the seizure sooner than it would terminate without intervention.