Abstract: A system and method can support persistence in a distributed data grid, such as persistent store versioning and integrity. A resolver in the distributed data grid can receive a plurality of identifiers from one or more members of the distributed data grid, wherein each said identifier is associated with a persisted partition in a persistent storage for the distributed data grid. Then, the resolver can select an identifier for each partition, wherein each selected identifier is associated with a most recent valid version of a partition. Furthermore, the resolver can determine a member in the distributed data grid that is responsible for recovering said partition from a persisted partition associated with the selected identifier.

Abstract: A searching system and a searching method are provided and perform packaged searching for information regarding a plurality of objects displayed on a map. As a result, searching may be performed on searching target objects selected by a user, and keywords may be mapped to the selected search target objects to enable packaged searching.

Abstract: Data to be stored in a data block for a columnar database table may be compressed according to a multi-level compression scheme. Data to be stored in the data block may be received. The data may be compressed according a column-specific compression technique to produce compressed data. The compressed data may then be compressed according to a second compression technique different than the column-specific compression technique to produce multi-level compressed data. The multi-level compressed data may be stored in the data block. When reading from the data block, multi-level compressed data may be decompressed according to the column-specific compression technique and the default compression technique applied to the data.

Abstract: Techniques for managing continuous queries that include subqueries are provided. In some examples, a continuous query that includes at least a subquery may be identified. Additionally, the subquery may be processed to obtain a first result or generate a logical subquery plan. Further, in some instances, the continuous query may then be processed based at least in part on the first result from the subquery or by merging a logical continuous query plan with the logical subquery plan. This may result in obtaining a second result via querying a data source with the continuous query that is based at least in part on the first result from the subquery and/or the merged plans.

Abstract: Techniques for counting event changes with archived relations are provided. In some examples, a query that identifies at least a data object may be identified. Additionally, the query may be evaluated against historical data associated with the data object. Additionally, in some instances, a listening service may be registered with the data object. Further, the query may be evaluated based at least in part on the data object and the historical data.

Abstract: A system, method and user interface for providing media or content recommendations are provided. More specifically, the system, method and user interface provide media recommendations including enabling a user to select a first media object, the first media object having a first set of characteristics, enabling the user to select a second media object, the second media object having a second set of characteristics, and recommending a plurality of additional media objects, each of the plurality of additional media objects having at least one characteristic in common with the first set of characteristics and at least one characteristic in common with the second set of characteristics.

Abstract: Disclosed are methods, systems, and computer program products for processing a file which include using a computer system that is programmed for performing a process of receiving the file in response to a request for storing the file, determining whether a database already contains the file, and storing the file in the database if the database does not already contain the file. The process may alternatively include receiving the file in response to a request for storing the file, determining whether a database already contains the file, and storing the file without storing the received file if the database already contains the file. The process may also alternatively include receiving the file in response to a request for storing the file in a database, separating the file into a plurality of portions, and storing the plurality of portions so each of the plurality of portions can be individually accessed.

Abstract: Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for generating query suggestions based on search data. In one aspect, a method includes receiving, by one or more computers, a first query, determining query refinements based on the first query, generating, from the query refinements, refinement clusters, each refinement cluster corresponding to a particular topic and each refinement cluster including query refinements that are determined to belong to the particular topic to which the refinement cluster corresponds, ranking the refinement clusters, and selecting the refinement cluster that is highest in the ranking relative to other refinement clusters in the ranking as a first search refinement cluster for the first query.

Abstract: In an approach, a database server maintains a container database which comprises: one or more pluggable databases, a root database that stores an undo log for rolling back transactions on the consolidated database, and a redo log for replaying modifications to the container database. The database server restores a particular pluggable with a backup version that corresponds to a first point in time. The database server generates a clone database loaded with a backup version of the root database that corresponds to the first point in time. The database server applies the redo log to recover the particular pluggable database and the clone database to a second point in time that is later than the first point in time. The database server identifies, based on the clone database, one or more active transactions on the particular pluggable database. The database server rolls back the one or more active transactions.

Abstract: A user of an online service sends a request to write a review of a media content item, using a text limited device such as a gamepad of a videogame console. In response to the request, one or more dictionaries are requested using metadata associated with the request such as the title of the movie or a genre associated with the movie. The dictionaries are received and used to populate user interface elements with words and phrases. Each user interface element corresponds to a sentence component such as a verb, noun, etc. The user may use the gamepad to cycle through the words and phrases in each user interface element to generate a sentence.

Abstract: An IMS DEDB database restructure operation creates an empty offline DEDB having the desired structure. The offline database is populated with data from a source (online) database while keeping the source database online (i.e., available for access and update operations). Updates to the source database made during this process are selectively processed in parallel with the offline DEDB load operation. When the contents of the offline database is substantially the same as the source or online database, the source database is taken offline, final updates to the offline database are applied whereafter the offline database is brought online, thereby replacing the source database. It is significant to note that updates occurring to the source or online DEDB are applied to the offline DEDB.

Abstract: Overflow access records (OARs) are managed in a database system. An OAR is created in response to receiving an update command for a data record and to the updated data record generated by the update command not fitting onto the page in the table where the data record was stored. The OAR that is created includes an index counter that indicates a number of indexes associated with the table. When an OAR is accessed in response to a query command, an identifier of the accessed OAR is replaced in the index by an identifier of a data record pointed to by the OAR, and the index counter in the accessed OAR is changed by a predefined amount. When the index counter reaches a predefined value, the accessed OAR is removed from the table.