Stored Procedures
Stored procedures are function-like interfaces that extend the functionality of the driver beyond simple SELECT/INSERT operations with Apache Kafka.
Stored procedures accept a list of parameters, perform their intended function, and then return any relevant response data from Apache Kafka, along with an indication of whether the procedure succeeded or failed.
CData JDBC Driver for Apache Kafka Stored Procedures
| Name | Description |
| CommitOffset | Commits the current set of message offsets for a specified consumer group. This stored procedure ensures that consumed messages are marked as processed within Kafka, preventing the same records from being read again when the consumer resumes operation. |
| CreateSchema | Creates a schema definition that maps a Kafka topic to a relational table structure. This stored procedure is typically used to establish a structured representation of message data so that the topic can be queried or transformed using SQL-like operations. |
| CreateTopic | Creates a new topic on the Kafka broker. This stored procedure allows you to define key topic parameters (for example, the number of partitions and replication factor) and initialize new message streams for publishing and consumption. |
| DeleteTopic | Deletes an existing topic from the Kafka broker. This stored procedure permanently removes the topic and all of its messages, so it should be used with caution in production environments. |
| GetAdminConsentURL.rsb | Specifies any additional parameters that are required by the authorization request. These parameters are passed directly to the OAuth authorization endpoint. |
| GetOAuthAccessToken | Gets an OAuth authentication token. |
| GetOAuthAuthorizationURL | Gets the authorization URL that must be opened separately by the user to grant access to your application. You will request the OAuthAccessToken from this URL. |
| ProduceMessage | Publishes a raw message to a specified Kafka topic. This stored procedure enables data producers to send serialized message payloads (for example, JSON or Avro) directly into the message stream for downstream consumers to process. |
| RefreshOAuthAccessToken | Exchanges a access token for a new access token. |