create_table_monitor
- create_table_monitor(
table_name: string,
options?: Record<string, string>,
callback?: GPUdbCallback,
): Promise<CreateTableMonitorResponse>Parameters
- table_name: string
Name of the table to monitor, in [schema_name.]table_name format, using standard name resolution rules.
Optionaloptions: Record<string, string>Optional parameters.
Optionalcallback: GPUdbCallbackOptional callback function
Returns Promise<CreateTableMonitorResponse>
Promise<Types.CreateTableMonitorResponse> - Promise resolving to the response
- Defined in src/GPUdb.ts:6846
- table_name: string
create_table_monitor_request
- create_table_monitor_request(
request: CreateTableMonitorRequest,
callback?: GPUdbCallback,
): Promise<CreateTableMonitorResponse>Creates a monitor that watches for a single table modification event type (insert, update, or delete) on a particular table (identified by
table_name) and forwards event notifications to subscribers via ZMQ. After this call completes, subscribe to the returnedtopic_idon 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 usingtype_schema. The monitor will continue to run (regardless of whether or not there are any subscribers) until deactivated withclear_table_monitor.For more information on table monitors, see Table Monitors.
Parameters
- request: CreateTableMonitorRequest
Request object containing the parameters for the operation
Optionalcallback: GPUdbCallbackOptional callback function
Returns Promise<CreateTableMonitorResponse>
Promise<Types.CreateTableMonitorResponse> - Promise resolving to the response
- Defined in src/GPUdb.ts:6811
- request: CreateTableMonitorRequest
Creates a monitor that watches for a single table modification event type (insert, update, or delete) on a particular table (identified by
table_name) and forwards event notifications to subscribers via ZMQ. After this call completes, subscribe to the returnedtopic_idon 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 usingtype_schema. The monitor will continue to run (regardless of whether or not there are any subscribers) until deactivated withclear_table_monitor.For more information on table monitors, see Table Monitors.