Abstract: Generating object morphisms during object search includes obtaining object-search request data, wherein the object-search request data includes object-search terms, obtaining resolved-request data representing the object-search terms, determining that a first analytical object partially consistent with the resolved-request data is available, wherein the first analytical object is consistent with a first portion of the resolved-request data, generating candidate object-morphism data with respect to the first analytical object in accordance with a second portion of the resolved-request data, outputting object-search response data including the candidate object-morphism data for presentation to a user, obtaining data indicating a selected object morphism from the candidate object-morphism data, generating a second analytical object in accordance with the first analytical object and the selected object morphism, wherein the second analytical object differs from the first analytical object, and outputting response

Abstract: Systems and methods for query generation based on a logical data model with one-to-one joins are described. For example, methods may include accessing a join graph representing tables in a database; receiving a first query; selecting a connected subgraph of the join graph that includes the two or more tables referenced in the first query; accessing an indication that a directed edge of the connected subgraph corresponds to a one-to-one join; modifying the connected subgraph based on the indication to obtain a modified subgraph; generating one or more leaf queries based on the modified subgraph; generating a query graph that specifies joining of results from queries based on the one or more leaf queries; invoking a transformed query on the database that is based on the query graph and the queries based on the one or more leaf queries.

Abstract: Systems and methods for mapping natural language to queries using a query grammar are described. For example, methods may include generating, based on a string, a set of tokens of a database syntax; generating a query graph for the set of tokens from a finite state machine representing a query grammar, wherein nodes of the finite state machine represent token types, directed edges of the finite state machine represent valid transitions between token types in the query grammar, vertices of the query graph correspond to respective tokens of the set of tokens, and directed edges of the query graph represent a transition between two tokens in a sequencing of the tokens; determining, based on a tour of the query graph, a sequence of the tokens in the set of tokens, forming a database query; and invoking a search of a database using a query based on the database query to obtain search results.

Abstract: Operating a low-latency database analysis system with phrase translation may include obtaining a locale-specific phrase localization rule and a canonical phrase localization rule for a phrase, generating a locale-specific index and a locale-specific finite state machine for the locale using the localization definition data and a canonical finite state machine, generating a resolved-request by obtaining a locale-specific token representing locale-specific input data by traversing the locale-specific index, obtaining a canonical token associated with locale-specific token, obtaining a locale-specific phrase by traversing the locale-specific finite state machine, obtaining a canonical phrase corresponding to the locale-specific phrase, the canonical phrase including the canonical token, generate a data-query based on the canonical phrase, obtaining results data responsive to the data expressing the usage intent by executing a query corresponding to the data-query by an in-memory database of the low-latency datab

Abstract: Operating a low-latency database analysis system using domain-specific chronometry may include obtaining chronometry configuration data including chronometric instance data describing an instance of a chronometric unit of a domain-specific chronometry dataset that describes an era, such that the chronometry configuration data includes respective chronometric instance data describing each instance of the first chronometric unit of the domain-specific chronometry dataset for the era of the domain-specific chronometry dataset, generating, in the low-latency database analysis system, a domain-specific chronometry dataset in accordance with the chronometry configuration data, such that the domain-specific chronometry dataset describes a chronometric unit such that a temporal location expressed with reference to the chronometric unit and indicative of an epoch value differs from a temporal location indicative of the epoch value and expressed in accordance with a canonical chronometry, and storing the domain-specifi

Abstract: Semantic analysis to resolve ambiguous user input data with respect to a request for data includes identifying tokens based on the text string, identifying a tables in a database, wherein a token indicates a column from a table and a token indicates a column from another table, identifying candidate join paths for joining tables, obtaining respective candidate results using the candidate join paths, outputting combined candidate results including values from the respective candidate results, obtaining second user input data indicating a selected value, identifying the request for data as unambiguous and identifying a selected join path based on the selected value, and, in response to identifying the request for data as unambiguous, outputting data responsive to the request for data using the selected join path.

Abstract: A request for database results is received from a query coordinator at a database instance of a distributed database. The request includes a query execution instruction of a query plan and an indication of override instructions corresponding to the query execution instruction. The override instructions are such that they do not modify the query plan. The database instance includes the override instructions in a set of high-level language query instructions. The database instance performs just-in-time compiling of the set of high-level language query instructions to obtain a machine language query for performing the query execution instruction of the query plan. The database instance executes the machine language query to obtain the database results. The database instance then transmits the database results to the query coordinator.

Abstract: A current set of context features for a database query that is associated with a string is identified. The database query includes a sequence of tokens of a database syntax, and the current set of context features includes words from the string and tokens from the database query. An inference record is selected from an inference store based on a comparison of the current set of context features to context features of inference records in the inference store. The database query is modified using a resolution of the inference record to obtain an inferred database query. The resolution includes one or more tokens of the database syntax. A search of a database is invoked using a query based on the inferred database query to obtain search results.

Abstract: A first replay log is replayed to generate a first replay result. Replaying the first replay log includes replacing, in the first replay result, a first value of a first field included in a first command in the first replay log with a first hash value responsive to a determination that the first field is not utilized as a condition in at least one command included in the first replay log. A second replay log is replayed to generate a second replay result. The first replay result and the second replay result are compared to verify that the first replay log and the second replay log are equivalent.

Abstract: A request to execute a database command is transmitted from a device to a database command execution device. The request includes a first indicator of a first set of tokens available at the device at a time that the request is transmitted. A response to the request is received. The response includes a second indicator of a second set of tokens available at the database command execution device at a time that the request is received at the database command execution device. Responsive to a determination that the second indicator is different from the first indicator, a request for updated tokens is transmitted to the database command execution device. The first set of tokens is updated based on a received response to the request for the updated tokens. A list of tokens the updated first set of tokens that match a partial token received as an input is output.

