A data table with an attached aggregation preprocessor that computes and maintains aggregations from another LiveView table that serves as a data source.

Author-time aggregation is configured in a LiveView configuration file that defines a LiveView data table with an aggregation data source. Author-time aggregations run on the LiveView Server and cannot be changed once the server has started.

An application that takes data that is not in the LiveView Server and publishes it in an existing LiveView table.

A technique for reducing the rate at which data is coming into a table. Conflation is done by periodic publication, publishing at most one update per second per key for example, with repeated updates on the same key folded together (conflated) such that clients get the result of multiple deltas as a single delta.

You configure a table to use conflation with the publish-interval-millis attribute of the aggregate table's <data-table> tag. For example, setting publish-interval-millis="250" means that data will be published in the target table row every 250 milliseconds.

To control whether the aggregated data is conflated, set the conflate-data attribute of the <aggregation> tag under the data-source in the target (aggregation) table. By default, this attribute is set to false, which means that the periodic publish will include all row updates. If you set this attribute to true, only the most recent update will be published.

A query that first executes a snapshot query, and then continues to return results as records that satisfy the query are created, updated, or deleted in the target table. A continuous query provides to a client a continuously updating view of the data that satisfies the query.

The Continuous Query Processor manages your data. LiveView Server executes the Continuous Query Processor in the default container of the host StreamBase® Server.

A LiveView Table is populated from a data source. A data source must be one of three types:

Dynamic aggregation uses ad hoc aggregate functions expressed in a query sent to a LiveView Server instance over a client connection. Client connections include those made by lv-client, and any custom querying utility or function you have made using the LiveView Client API.

A join of two tables, a local table and a foreign table, whereby join processing occurs when a row in the either the local or the foreign table is inserted or updated. As in a half-active join, when a row in the local table is inserted or updated, a lookup of a row in the foreign table is performed based on the join keys, and the lookup results update the data in the local row. Additionally, when a row in the foreign table is inserted or updated, all rows in the local table that match the join keys are updated.

A join of two tables, a local table and a foreign table, whereby when a row in the local table is inserted or updated, a lookup of a row in the foreign table is performed based on the join keys, and the lookup results update the data in the local row.

The layer in the logical architecture that connects directly to clients.

XML files that:

When LiveView Server starts, all configuration files in the same folder where LiveView is launched are validated against a schema for semantic correctness. LiveView configuration files have file extension .lvconf and are often called lvconf files (pronounced ell-vee-conf).

The layer in the logical architecture where data is stored. Data is stored in continuous query processors.

Consists of one or more definitions of LiveView tables that are to contain live, streaming data presented by a LiveView server. LiveView clients connect to the server to run queries against its tables, and to show visualizations of the results.

A pair of LiveView Servers with identical configuration and data used as backups for one another, to provide high availability (HA).

A library for Java programs to access LiveView, available on the file system at %STREAMBASE_HOME%\liveview\lib, and through StreamBase Studio as a library for Java and Studio projects.

A library for .NET programs to access LiveView Server. The LiveView .NET Client Library and API uses the Microsoft Reactive Extensions (Rx) library. It is available on the file system at %STREAMBASE_HOME%\liveview\sdk\bin, and through StreamBase Studio as a library for .NET and Studio projects.

A StreamBase Studio project that contains LiveView configuration files at its root, along with any other files needed to start LiveView Server.

A single instance of LiveView software that ingests data, runs the Continuous Query Processor, and provides services for clients.

The layer in the logical architecture where services (such as alerts) occur.

A LiveView table (sometimes called an Active Table) is data table with a particular schema that accepts a stream of incoming data and queries.

An abbreviation for LiveView Configuration file.

A StreamBase® application that processes all data flowing into a LiveView table. Processors can be custom or built in LiveView. They may fetch data themselves using input adapters, or they may receive data from other tables.

A join of two data feeds with the same primary key, such that each row contains all fields for a given primary key value.

An application that publishes data into a LiveView table.

A StreamBase® application that runs in the default container and forms the basis for LiveView Server.

The number of parallel threads used to scan a table during the snapshot portion of a query.

A query that executes once and returns a single result set, containing all records from the target table that satisfy the query at the time of execution.

Static aggregation was provided in LiveView releases before 2.0 as another version of aggregation defined in lvconf files for running on LiveView Server. Static aggregation is still supported by LiveView 2.x servers, but this feature is now deprecated in favor of Author-Time Aggregation, and will be removed in a future release.

A StreamBase® application that acts on a data source and feeds into a LiveView table.