A method and system for executing database queries in parallel using a shared metadata store. The metadata store may reside on a master node, where the master node is the root node in a tree. The master node may distribute query plans and query metadata to other nodes in the cluster. These additional nodes may request additional metadata from each other or the master nodes as necessary.

A database security system protects a data table at both the column level and the individual data record level. Access to data records within the data table is governed by categories assigned to data records, by user roles assigned to users, and by a set of security access tables. A first access table maps data record identifiers to data record categories, data record protection schemes, and corresponding scheme keys. A second access table maps user roles to data record categories. A third access table maps column identifiers to column protection schemes and corresponding scheme keys. A fourth access table maps user roles to column identifiers. If a user requests access to a data record, the security access tables are queried using the data record identifier, the associated column identifier, and the user roles associated with the user to determine if the user can access the requested data record.

An information processing system includes a first information processing device configured to accept an input of a query to be processed, and a second information processing device configured to execute the query for each of a plurality of tasks in parallel. The first information processing device determines whether or not an external database server contains records targeted by the query, and transmit the query and a connection information for accessing the external database server to the second information processing device. The second information processing device connects to the external database server based on the connection information received from the first information processing device, acquires information indicating a storage status of the records targeted by the query among records stored in the external database server, and determines a processing target range for each of the plurality of tasks relevant to the records targeted by the query, based on the acquired information.

A content unification system is described herein that aligns related content from various sources into one unified stream. The system leverages tagging (e.g., hashtags or other added metadata associated with content) to filter and connect related content across sites, formats, and sources. One component of the system is a user-friendly and customizable “dash board” view of the various topics, called a “tagboard”. Tagboards can be quickly and easily created by users and can be embedded on any website. Users can interact with various content sources such as blogs, forums, or services without leaving the tagboard they are viewing. The content unification system provides users the tools to make the web efficient, increase user interaction, and increase the signal to noise ratio. The system also allows site owners and publishers to monetize their traffic better by directing advertisements to their content in real time.

A packet processing technique can include receiving a packet, and parsing the packet based on a protocol field to generate a parse result vector. The parse result vector is used to select between forwarding the packet to a virtual machine executing on a host processing integrated circuit, forwarding the packet to a physical media access controller, multicasting the packet to multiple virtual machines executing on the host processing integrated circuit, and sending the packet to a hypervisor.

A method, performed by one or more processors, including: receiving a user query; deriving, based on the user query, a search engine query for use with search engine software and a data access query for use with data access software; sending, to the search engine software, the search engine query to cause the search engine software to locate first data stored in a search engine index; sending, to the data access software, the data access query to cause the data access software to locate second data stored in a distributed data store; receiving, from the search engine software, the first data; and receiving, from the data access software, the second data.

The present disclosure relates to systems and methods for implementing a distributed search that allows a search engine to retrieve the correct results for a search request even if the search engine does not request the full results from each index shard originally requested in the search request.

A format conversion engine for Apache Hadoop that converts data from its original format to a database-like format at certain time points for use by a low latency (LL) query engine. The format conversion engine comprises a daemon that is installed on each data node in a Hadoop cluster. The daemon comprises a scheduler and a converter. The scheduler determines when to perform the format conversion and notifies the converter when the time comes. The converter converts data on the data node from its original format to a database-like format for use by the low latency (LL) query engine.

Systems and techniques for an information centric network (ICN) distributed search with approximate cache and forwarding information lookup. For example, a search interest packet may be received. Here, the search interest packet includes search criteria and a signal indicating that it is a search interest packet. A search for content—including content in a local content store—that meets the search criteria may then be performed. Once complete, a data packet that includes the results of the search may be transmitted towards an author of the search interest packet.

In one embodiment, a method includes receiving, at a network management system (NMS) from a client, a message having an object reference embedding a query, the query requesting an operation to be performed on data stored in a data tree maintained by the NMS. The method provides for generating, by the NMS, a result of the query by performing the operation on the data. In this embodiment, the method further provides for sending, by the NMS to the client, the result of the query. In some embodiments, the object reference may include a pathname.