Skip to content

docs: pipeline: outputs: kafka: document schema registry support - #2640

Open
eschabell wants to merge 1 commit into
fluent:masterfrom
eschabell:erics_kafka_reg_options_updates
Open

docs: pipeline: outputs: kafka: document schema registry support#2640
eschabell wants to merge 1 commit into
fluent:masterfrom
eschabell:erics_kafka_reg_options_updates

Conversation

@eschabell

Copy link
Copy Markdown
Collaborator

Document the schema_registry_* parameters for resolving Avro schemas from a Confluent Schema Registry, including subject and ID based resolution, basic and bearer authentication, multiple registry endpoints with failover, and the accepted dotted key spellings.

Note, covers code merges without corresponding docs PR.

Document the schema_registry_* parameters for resolving Avro schemas
from a Confluent Schema Registry, including subject and ID based
resolution, basic and bearer authentication, multiple registry
endpoints with failover, and the accepted dotted key spellings.

Note, covers code merges without corresponding docs PR.

Signed-off-by: Eric D. Schabell <eric@schabell.org>
@eschabell eschabell self-assigned this Aug 1, 2026
@eschabell eschabell added the waiting-on-review Waiting on a review from mainteners label Aug 1, 2026
@eschabell
eschabell requested a review from a team as a code owner August 1, 2026 09:00
@eschabell eschabell added the 5.0.9 label Aug 1, 2026
@coderabbitai

coderabbitai Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@eschabell, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 24 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 82c96689-3794-4208-9683-90a1ca0fe927

📥 Commits

Reviewing files that changed from the base of the PR and between 0eb06a6 and 92da829.

📒 Files selected for processing (1)
  • pipeline/outputs/kafka.md

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@eschabell

Copy link
Copy Markdown
Collaborator Author

@patrick-stephens ready for review!

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

Labels

5.0.9 waiting-on-review Waiting on a review from mainteners

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant