Skip to main content
How-to guideApplies to: Unified engine deployments
Register a Kafka source, register an Iceberg sink, and create a continuous pipeline through SQL session operations. Execution uses the native streaming path.

Before you start

Complete Streaming setup. You need Kafka, an accessible Iceberg REST catalog and warehouse, configured storage access, and streaming workers. Choose unused source, sink, pipeline, and destination names. Replace the practice names throughout if they already exist.

Define Kafka to Iceberg through HTTP

Send each statement separately in one session. Wait for success before its dependent step. Cleanup is explicit. Replace the placeholders in your client. Keep returned IDs for later requests. Paths below use the native API prefix; adjust it for your deployment.

1. Open a session

From the response, keep session_id from /session_id. Endpoint reference.

2. Register the Kafka source

Endpoint reference.

3. Follow: Register the Kafka source

Repeat this read until /status reaches a terminal state: Succeeded, Failed, Cancelled, OutcomeUnknown, Skipped. Endpoint reference.

4. Register the Iceberg sink

Endpoint reference.

5. Follow: Register the Iceberg sink

Repeat this read until /status reaches a terminal state: Succeeded, Failed, Cancelled, OutcomeUnknown, Skipped. Endpoint reference.

6. Create and start the pipeline

Endpoint reference.

7. Follow: Create and start the pipeline

Repeat this read until /status reaches a terminal state: Succeeded, Failed, Cancelled, OutcomeUnknown, Skipped. Endpoint reference.

8. Read: Create and start the pipeline

Endpoint reference.

9. Inspect the continuous pipeline

Endpoint reference.

10. Follow: Inspect the continuous pipeline

Repeat this read until /status reaches a terminal state: Succeeded, Failed, Cancelled, OutcomeUnknown, Skipped. Endpoint reference.

11. Read: Inspect the continuous pipeline

Endpoint reference.

12. Stop continuous execution

Endpoint reference.

13. Follow: Stop continuous execution

Repeat this read until /status reaches a terminal state: Succeeded, Failed, Cancelled, OutcomeUnknown, Skipped. Endpoint reference.

14. Read: Stop continuous execution

Endpoint reference.

15. Close the session

Endpoint reference.

Configure and send each statement

Enter the Kafka brokers, topic, catalog URL, and warehouse under Example values. The example sends each statement as its own SQL operation in the same session, with a separate operation identity. Wait for each required predecessor to succeed. Creating the pipeline starts continuous execution by default. A successful create operation means the command was accepted; it does not prove that streaming workers reached Running or that the first checkpoint committed.

Inspect and verify

Run the DESCRIBE step and inspect the result column. To repeat that inspection, prepare a new SQL operation with a fresh identity. Reusing the old identity reads the earlier operation rather than issuing a new DESCRIBE. Use the Kafka to Iceberg lesson for sample input records and expected output. Verify the destination after a successful checkpoint. Streaming connector names are separate from the qualified catalog table name used to query Iceberg through Unified.

Stop deliberately

Send the Stop pipeline statement when you are ready to end continuous execution. Follow its reported state. Stopping a docs watch or closing the HTTP session does not stop the pipeline. Keep or remove connector definitions and destination objects through their supported management flows. Stopping the pipeline does not delete its published data.
Last modified on November 4, 2026