Abstract: In some example embodiments, a graphical user interface (GUI) is caused to be displayed on a computing device of a user. The GUI can be configured to enable the user to submit an identification of a dataset and at least one configuration parameter. The identification of the data source, the at least one configuration parameter, and the at least one wrangling parameter can be received via the GUI on the computing device. A sampling algorithm can be configured based on the at least one configuration parameter. A sample of data from the dataset can be generated using the configured sampling algorithm. At least one data wrangling operation can be performed on the sample of data based on the at least one wrangling parameter.

Abstract: Embodiments provide an overview visualization of graph data by rendering a graph's structure based upon different node/edge types, rather than upon a total number of nodes and/or edges. These node/edge types are recognized based upon associated metadata. The small number of different node/edge types of a typical graph reduces components for representation in the overview, simplifying that visualization and facilitating user interaction. A user can switch between the graph overview, and a different view affording node-level details. In analysis and/or querying, switching between the overview and the detailed visualization can afford natural and intuitive control over data granularity. For example the overview visualization of graph data may allow a user to initially filter on particular node types, with the subsequent node-level view permitting exploration of finer details while maintaining the overall context of the original graph.

Abstract: In some example embodiments, a graphical user interface (GUI) is caused to be displayed on a computing device of a user. The GUI can be configured to enable the user to submit an identification of a dataset and at least one configuration parameter. The identification of the data source, the at least one configuration parameter, and the at least one wrangling parameter can be received via the GUI on the computing device. A sampling algorithm can be configured based on the at least one configuration parameter. A sample of data from the dataset can be generated using the configured sampling algorithm. At least one data wrangling operation can be performed on the sample of data based on the at least one wrangling parameter.

Abstract: In some example embodiments, a graphical user interface (GUI) is caused to be displayed on a computing device of a user. The GUI can be configured to enable the user to submit an identification of a dataset and at least one configuration parameter. The identification of the data source, the at least one configuration parameter, and the at least one wrangling parameter can be received via the GUI on the computing device. A sampling algorithm can be configured based on the at least one configuration parameter. A sample of data from the dataset can be generated using the configured sampling algorithm. At least one data wrangling operation can be performed on the sample of data based on the at least one wrangling parameter.

Abstract: In some example embodiments, a graphical user interface (GUI) is caused to be displayed on a computing device of a user. The GUI can be configured to enable the user to submit an identification of a dataset and at least one configuration parameter. The identification of the data source, the at least one configuration parameter, and the at least one wrangling parameter can be received via the GUI on the computing device. A sampling algorithm can be configured based on the at least one configuration parameter. A sample of data from the dataset can be generated using the configured sampling algorithm. At least one data wrangling operation can be performed on the sample of data based on the at least one wrangling parameter.

Abstract: Methods, systems, and computer program products for visually representing and displaying data are described. The visual representation may be a data animation. A data query may be submitted, a time measurement for processing the query may be obtained, and a sample size of the query may be adjusted based on the time measurement and a frame refresh rate of a data animation. A data animation may be generated based on one or more results of the query.

Abstract: In some example embodiments, a graphical user interface (GUI) is caused to be displayed on a computing device of a user. The GUI can be configured to enable the user to submit an identification of a dataset and at least one configuration parameter. The identification of the data source and the at least one configuration parameter can be received via the GUI on the computing device. A sampling algorithm can be configured based on the at least one configuration parameter. A sample of data from the dataset can be generated using the configured sampling algorithm. The time parameter can limit an execution time of the generating of the sample of data to within a maximum amount of time indicated by the user.

Abstract: Embodiments provide for querying and visualization of query results of graph data. An engine processes graph data to create metadata (e.g., in JSON format) identifying at least different node types and edge types that are present in a graph database. An overview visualization simplifies presentation of graph data by depicting only various different node types and graph types. The overview visualization may form the basis for formulating queries including the metadata, which are then promulgated to the graph database. Returned query results may be visualized as an overview or on a detailed node level, promoting insight and formulation of additional queries including node/edge type metadata. The engine may convert graph data query results into tabular form for consumption by relational database analytical tools. According to particular embodiments, an engine of an in-memory database may be particularly suited to perform graph data visualization, querying, and/or tabular conversion tasks.

Abstract: In some example embodiments, a graphical user interface (GUI) is caused to be displayed on a computing device of a user. The GUI can be configured to enable the user to submit an identification of a dataset and at least one configuration parameter. The identification of the data source, the at least one configuration parameter, and the at least one wrangling parameter can be received via the GUI on the computing device. A sampling algorithm can be configured based on the at least one configuration parameter. A sample of data from the dataset can be generated using the configured sampling algorithm. At least one data wrangling operation can be performed on the sample of data based on the at least one wrangling parameter.

Abstract: Methods, systems, and computer program products for visually representing and displaying data are described. The visual representation may be a data animation. A data query may be submitted, a time measurement for processing the query may be obtained, and a sample size of the query may be adjusted based on the time measurement and a frame refresh rate of a data animation. A data animation may be generated based on one or more results of the query.

