Load Confluent Schema Registry data in Python using dltHub

Build a Confluent Schema Registry-to-database or-dataframe pipeline in Python using dlt with automatic Cursor support.

In this guide, we'll set up a complete Confluent Cloud data pipeline from API credentials to your first data load in just 10 minutes. You'll end up with a fully declarative Python pipeline based on dlt's REST API connector, like in the partial example code below:

Example code
@dlt.source
def confluent_cloud_migration_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "http://localhost:8087/",
            "auth": {
                "type": "bearer",
                "token": access_token,
            },
        },
        "resources": [
            top,,errors,,latest
            ],
    }
    [...]
    yield from rest_api_resources(config)


def get_data() -> None:
    # Connect to destination
    pipeline = dlt.pipeline(
        pipeline_name='confluent_cloud_migration_pipeline',
        destination='duckdb',
        dataset_name='confluent_cloud_migration_data', 
    )
    # Load the data
    load_info = pipeline.run(confluent_cloud_migration_source())
    print(load_info)

Why use dltHub Workspace with LLM Context to generate Python pipelines?

  • Accelerate pipeline development with AI-native context
  • Debug pipelines, validate schemas and data with the integrated Pipeline Dashboard
  • Build Python notebooks for end users of your data
  • Low maintenance thanks to Schema evolution with type inference, resilience and self documenting REST API connectors. A shallow learning curve makes the pipeline easy to extend by any team member
  • dlt is the tool of choice for Pythonic Iceberg Lakehouses, bringing mature data loading to pythonic Iceberg with or without catalogs

What you’ll do

We’ll show you how to generate a readable and easily maintainable Python script that fetches data from confluent_cloud_migration’s API and loads it into Iceberg, DataFrames, files, or a database of your choice. Here are some of the endpoints you can load:

  • Top: Contains information about the most recent events.
  • Errors: Provides details on error messages.
  • Latest: Fetches the latest updates in the system.
  • Streams: Manages and monitors data streams.
  • Schemas: Handles schema definitions and versions.
  • Categories: Organizes various topics related to the service.
  • Replication: Deals with data replication settings.
  • Kafka Connectors: Manages connectors for Kafka integrations.

You will then debug the Confluent Cloud pipeline using our Pipeline Dashboard tool to ensure it is copying the data correctly, before building a Notebook to explore your data and build reports.

Setup & steps to follow

💡
Before getting started, let's make sure Cursor is set up correctly:

Now you're ready to get started!

  1. ⚙️ Set up dlt Workspace

    Install dlt with duckdb support:

    pip install dlt[workspace]

    Initialize a dlt pipeline with Confluent Cloud support.

    dlt init dlthub:confluent_cloud_migration duckdb

    The init command will setup the necessary files and folders for the next step.

  2. 🤠 Start LLM-assisted coding

    Here’s a prompt to get you started:

    Prompt
    Please generate a REST API Source for Confluent Cloud API, as specified in @confluent_cloud_migration-docs.yaml 
Start with endpoints top and  and skip incremental loading for now. 
Place the code in confluent_cloud_migration_pipeline.py and name the pipeline confluent_cloud_migration_pipeline. 
If the file exists, use it as a starting point. 
Do not add or modify any other files. 
Use @dlt rest api as a tutorial. 
After adding the endpoints, allow the user to run the pipeline with python confluent_cloud_migration_pipeline.py and await further instructions.

  3. 🔒 Set up credentials

    The authentication method employs OAuth2 with a refresh token, which necessitates the setup of a connected app in the API for seamless operation.

    To get the appropriate API keys, please visit the original source at https://www.confluent.io/. If you want to protect your environment secrets in a production environment, look into setting up credentials with dlt.

  4. 🏃‍♀️ Run the pipeline in the Python terminal in Cursor

    python confluent_cloud_migration_pipeline.py

    If your pipeline runs correctly, you’ll see something like the following:

    Pipeline confluent_cloud_migration load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset confluent_cloud_migration_data
The duckdb destination used duckdb:/confluent_cloud_migration.duckdb location to store data
Load package 1749667187.541553 is LOADED and contains no failed jobs

  5. 📈 Debug your pipeline and data with the Pipeline Dashboard

    Now that you have a running pipeline, you need to make sure it’s correct, so you do not introduce silent failures like misconfigured pagination or incremental loading errors. By launching the dlt Workspace Pipeline Dashboard, you can see various information about the pipeline to enable you to test it. Here you can see:

    • Pipeline overview: State, load metrics
    • Data’s schema: tables, columns, types, hints
    • You can query the data itself
    dlt pipeline confluent_cloud_migration_pipeline show --dashboard

  6. 🐍 Build a Notebook with data explorations and reports

    With the pipeline and data partially validated, you can continue with custom data explorations and reports. To get started, paste the snippet below into a new marimo Notebook and ask your LLM to go from there. Jupyter Notebooks and regular Python scripts are supported as well.

    import dlt

data = dlt.pipeline("confluent_cloud_migration_pipeline").dataset()
# get o table as Pandas frame
data.o.df().head()

Running into errors?

Users should be aware that the service may return 422 errors if complex type references are not provided. Additionally, operations could be throttled if the request limit is exceeded, leading to potential delays in response. It's also crucial to handle null values correctly in deeply nested fields, as these may cause unexpected behavior in the application.

Extra resources:

Next steps