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

Set KafkaChannel delivery order to ordered by default #1438

Conversation

pierDipi
Copy link
Member

@pierDipi pierDipi commented Nov 9, 2021

The existing channel uses ordered delivery and I think we should
keep it ordered by default for the new channel for backward
compatibility and seamless upgrade.

Proposed Changes

  • Set KafkaChannel delivery order to ordered by default

Release Note

None

Docs

None

The existing channel uses ordered delivery and I think we should
keep it ordered by default for the new channel for backward
compatibility and seamless upgrade.

Signed-off-by: Pierangelo Di Pilato <pdipilat@redhat.com>
@pierDipi pierDipi requested a review from aliok November 9, 2021 07:49
@google-cla google-cla bot added the cla: yes Indicates the PR's author has signed the CLA. label Nov 9, 2021
@knative-prow-robot knative-prow-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. area/control-plane labels Nov 9, 2021
@codecov
Copy link

codecov bot commented Nov 9, 2021

Codecov Report

Merging #1438 (39496b1) into main (fb707d4) will decrease coverage by 0.06%.
The diff coverage is 0.00%.

Impacted file tree graph

@@             Coverage Diff              @@
##               main    #1438      +/-   ##
============================================
- Coverage     73.41%   73.34%   -0.07%     
  Complexity      575      575              
============================================
  Files           100      100              
  Lines          3942     3943       +1     
  Branches        160      160              
============================================
- Hits           2894     2892       -2     
- Misses          808      811       +3     
  Partials        240      240              
Flag Coverage Δ
java-unittests 82.16% <ø> (ø)

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

Impacted Files Coverage Δ
control-plane/pkg/reconciler/channel/channel.go 29.96% <0.00%> (-0.12%) ⬇️
control-plane/pkg/prober/cache.go 94.28% <0.00%> (-5.72%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fb707d4...39496b1. Read the comment docs.

@@ -447,6 +448,7 @@ func (r *Reconciler) getSubscriberConfig(ctx context.Context, channel *messaging
egress := &contract.Egress{
Destination: subscriber.SubscriberURI.String(),
ConsumerGroup: consumerGroup(channel, subscriber),
DeliveryOrder: contract.DeliveryOrder_ORDERED,
Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Member Author

Choose a reason for hiding this comment

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

I'm not following what do you mean here.

Copy link
Member

Choose a reason for hiding this comment

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

I also am not sure about the behaviour of delivery order in KafkaChannel implementations.

Copy link
Contributor

Choose a reason for hiding this comment

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

is the eventing-kafka unordered ?

Copy link
Member Author

Choose a reason for hiding this comment

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

eventing-kafka is ordered (only)

@knative-prow-robot knative-prow-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Nov 10, 2021
@pierDipi pierDipi requested a review from matzew November 11, 2021 08:09
Copy link
Contributor

@matzew matzew 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-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Nov 11, 2021
@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: matzew, 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-robot knative-prow-robot merged commit aef1869 into knative-extensions:main Nov 11, 2021
@pierDipi pierDipi deleted the SRVKE-1026_KafkaChannel-default-delivery-order branch November 12, 2021 13:31
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/control-plane cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants