[Blog] realtime profiles blog post

[polyzos]

No description provided.

[polyzos]

@fresh-borzoni @Prajwal-banakar @platinumhamburg @wuchong PTAL

[Prajwal-banakar]

Hi @polyzos, this is a really strong blog post, the narrative and end-to-end flow work very well.

I have a few small questions and suggestions:

1. On the UDF side, I noticed the blog uses functions like to_bitmap64, bitmap_cardinality, bitmap_or_agg, etc., while the shared flink-roaringbitmap repo (recently released as v0.1.0) follows the rb_ prefix family (rb_build_agg, rb_cardinality, rb_or_agg).
   Just wanted to clarify whether this post is intentionally using a different UDF implementation, or if we should align naming / references to avoid confusion for users.

2. Related to that, it might help to explicitly mention which parts are Fluss-native (e.g., rbm64, aggregation merge engine, auto-increment) and which parts rely on external UDFs, so readers clearly understand the boundary.

3. For the visuals, I noticed one of the images appears slightly cropped and some diagrams have very light text, which makes them a bit hard to read. It might be worth adjusting the export or contrast for better clarity.

Overall, I think this is exactly the right place for the full end-to-end bitmap/deep-dive example and i'm working on simpliyf the quickstart guide

[polyzos]

@Prajwal-banakar Thank you for your comments and for catching the typo.

1. Yes, it's different UDFs, because at the time of writing, the ones on the repo were not available.
2. The UDFs and the concrete guide is under the code repo.. the goal here is more to help users understand what they can build and why this featureset is important.. so those interested can refer to the repo for more context.
3. Without a designer, the visuals are a best effort, but I think they are good enough for the blog post

Looking forward to getting all these directly on Fluss

[Prajwal-banakar]

Hi @polyzos, Thanks for the clarification, that makes sense 😊
Looking forward to getting these capabilities directly into Fluss as well 🚀

[platinumhamburg]

Hi @polyzos, great job! If possible, we could consider unifying everything under the flink-roaringbitmap repository as a baseline for all our future release examples. This would also serve as the standard recommended pattern for Fluss's RoaringBitmap practices in the open-source community, providing users with a more consistent mental model. cc @wuchong

[polyzos]

@platinumhamburg I agree overall; however, I had created all these before creating the repo, and updating everything, making sure it works is a fair amount of work for the blog post.
The functions in the repo will be the standard moving forward as they will be introduced in Fluss directly. However, at this point, changing everything is a bit hard.

We can introduce this formally as a standard when introduced, and keep it as is for now.. For the most part is more about helping users understand what they can do, instead of how to do it. In any case if there are any concerns, I could park this blog post, until i find time to rework on it, although it probably wont be any time soon due to bandwidth.

Any approach works for me. @wuchong WDYT?