Abstract: Updating a constituent-data index includes determining whether sampling is currently contraindicated for the column, in response to determining that sampling is currently contraindicated for the column, omitting sampling the column, in response to determining that sampling is currently other than contraindicated for the column, sampling the column, determining whether updating the constituent-data index is currently contraindicated for the column, in response to determining that updating the constituent-data index is currently contraindicated for the column, omitting updating the constituent-data index with respect to the column, and in response to determining that updating is currently other than contraindicated for the column, updating the constituent-data index with respect to the column.

Abstract: Query execution on compressed in-memory data includes receiving, at a processor of an instance of a distributed in-memory database, a query for data from a table stored in the distributed in-memory database as compressed table data, obtaining results data responsive to the query from the table, and outputting the results data for presentation to a user. Obtaining results data includes allocating memory to identify allocated memory for decompressing the compressed table data, obtaining uncompressed table data by decompressing the compressed table data into the allocated memory, and obtaining the results data from the uncompressed table data. The allocated memory is deallocated in response to obtaining the results data. Compressing a table to form compressed table data is also described.

Abstract: Object scriptability includes receiving a high-level language script describing at least one data-analysis object, including a node representing the data-analysis object in a graph-based data structure including a plurality of nodes, where each node from the plurality of nodes represents a respective data-analysis object in a data analysis system, where each node from the plurality of nodes is connected to at least one other node from the plurality of nodes by an edge, and where the edge represents a relationship between the respective objects in the data analysis system.

Abstract: First images that are screenshots from a first version of a software component are obtained. Second images that are screenshots from a second version are obtained. A collection of image deviations that includes pair-wise image deviations between pairs of images are identified. A pair of images includes a first image from the first images and a corresponding second image from the second images. An image deviation indicates a portion of the second image identified as differing from a spatially corresponding portion of the first image. The image deviations are grouped into deviation groups. At least some of the second images are associated with at least some of the deviation groups. A subset of the second images corresponding to a deviation group is output responsive to a selection of an indication of the deviation group.

Abstract: A method includes obtaining first data expressing a first usage intent; obtaining an answer object; obtaining, in accordance with first access control data, a first visualization data for the answer object; associating, with the first visualization data, a first generation-identifier that corresponds to at least a subset of the first access control data; generating first instructions for rendering the first visualization data on a user device of the first user; receiving a first snapshot of the first visualization data; storing a first association between the first generation-identifier and the first snapshot; obtaining second data expressing a second usage intent from a second user; identifying the answer object responsive to the second data expressing the second usage intent from the second user; and, responsive to second access control data corresponding to the second user matching the first generation-identifier, outputting second instructions for rendering the first snapshot to the second user.

Abstract: A method and system may be implemented for automatically analyzing data in a database. A method for use in a low-latency database analysis system may include generating a schema. The schema may be based on a portion of an external database. The method may include storing the schema in an in-memory database. The method may include receiving a data-query. The method may include generating a resolved-request. The resolved-request may be based on the data-query and the stored schema. The stored schema may be used for executing the query on the external database. The method may include receiving results data responsive to the data-query from the external database. The method may include outputting the results data for display on a user interface.

Abstract: A replay tool configured in a learning mode is used to replay a recorded interaction workflow to obtain respective learning-mode test data responsive to a request from a client device to a server. A baseline response template is obtained from the respective learning-mode test data. A baseline response time of the request is also obtained from the respective learning-mode test data. The recorded interaction workflow is replayed in a testing mode to obtain testing-mode test data. Responsive to determining that a response body included in the testing-mode test data is inconsistent with the baseline response template, a first anomaly message is output. Responsive to determining that the response time included in the testing-mode test data is not within a tolerance of the baseline response time, a second anomaly message is output.

Abstract: Query planning in a distributed database that includes a table partitioned into shards according to a sharding criterion and distributed to database instances includes receiving a data-query. The data-query includes a “distinct count” clause on a first column and a “group by” clause on least a second column. A query plan is formulated to include respective instructions for converting, at at least some of the database instances, distinct values of the first column grouped by values of the second column into a count of the distinct values grouped by the values of the second column to obtain respective intermediate results; instructions for receiving the respective intermediate results from at least a subset of the at least some of the database instances; and instructions for concatenating the respective intermediate results using a summing operation to obtain the first “distinct count” of the first column grouped by the second column.

Abstract: A low-latency database analysis system using an object index may include obtaining data expressing a usage intent, and, in response to a determination that the data expressing the usage intent includes object search request data including a user identifier and zero or more object search terms, obtaining, from an object-index responsive to the object search request data, object indexing data for an object, obtaining object detail data for the object, obtaining an object visualization capture for the object, and outputting object search response data including the object visualization capture and at least a portion of the object detail data for presentation to a user.

Abstract: Systems and methods for query generation based on merger of subqueries are described. For example, methods may include accessing a first join graph representing tables in a database, wherein the first join graph has vertices corresponding to respective tables in the database and directed edges corresponding to join relationships; receiving a first query specification that references data in two or more of the tables of the database to specify multiple subqueries in a set of subqueries; checking that two or more subqueries from the set of subqueries have the same join graph; checking that the two or more subqueries have the same set of grouping columns; responsive, at least in part, to the two or more subqueries having the same join graph and the same set of grouping columns, merging the two or more subqueries to obtain a consolidated query.