BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//sf26-agenda//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
BEGIN:VEVENT
UID:SESS-199@sf26-agenda
DTSTAMP:20261020T151709Z
DTSTART:20261105T195000Z
DTEND:20261105T200500Z
SUMMARY:Catching the Wave: PyFlink's missing DataFrame API
LOCATION:Innovation Theater
DESCRIPTION:Zander Matheson\, Tun Shwe\n\nEvery Python data engineer alread
 y knows how to write df.filter(...).group_by(...).agg(...). Give them that
  entry point into Flink and a whole community can build streaming and AI p
 ipelines with the muscle memory they already have\, while the Flink planne
 r\, runtime and checkpointing do the heavy lifting underneath. That's the 
 promise of FLIP-591\, a new pyflink.dataframe module that adds a DataFrame
  API alongside the existing Table and DataStream APIs. In this lightning t
 alk we'll show why it lives as its own dedicated API rather than reshaping
  the Table API\, and why it borrows ergonomics from the modern generation 
 of DataFrame libraries (Polars\, Daft and Ray Data) rather than chasing pa
 ndas parity. Then the streaming twist\, where the DataFrame model is reima
 gined for an infinite source: lazy plans\, changelog-aware iteration that 
 yields RowKind\, and bounded time-boxed previews so a notebook peek actual
 ly terminates. You'll leave knowing where PyFlink is heading and how to he
 lp shape it.
URL:https://sf26.rmoff.net/s/catching-the-wave-pyflinks-missing-dataframe-a
 pi-199
END:VEVENT
END:VCALENDAR
