Abstract: The present disclosure relates to chatbot systems, and more particularly, to techniques for identifying an explicit invocation of a chatbot and determining an input for the chatbot being invoked. In certain embodiments, explicit invocation analysis involves detecting an invocation name in an utterance. The invocation name is an identifier assigned to a particular chatbot. In response to detection of the invocation name, the utterance is refined for input to the particular chatbot by determining which parts of the utterance, if any, contain relevant information for the particular chatbot and generating a new utterance, using the relevant parts of the utterance, for processing by the particular chatbot. The refining can involve removal of a portion of the utterance associated with the invocation name.

Abstract: A database server stores compressed units in data blocks of a database. A table (or data from a plurality of rows thereof) is first compressed into a “compression unit” using any of a wide variety of compression techniques. The compression unit is then stored in one or more data block rows across one or more data blocks. As a result, a single data block row may comprise compressed data for a plurality of table rows, as encoded within the compression unit. Storage of compression units in data blocks maintains compatibility with existing data block-based databases, thus allowing the use of compression units in preexisting databases without modification to the underlying format of the database. The compression units may, for example, co-exist with uncompressed tables. Various techniques allow a database server to optimize access to data in the compression unit, so that the compression is virtually transparent to the user.

Abstract: A method and system is provided for reducing delay to applications connected to a database server that guarantees no data loss during failure or disaster. After storing a log record persistently in a local primary log, the log writer returns control to the application which continues running concurrently with the database server sending the session's log records to a standby database. A separate back channel is used by the standby to communicate, out-of-band to the primary, the location of the last log record stored persistently to the standby log. An application waiting for a transaction to commit may wait until the transaction's commit record has been persisted. Also described is a technique for reducing application delay when there is contention between nodes of a multi-node cluster for updating the same block. The technique provides for an asynchronous ping protocol that guarantees zero data loss during failure or disaster.