Creates a monitor that watches for a single table modification event type
(insert, update, or delete) on a particular table (identified by input
parameter table_name) and forwards event notifications to subscribers via
ZMQ. After this call completes, subscribe to the returned output parameter
topic_id on the ZMQ table monitor port (default 9002). Each time an operation
of the given type on the table completes, a multipart message is published for
that topic; the first part contains only the topic ID, and each subsequent part
contains one binary-encoded Avro object that corresponds to the event and can
be decoded using output parameter type_schema. The monitor will continue to
run (regardless of whether or not there are any subscribers) until deactivated
with /clear/tablemonitor.For more information on table monitors, see
Table Monitors.
Input Parameter Description
string
Name of the table to monitor, in [schema_name.]table_name format, using standard name resolution rules.
map of string to strings
Optional parameters.The default value is an empty map ( {} ).
Show options
Type of modification event on the target table to be monitored by this table monitor.The default value is insert.
insert: Get notifications of new record insertions. The new row images are forwarded to the subscribers.
update: Get notifications of update operations. The modified row count information is forwarded to the subscribers.
delete: Get notifications of delete operations. The deleted row count information is forwarded to the subscribers.
ID to use for this monitor instead of a randomly generated one.
Name of an existing data sink to send change data notifications to.
Maximum number of consecutive failed notification attempts before suspending the stream. A value of -1 (default) disables auto-suspend. This value is by rank and not overall.
Name of a table to which failed stream notifications are written when the stream is suspended. The database will attempt to send notifications persisted in this table when the stream is resumed. The table has the following columns: rank (long), job_id (long), uuid (uuid), timestamp (timestamp), error_msg (string), payload (bytes). Leave this option empty to disable persisting failed notification events.
Destination for the output data in format ‘destination_type://path[:port]’. Supported destination types are ‘http’, ‘https’ and ‘kafka’.
Name of the Kafka topic to publish to if destination in input parameter options is specified and is a Kafka broker.
Column on subscribed table that will increase for new records (e.g., TIMESTAMP).
Filter expression to limit records for notification.
A comma-separated list of tables (optionally with aliases) to include in the join. The monitored table input parameter table_name must be included, representing only the newly inserted rows (deltas) since the last notification. Other tables can be any existing tables or views. Aliases can be used with the ‘table_name as alias’ syntax.
A comma-separated list of columns or expressions to include from the joined tables. Column references can use table names or aliases defined in ‘join_table_names’. Each column can optionally be aliased using ‘as’. The selected columns will also appear in the notification output.
Filter or join expressions to apply when combining the tables. Expressions are standard SQL-style conditions and can reference any table or alias listed in ‘join_table_names’. This corresponds to the WHERE clause of the underlying join, and can include conditions to filter the delta rows.
Method controlling when the table monitor reports changes to the input parameter table_name.The default value is on_change.
on_change: Report changes as they occur.
periodic: Report changes periodically at rate specified by refresh_period.
When refresh_method is periodic, specifies the period in seconds at which changes are reported.
When refresh_method is periodic, specifies the first time at which changes are reported. Value is a datetime string with format ‘YYYY-MM-DD HH:MM:SS’.
Output Parameter Description
The Kinetica server embeds the endpoint response inside a standard response structure which contains status information and the actual response to the query. Here is a description of the various fields of the wrapper:
String
‘OK’ or ‘ERROR’
String
Empty if success or an error message
String
‘create_table_monitor_response’ or ‘none’ in case of an error
String
Empty string
JSON or String
This embedded JSON represents the result of the /create/tablemonitor endpoint:
Show data_str
string
The ZMQ topic ID to subscribe to for table events.
string
Value of input parameter table_name.
string
JSON Avro schema of the table, for use in decoding published records.
map of string to strings
Additional information.The default value is an empty map ( {} ).
Show info
For insert_table/delete_table events, the ttl of the table.
The topic id for ‘insert’ event in input parameter options.
The topic id for ‘update’ event in input parameter options.
The topic id for ‘delete’ event in input parameter options.
The JSON Avro schema of the table in output parameter table_name.
The JSON Avro schema for ‘update’ events.
The JSON Avro schema for ‘delete’ events.
Empty string in case of an error.
Assistant
Responses are generated using AI and may contain mistakes.