David Radley

In this session, we will briefly introduce how the apache software foundation, and Flink in particular, works as an open source community. The Flink community very open and happy about new contributions, so we will share how our community works, the community over code principle, consensus models and our tools. Then, we'll open it up to the audience to ask their questions.

Have you ever wished you could handle problematic events in Flink SQL as easily as with DataStream side outputs? Imagine routing unprocessable records—such as those failing serialization—straight to a dead-letter Kafka queue without stopping your job. The new Apache Flink HTTP connector makes this possible while unlocking even more capabilities. It allows you to treat API endpoints as dynamic Flink tables, enabling seamless integration with any technology that exposes APIs—without writing custom code. For example, you can connect to your favorite AI endpoint simply by declaring a Flink SQL table. In this session, you’ll learn how to leverage the HTTP connector to keep your Flink jobs running even after exceptions, HTTP error codes, or deserialization failures. We’ll explore how its new metadata columns provide powerful tools for error handling and observability. You’ll also discover best practices for tuning the connector for enterprise scenarios, including caching strategies, security configurations, and retry mechanisms. Key Takeaways: • How to integrate APIs into Flink SQL with zero custom code • Techniques for handling errors gracefully and improving resilience • Using…

PyTorch and the Wikimedia Ecosystem - Daniel Mietchen, FIZ Karlsruhe — Leibniz Institute for Information Infrastructure This session will provide a brief tour through the continuously evolving landscape of interactions between the PyTorch and Wikimedia ecosystems. Starting out with a short review...