Meet with Aiven at Iceberg Summit 2026!

Apr 8, 2026 - Apr 9, 2026

08:00-17:00 PT

Marriott Marquis, San Francisco, United States

Aiven is thrilled to be sponsoring Iceberg Summit 2026, visit our booth (#B2) to discover how Aiven can help you:

  • Break down the barriers of architecture sprawl - the need to manage separate silos for streaming, relational data, and search - by providing a single, open-source foundation built for the Apache Iceberg ecosystem.
  • Run Kafka, Diskless, and Iceberg topics side-by-side in one cluster: Kafka for sub-100ms with optional Tiered Storage handoff, Diskless for cost-optimized object-store streams, and Iceberg Topics for native tables/SQL with seconds-level freshness— each opt-in per topic, no client API change, and no migrations.
  • Stop service sprawl. Aiven offers your favorite open-source services - Kafka, OpenSearch, PostgreSQL, ClickHouse and more - on one unified platform.
  • Manage your entire data infrastructure easily from a single control plane, giving you more time to innovate.
  • Connect your data services across multiple cloud vendors and regions without the overhead

Book a demo or meeting with our experts

Loading...

AIVEN SESSION

Hear from our experts on Apache Iceberg topics

    • 11:00-11:15, April 8
      Lightning talk

    From Black Box to Breakpoints: Debugging the Kafka Connect Iceberg Connector

    If you ingest Kafka data into Iceberg via Kafka connector, debugging failures can be painful. Connector issues are hard to reproduce when runtime state is split across worker properties, connector configs, and catalog backends. Join us for an IDE‑first workflow: run an embedded Connect worker in‑process, use Testcontainers for Kafka/Schema Registry/object storage, and debug with breakpoints. A multi‑task setup mirrors real Connect behavior and lets you run upstream connector tests against your catalog or FileIO.

    We’ll apply the workflow to two real failures:
    * a config‑provider crash when worker properties are applied twice with Kafka’s config‑provider allowlist enabled;
    * REST catalog responses that diverge from the Iceberg REST spec (error types, auto‑create).
    Both cases are reproducible in the upstream versions we tested.

    You’ll see how to isolate each issue, turn it into targeted integration tests, and leave with a reusable harness and a minimal embedded‑Connect runner pattern. All examples run locally.

    Anatolii Popov