Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kafka: move processing loop into connect context #8135

Merged
merged 3 commits into from
Jan 10, 2023

Conversation

dotnwat
Copy link
Member

@dotnwat dotnwat commented Jan 10, 2023

The processing loop for a kafka connection was implemented at the server
level despite being part of the processing pipeline for a connection.
This commit moves that loop into the connection context itself.

Backports Required

  • none - not a bug fix
  • none - issue does not exist in previous branches
  • none - papercut/not impactful enough to backport
  • v22.3.x
  • v22.2.x
  • v22.1.x

UX Changes

Release Notes

  • none

The processing loop for a kafka connection was implemented at the server
level despite being part of the processing pipeline for a connection.
This commit moves that loop into the connection context itself.

Signed-off-by: Noah Watkins <[email protected]>
Signed-off-by: Noah Watkins <[email protected]>
graphcareful
graphcareful previously approved these changes Jan 10, 2023
@@ -213,10 +213,10 @@ ss::future<> server::apply(ss::lw_shared_ptr<net::connection> conn) {
mtls_state,
config::shard_local_cfg().kafka_request_max_bytes.bind());

co_return co_await ss::do_until(
[ctx] { return ctx->is_finished_parsing(); },
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: is_finished_parsing() can be private now

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed can ya reapprove?

@dotnwat dotnwat merged commit 5ffa022 into redpanda-data:dev Jan 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants