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
session_id from /session_id.
Endpoint reference.
2. Register the Kafka source
3. Follow: Register the Kafka source
/status reaches a terminal state: Succeeded, Failed, Cancelled, OutcomeUnknown, Skipped.
Endpoint reference.
4. Register the Iceberg sink
5. Follow: Register the Iceberg sink
/status reaches a terminal state: Succeeded, Failed, Cancelled, OutcomeUnknown, Skipped.
Endpoint reference.
6. Create and start the pipeline
7. Follow: Create and start the pipeline
/status reaches a terminal state: Succeeded, Failed, Cancelled, OutcomeUnknown, Skipped.
Endpoint reference.
8. Read: Create and start the pipeline
9. Inspect the continuous pipeline
10. Follow: Inspect the continuous pipeline
/status reaches a terminal state: Succeeded, Failed, Cancelled, OutcomeUnknown, Skipped.
Endpoint reference.
11. Read: Inspect the continuous pipeline
12. Stop continuous execution
13. Follow: Stop continuous execution
/status reaches a terminal state: Succeeded, Failed, Cancelled, OutcomeUnknown, Skipped.
Endpoint reference.
14. Read: Stop continuous execution
15. Close the session
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 theresult 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.