docs(blog): add post introducing the Flink backend

[deepyaman]

Description of changes

Port https://github.com/claypotai/ibis-flink-example to a quickstart/blog post.

Issues closed

Resolves #7739

[cpcloud]

Some stylistic requests; content-wise this looks good!

[cpcloud]

One small change! After that, I will approve and merge!

[cpcloud]

@deepyaman Can you target against main? The 8.x.x branches changes have been merged into main, since the next release we're targeting is 8.0.0.

[ibis-docs-bot]

Docs preview: https://pr-7912-c8edc68774c23a5d5571d9676c206be078a8936e--ibis-quarto.netlify.app

[chiphuyen]

i'd emphasizing first streaming backend + why this is important

Ibis v8 marks the official release of the first streaming backend for Ibis: the Apache Flink backend. Ibis users can now do data manipulation across both streaming and batch using the same interface. (something like that)

[chiphuyen]

looks like the post is more of an installation guide rather than an introduction post. do you want to keep it like this or want to add more meats like potential use cases and why this is a big deal (like why the world sucks without this feature?)

[deepyaman]

looks like the post is more of an installation guide rather than an introduction post. do you want to keep it like this or want to add more meats like potential use cases and why this is a big deal (like why the world sucks without this feature?)

It was intended mostly as a "quickstart with the Flink backend."

Would anything around potential use cases be Flink-specific? Would it make more sense to include that in the Flink/RisingWave/general Ibis support for streaming announcement, and leave this more as a quickstart?

[chiphuyen]

looks like the post is more of an installation guide rather than an introduction post. do you want to keep it like this or want to add more meats like potential use cases and why this is a big deal (like why the world sucks without this feature?)

It was intended mostly as a "quickstart with the Flink backend."

Would anything around potential use cases be Flink-specific? Would it make more sense to include that in the Flink/RisingWave/general Ibis support for streaming announcement, and leave this more as a quickstart?

i see. maybe rename the title to reflect that this is a quickstart guide?

[deepyaman]

looks like the post is more of an installation guide rather than an introduction post. do you want to keep it like this or want to add more meats like potential use cases and why this is a big deal (like why the world sucks without this feature?)

It was intended mostly as a "quickstart with the Flink backend."

Would anything around potential use cases be Flink-specific? Would it make more sense to include that in the Flink/RisingWave/general Ibis support for streaming announcement, and leave this more as a quickstart?

@chiphuyen @lostmygithubaccount would some of this feedback make more sense to address in #8200? I could imagine, the flow of a reader be:

1. Oh, cool, Ibis v8 includes a bunch of new features, including streaming support (Cody's post)
2. I want to try one of them, the Flink backend (this post)

[lostmygithubaccount]

I have some of the language in here: #8200

but would be worth having streaming expert expand on that either there or a separate post

[chiphuyen]

I have some of the language in here: #8200

but would be worth having streaming expert expand on that either there or a separate post

oh i see. cody is ahead of our time

[ibis-docs-bot]

Docs preview: https://pr-7912-fb6c6e0ae0f1319eb8a72b73099f14d1f30213bb--ibis-quarto.netlify.app

[lostmygithubaccount]

a few comments -- @deepyaman can you address these soon and update the execution file? and ideally remove the old one if you are changing the directory path?

[lostmygithubaccount]

thanks!

old