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

ReactiveKafkaConsumer Interface and it's Vert.x Implementation #3159

Merged

Conversation

debasishbsws
Copy link
Member

@debasishbsws debasishbsws commented Jun 20, 2023

Progress on #2928

Proposed Changes

  • Identifies all the Consumer functions used and needs to be implemented in specialised modules.
  • Implement all of these methods in the dispatcher vertx module with vertx implementation.

It may require some additional changes while migrating the base dispatcher to use ReactiveKafkaConsumer

@knative-prow
Copy link

knative-prow bot commented Jun 20, 2023

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@knative-prow knative-prow bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. area/data-plane labels Jun 20, 2023
@knative-prow knative-prow bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jun 20, 2023
@codecov
Copy link

codecov bot commented Jun 20, 2023

Codecov Report

Merging #3159 (68efcf0) into main (6abfaa2) will decrease coverage by 0.14%.
The diff coverage is n/a.

❗ Current head 68efcf0 differs from pull request most recent head cfef090. Consider uploading reports for the commit cfef090 to get more accurate results

@@             Coverage Diff              @@
##               main    #3159      +/-   ##
============================================
- Coverage     63.57%   63.43%   -0.14%     
- Complexity      757      758       +1     
============================================
  Files           167      167              
  Lines         11518    11548      +30     
  Branches        233      239       +6     
============================================
+ Hits           7323     7326       +3     
- Misses         3656     3678      +22     
- Partials        539      544       +5     
Flag Coverage Δ
java-unittests 80.22% <ø> (-0.80%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 5 files with indirect coverage changes

@debasishbsws debasishbsws marked this pull request as ready for review June 23, 2023 18:41
@knative-prow knative-prow bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 23, 2023
@debasishbsws
Copy link
Member Author

/ok-to-test

@knative-prow knative-prow bot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Jun 23, 2023
@debasishbsws
Copy link
Member Author

/retest-required

@debasishbsws
Copy link
Member Author

I added commit(...) method that is used in https://github.com/knative-sandbox/eventing-kafka-broker/blob/5a236cb645066be1fbb1d7ccbc95bfeac2b43ccd/data-plane/dispatcher/src/main/java/dev/knative/eventing/kafka/broker/dispatcher/impl/consumer/OffsetManager.java#L163-L165
But in apache kafkaConsumer it does not have commit(...), it has commitSync() and commitAsync()

Which method signature should I use for our Interface?

@pierDipi
Copy link
Member

I added commit(...) method that is used in

https://github.com/knative-sandbox/eventing-kafka-broker/blob/5a236cb645066be1fbb1d7ccbc95bfeac2b43ccd/data-plane/dispatcher/src/main/java/dev/knative/eventing/kafka/broker/dispatcher/impl/consumer/OffsetManager.java#L163-L165

But in apache kafkaConsumer it does not have commit(...), it has commitSync() and commitAsync()
Which method signature should I use for our Interface?

I think the one you have used is good

debasishbsws and others added 2 commits June 26, 2023 14:34
…/broker/dispatcher/ReactiveKafkaConsumer.java

Co-authored-by: Pierangelo Di Pilato <pierangelodipilato@gmail.com>
Copy link
Member

@pierDipi pierDipi left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Jun 26, 2023
@knative-prow
Copy link

knative-prow bot commented Jun 26, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: debasishbsws, pierDipi

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 26, 2023
@knative-prow knative-prow bot merged commit 80d3cf2 into knative-extensions:main Jun 26, 2023
28 of 30 checks passed
@debasishbsws debasishbsws deleted the reactive-vertx-consumer branch June 26, 2023 20:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/data-plane lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants