Abstract: Systems, methods, and apparatus are disclosed for identifying and analyzing online advertising performance data. Systems may receive data records that include data events characterizing interactions between users and online advertisement campaigns. The online advertising data records may include timestamp data characterizing creation dates for data events. The systems may generate intermediate data objects by partitioning at least some of the online advertising data records based on a first plurality of temporal data categories representing different units of time. Each intermediate data object may be associated with a temporal data category of the first plurality of temporal data categories. The systems may generate performance data objects by partitioning the intermediate data objects based on a second plurality of temporal data categories that are different than the first temporal data categories.

Abstract: A method of managing on-line user data in a table-level distributed database system is disclosed. At a loading interface, a load request from a client device specifying a new or updated data table, which has been populated in a distributed file system, is received. The load request also specifies a location in the distributed file system and a schema of the data table. The loading interface creates new records in a metadata store, and each new record specifies a mapping between the data table and a particular instance that is to load such data table. Each record also specifies the location and schema for such data table. Based on the new records, each instance also loads the data table. Each instance publishes, in the metadata store, load status specifying that loading of the data table is complete so that such data table can be queried by a query client.

Abstract: A method of managing on-line user data in a table-level distributed database system is disclosed. At a loading interface, a load request from a client device specifying a new or updated data table, which has been populated in a distributed file system, is received. The load request also specifies a location in the distributed file system and a schema of the data table. The loading interface creates new records in a metadata store, and each new record specifies a mapping between the data table and a particular instance that is to load such data table. Each record also specifies the location and schema for such data table. Based on the new records, each instance also loads the data table. Each instance publishes, in the metadata store, load status specifying that loading of the data table is complete so that such data table can be queried by a query client.

Abstract: Systems, methods, and apparatus are disclosed for identifying and analyzing online advertising performance data. Systems may receive data records that include data events characterizing interactions between users and online advertisement campaigns. The online advertising data records may include timestamp data characterizing creation dates for data events. The systems may generate intermediate data objects by partitioning at least some of the online advertising data records based on a first plurality of temporal data categories representing different units of time. Each intermediate data object may be associated with a temporal data category of the first plurality of temporal data categories. The systems may generate performance data objects by partitioning the intermediate data objects based on a second plurality of temporal data categories that are different than the first temporal data categories.

Abstract: Methods and systems are provided that may be utilized for spilling in query processing environments.

Abstract: A system and method for preventing a count-to-infinity problem in a network using epochs of sequence numbers in protocol messages to eliminate stale protocol information in the network and to allow the forwarding topology to recover in merely one round trip time across the network.

Abstract: A system and method for preventing a count-to-infinity problem in a network using epochs of sequence numbers in protocol messages to eliminate stale protocol information in the network and to allow the forwarding topology to recover in merely one round trip time across the network.