🔗 SELECT
📄️ ALTER STREAM
You can modify the retention policy for historical store via MODIFY TTL and modify the retention policy for streaming storage via MODIFY SETTING. For mutable streams, you can also run MODIFY SETTING to change the RocksDB settings.
📄️ ALTER VIEW
You can use this SQL to change a view or a materialized view. Today only the settings can be changed. To change the SQL query behinds the view, you have to drop and re-create it.
📄️ CREATE DATABASE
Starting from Timeplus Enterprise 2.6, you can create a database to organize your streams, materialized views and other resources. The database is a logical container to help you to manage and query the data more efficiently.
📄️ CREATE DICTIONARY
Starting from Timeplus Enterprise 2.7, you can create dictionaries to store key-value pairs in memory, with data from various sources, such as files, MySQL/ClickHouse databases, or streams in Timeplus.
📄️ CREATE DISK
By default, Timeplus only created a default disk for local storage.
📄️ CREATE EXTERNAL STREAM
External stream for Kafka is official supported. The external stream for local log files is at technical preview. In Timeplus Enterprise, it also supports another type of External Stream to read/write data for a remote Timeplus Enterprise.
📄️ CREATE EXTERNAL TABLE
Timeplus supports 3 types of external tables: ClickHouse, MySQL, and S3. Reading data from external tables are bounded, which means the query will end when all the data is read. Writing data to external tables are unbounded, which means the query will keep running until you cancel it.
📄️ CREATE FORMAT
Timeplus supports reading or writing messages in Protobuf or Avro format. This document covers how to process data without a Schema Registry. Check this page if your Kafka topics are associated with a Schema Registry.
📄️ CREATE FUNCTION
Timeplus supports four ways to develop/register UDF. Please check UDF page for the overview.
📄️ CREATE MATERIALIZED VIEW
The difference between a materialized view and a regular view is that the materialized view is running in background after creation and the resulting stream is physically written to internal storage (hence it's called materialized).
📄️ CREATE MUTABLE STREAM
Regular streams in Timeplus are immutable, and stored in columnar format. Mutable streams are stored in row format (implemented via RocksDB), and can be updated or deleted. It is only available in Timeplus Enterprise. Please check this page for details.
📄️ CREATE RANDOM STREAM
You may use this special stream to generate random data for tests. For example:
📄️ CREATE REMOTE FUNCTION
At Timeplus, we leverage SQL to make powerful streaming analytics more accessible to a broad range of users. Without SQL, you have to learn and call low-level programming API, then compile/package/deploy them to get analytics results. This is a repetitive and tedious process, even for small changes.
📄️ CREATE STREAM
Stream is a key concept in Timeplus. All data lives in streams, no matter static data or data in motion. We don't recommend you to create or manage TABLE in Timeplus.
📄️ CREATE VIEW
There are two types of views in Timeplus: logical view (or just view ) and materialized view.
📄️ DELETE
Starting from Timeplus Enterprise 2.7, you can delete data from the streams.
📄️ DROP DATABASE
Starting from Timeplus Enterprise 2.6, you can create a database to organize your streams, materialized views and other resources. The database is a logical container to help you to manage and query the data more efficiently.
📄️ DROP DICTIONARY
Starting from Timeplus Enterprise 2.7, you can create dictionaries to store key-value pairs in memory, with data from various sources, such as files, MySQL/ClickHouse databases, or streams in Timeplus.
📄️ DROP EXTERNAL TABLE
Run the following SQL to drop an external table from Timeplus, while keeping the data in external database intact.
📄️ DROP FORMAT SCHEMA
📄️ DROP FUNCTION
No matter UDF or UDAF, you can remove the function via DROP FUNCTION
📄️ DROP STREAM
Run the following SQL to drop a stream or an external stream, with all data in streaming storage and historical storage.
📄️ DROP VIEW
Run the following SQL to drop a view or a materialized view.
📄️ EXPLAIN
The execution of a query in Timeplus is decomposed into many steps. Each step of the query execution can be analyzed and troubleshooted using the corresponding EXPLAIN query. These steps are summarized in the chart below:
📄️ OPTIMIZE
Run the following SQL to initiate an unscheduled merge of a mutable stream or a table with MergeTree engine. This will reorganize the data in the stream and optimize the performance of the stream. Note that we generally recommend against using OPTIMIZE STREAM ... FINAL as its use case is meant for administration, not for daily operations.
📄️ RENAME STREAM
You can rename a stream using the RENAME STREAM statement.
📄️ SHOW CREATE
Show Details For A Stream
📄️ SHOW DATABASES
Starting from Timeplus Enterprise 2.6, you can create a database to organize your streams, materialized views and other resources. The database is a logical container to help you to manage and query the data more efficiently.
📄️ SHOW DICTIONARIES
Starting from Timeplus Enterprise 2.7, you can create dictionaries to store key-value pairs in memory, with data from various sources, such as files, MySQL/ClickHouse databases, or streams in Timeplus.
📄️ SHOW DISKS
Starting from Timeplus Enterprise 2.8, you can create S3 disks for tiered storage or autoscaling materialized views.
📄️ SHOW FORMAT SCHEMAS
List schemas in the current Timeplus deployment:
📄️ SHOW FUNCTIONS
List available User-Defined Functions.
📄️ SHOW STREAMS
List Streams From Current Database
📄️ SYSTEM PAUSE
SYSTEM PAUSE MATERIALIZED VIEW
📄️ SYSTEM RECOVER
This is an advanced feature, for debugging purpose.
📄️ SYSTEM RESUME
SYSTEM RESUME MATERIALIZED VIEW
📄️ SYSTEM TRANSFER LEADER
Transfer the leader of a materialized view to another node in the cluster.
📄️ TRUNCATE STREAM
Run the following SQL to remove the historical data from a stream, keeping the schema and the stream itself.
📄️ USE
Starting from Timeplus Enterprise 2.6, you can create a database to organize Timeplus streams, materialized views, or connect to other systems such as MySQL and Iceberg without creating multiple external tables repeating the connection information.