Abstract: A search index is generated from one or more data records, wherein the one or more data records have contents in a plurality of different fields. Field information of the one or more data records is stored in the search index as specialized indexed elements, wherein the specialized indexed elements overlap with other indexed elements of the one or more data records. A search query is received from a user allowed to access only a portion of the plurality of different fields. The search query is processed within the portion of the plurality of different fields using the search index including the specialized indexed elements.

Abstract: A search index is generated from one or more data records, wherein the one or more data records have contents in a plurality of different fields. Field information of the one or more data records is stored in the search index as specialized indexed elements, wherein the specialized indexed elements overlap with other indexed elements of the one or more data records. A search query is received from a user allowed to access only a portion of the plurality of different fields. The search query is processed within the portion of the plurality of different fields using the search index including the specialized indexed elements.

Abstract: Documents and data are analyzed to determine one or more data facets. The documents, data and other information contained therein may be presented according to statistically-determined groupings based on the data facets.

Abstract: Messages are processed to guarantee proper work scheduling and allow for cyclic and conditional processing. A processing node requiring ordered processing of messages is configured to operate within a plurality of successive processing nodes not requiring ordering processing of messages. Nodes upstream of the ordered node (i) monitor skew between the messages being processed and messages that are ordered after the messages still being processed and that have been forwarded downstream of the node and (ii) pause processing upon reaching skew limits. The nodes upstream of the ordered node limit output of messages to be within a delta of other messages as defined by message IDs. In addition, messages removed from a flow path are replaced by Null messages for ordered processing. Child messages are encoded to incorporate parent IDs preserving ordering systems.

Abstract: Techniques and systems for indexing and retrieving data and documents stored in a record-based database management system (RDBMS) utilize a search engine interface. Search-engine indices are created from tables in the RDBMS and data from the tables is used to create “documents” for each record. Queries that require data from multiple tables may be parsed into a primary query and a set of one or more secondary queries. Join mappings and documents are created for the necessary tables. Documents matching the query string are retrieved using the search-engine indices and join mappings.

Abstract: Messages are processed to guarantee proper work scheduling and allow for cyclic and conditional processing. A processing node requiring ordered processing of messages is configured to operate within a plurality of successive processing nodes not requiring ordering processing of messages. Nodes upstream of the ordered node (i) monitor skew between the messages being processed and messages that are ordered after the messages still being processed and that have been forwarded downstream of the node and (ii) pause processing upon reaching skew limits. The nodes upstream of the ordered node limit output of messages to be within a delta of other messages as defined by message IDs. In addition, messages removed from a flow path are replaced by Null messages for ordered processing. Child messages are encoded to incorporate parent IDs preserving ordering systems.

Abstract: Techniques and systems for indexing and retrieving data and documents stored in a record-based database management system (RDBMS) utilize a search engine interface. Search-engine indices are created from tables in the RDBMS and data from the tables is used to create “documents” for each record. Queries that require data from multiple tables may be parsed into a primary query and a set of one or more secondary queries. Join mappings and documents are created for the necessary tables. Documents matching the query string are retrieved using the search-engine indices and join mappings.