Thank you 😅

Boooooo for hosting this in the middle of summer PTO. Now I can’t join

Yeah I can see it being useful when you’ve implemented your own operator, but I also see users making assumptions how some of the built-in operators work and try to change/fix things where they don’t know exactly what they’re doing

The main challenge is always that savepoint and checkpoints can also contain data that hasn’t been emitted to the sink yet. You’re basically looking at committed and uncommitted data from internal state. Is that really interesting for users? Or just the committed part?

I read this more as changes to what would be the equivalent of the State Processor API in Flink?

Now you can teach me how to make all the memes 🥰😍

I would recommend to check out Restate restate.dev

I think I just saw a notification today in the community on someone porting the existing one to the target interfaces…

Of course. BlacKkklansman was amazing

👋

We will miss you ❤️

If they push it into Calcite, it might

Product Management at Confluent, Flink PMC/committer. Working on streaming data, Flink/Kafka/Iceberg etc

There are thousands of them here in the fall, it’s a super common thing as a Dutch person but so pretty when you actually take a moment to appreciate them

It’s always a trade-off. From my experience, the larger the organization is, the more prefer they prefer to have it under a neutral body so they never have to worry about it.

There are a couple of people working adding it to open source. Same for JSON_SR. Did you consider contributing it back?

I guess that’s why everyone is now on the VARIANT data type hype 😏