Abstract: Methods, systems, and computer program products for visually representing and displaying data are described. The visual representation may be a data animation. A data query may be submitted, a time measurement for processing the query may be obtained, and a sample size of the query may be adjusted based on the time measurement and a frame refresh rate of a data animation. A data animation may be generated based on one or more results of the query.

Abstract: Example embodiments involve a system, computer-readable storage medium storing at least one program, and computer-implemented method for behaviorally consistent data wrangling. A local client device selects a set of raw sample data from a remote datastore. A local execution engine then applies one or more local data wrangling operations to the raw sample data. If the results of the local data wrangling operations are satisfactory, the local data wrangling operations may then be transferred to a remote data wrangling cluster. A remote execution engine being executed by the remote data wrangling cluster then applies the data wrangling operations to the larger set of raw data from which the sample raw data was obtained. As the remote execution engine and the local execution engine are of the same type, the data wrangling behavior exhibited by the local execution engine is reflected in the data wrangling behavior of the remote execution engine.

Abstract: In some example embodiments, a graphical user interface (GUI) is caused to be displayed on a computing device of a user. The GUI can be configured to enable the user to submit an identification of a dataset and at least one configuration parameter. The identification of the data source, the at least one configuration parameter, and the at least one wrangling parameter can be received via the GUI on the computing device. A sampling algorithm can be configured based on the at least one configuration parameter. A sample of data from the dataset can be generated using the configured sampling algorithm. At least one data wrangling operation can be performed on the sample of data based on the at least one wrangling parameter.

Abstract: Embodiments provide an overview visualization of graph data by rendering a graph's structure based upon different node/edge types, rather than upon a total number of nodes and/or edges. These node/edge types are recognized based upon associated metadata. The small number of different node/edge types of a typical graph reduces components for representation in the overview, simplifying that visualization and facilitating user interaction. A user can switch between the graph overview, and a different view affording node-level details. In analysis and/or querying, switching between the overview and the detailed visualization can afford natural and intuitive control over data granularity. For example the overview visualization of graph data may allow a user to initially filter on particular node types, with the subsequent node-level view permitting exploration of finer details while maintaining the overall context of the original graph.

Abstract: Embodiments provide for querying and visualization of query results of graph data. An engine processes graph data to create metadata (e.g., in JSON format) identifying at least different node types and edge types that are present in a graph database. An overview visualization simplifies presentation of graph data by depicting only various different node types and graph types. The overview visualization may form the basis for formulating queries including the metadata, which are then promulgated to the graph database. Returned query results may be visualized as an overview or on a detailed node level, promoting insight and formulation of additional queries including node/edge type metadata. The engine may convert graph data query results into tabular form for consumption by relational database analytical tools. According to particular embodiments, an engine of an in-memory database may be particularly suited to perform graph data visualization, querying, and/or tabular conversion tasks.

Abstract: Example embodiments involve a system, computer-readable storage medium storing at least one program, and computer-implemented method for behaviorally consistent data wrangling. A local client device selects a set of raw sample data from a remote datastore. A local execution engine then applies one or more local data wrangling operations to the raw sample data. If the results of the local data wrangling operations are satisfactory, the local data wrangling operations may then be transferred to a remote data wrangling cluster. A remote execution engine being executed by the remote data wrangling cluster then applies the data wrangling operations to the larger set of raw data from which the sample raw data was obtained. As the remote execution engine and the local execution engine are of the same type, the data wrangling behavior exhibited by the local execution engine is reflected in the data wrangling behavior of the remote execution engine.

Abstract: In some example embodiments, a graphical user interface (GUI) is caused to be displayed on a computing device of a user. The GUI can be configured to enable the user to submit an identification of a dataset and at least one configuration parameter. The identification of the data source, the at least one configuration parameter, and the at least one wrangling parameter can be received via the GUI on the computing device. A sampling algorithm can be configured based on the at least one configuration parameter. A sample of data from the dataset can be generated using the configured sampling algorithm. At least one data wrangling operation can be performed on the sample of data based on the at least one wrangling parameter.

Abstract: Methods, systems, and computer program products for visually representing and displaying data are described. The visual representation may be a data animation. A data query may be submitted, a time measurement for processing the query may be obtained, and a sample size of the query may be adjusted based on the time measurement and a frame refresh rate of a data animation. A data animation may be generated based on one or more results of the query.

Abstract: In an embodiment, a method is provided for tracking a state of a document that is accessible over a computer network. In this method, requests to modify the document are received by way of the computer network. A size of a set of these requests are identified to exceed a threshold size and an identifier that identifies this set of requests is generated. The identifier is then transmitted in a response to the requests by way of the computer network.

Abstract: In an embodiment, a method is provided for tracking a state of a document that is accessible over a computer network. In this method, requests to modify the document are received by way of the computer network. A size of a set of these requests are identified to exceed a threshold size and an identifier that identifies this set of requests is generated. The identifier is then transmitted in a response to the requests by way of the computer network.