Skip to content

[Blog] realtime profiles blog post#3022

Open
polyzos wants to merge 5 commits intoapache:mainfrom
polyzos:blog-realtime-profiles
Open

[Blog] realtime profiles blog post#3022
polyzos wants to merge 5 commits intoapache:mainfrom
polyzos:blog-realtime-profiles

Conversation

@polyzos
Copy link
Copy Markdown
Contributor

@polyzos polyzos commented Apr 8, 2026

No description provided.

@polyzos polyzos marked this pull request as ready for review April 8, 2026 07:39
@polyzos
Copy link
Copy Markdown
Contributor Author

polyzos commented Apr 8, 2026

@Prajwal-banakar
Copy link
Copy Markdown
Contributor

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
Copy link
Copy Markdown
Contributor Author

polyzos commented Apr 8, 2026

@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
Copy link
Copy Markdown
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants