out_kafka_rest: Document usage of Message_Key_Field in sending messages to Kafka Rest#1175
out_kafka_rest: Document usage of Message_Key_Field in sending messages to Kafka Rest#1175TechBRSavvy wants to merge 4 commits into
Conversation
…es to Kafka Rest Signed-off-by: TechBRSavvy <techbrsavvy@gmail.com>
|
@esmerel can you please review and check on the conflicts? |
Signed-off-by: Lynette Miles <6818907+esmerel@users.noreply.github.com>
fixed! |
Signed-off-by: Eric D. Schabell <eric@schabell.org>
|
Warning Review limit reached
More reviews will be available in 1 minute and 9 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR documents a new ChangesKafka REST Proxy message_key_field Documentation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@TechBRSavvy fixed the conflicts. |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@pipeline/outputs/kafka-rest-proxy.md`:
- Line 15: The Markdown table row incorrectly merges two parameters into one;
split the combined row into two separate table rows for `message_key_field` and
`partition` so each parameter has its own description and default value. Locate
the merged cell referencing `message_key_field` and `partition` and create one
row: `message_key_field` with its description ("If set, the value of
`message_key_field` in the record indicates the message key. If not set nor
found in the record, `message_key` will be used (if set).") and default
(`_none_`), and a second row: `partition` with its description ("Optional
partition number.") and default (`-1`), ensuring proper pipe-separated Markdown
table syntax and column alignment.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: f0bbf98f-acb6-409b-91fc-b4f7f4892cfd
📒 Files selected for processing (1)
pipeline/outputs/kafka-rest-proxy.md
… layout Applies to fluent#1175 Signed-off-by: Eric D. Schabell <eric@schabell.org>
eschabell
left a comment
There was a problem hiding this comment.
@TechBRSavvy now just waiting on code PR merging.
Documents changes posted fluent/fluent-bit#7813
Summary by CodeRabbit
message_key_fieldconfiguration parameter. Users can specify which record field serves as the message key, with automatic fallback tomessage_keyconfiguration when the specified field is unavailable.