[websocket] Query parameter "negativeAckRedeliveryDelay" should be effective even if DLQ is disabled#11495
Merged
Merged
Conversation
… if DLQ is disabled
codelipenghui
approved these changes
Jul 29, 2021
Anonymitaet
approved these changes
Jul 30, 2021
Anonymitaet
reviewed
Jul 30, 2021
Anonymitaet
left a comment
Member
There was a problem hiding this comment.
Thanks for your contribution. I’ve left some comments, PTAL.
Co-authored-by: Anonymitaet <50226895+Anonymitaet@users.noreply.github.com>
Contributor
Author
|
@Anonymitaet Addressed your comment. PTAL |
Anonymitaet
approved these changes
Aug 3, 2021
Anonymitaet
left a comment
Member
There was a problem hiding this comment.
Thanks for your contribution. Approved from the language perspective.
sijie
approved these changes
Aug 4, 2021
codelipenghui
pushed a commit
that referenced
this pull request
Aug 4, 2021
…fective even if DLQ is disabled (#11495) ### Motivation On the consumer endpoint of WebSocket API, we can specify the delay time before a message which is negatively acknowledged is redelivered using the query parameter `negativeAckRedeliveryDelay`. However, this parameter is currently ignored when DLQ is disabled. I think this is an implementation mistake. Users should be able to specify `negativeAckRedeliveryDelay` even if DLQ is disabled. https://github.com/apache/pulsar/blob/ee202d06548e3c73d70ad52374658ee3507ca809/pulsar-websocket/src/main/java/org/apache/pulsar/websocket/ConsumerHandler.java#L389-L403 Related PR: #8249 ### Modifications Fixed `ConsumerHandler` of WebSocket to use the `negativeAckRedeliveryDelay` value specified by the client even if DLQ is disabled. In addition, fixed an inappropriate test code (`ProxyPublishConsumeTest#nackMessageTest()`). (cherry picked from commit 1f76d0d)
LeBW
pushed a commit
to LeBW/pulsar
that referenced
this pull request
Aug 9, 2021
…fective even if DLQ is disabled (apache#11495) ### Motivation On the consumer endpoint of WebSocket API, we can specify the delay time before a message which is negatively acknowledged is redelivered using the query parameter `negativeAckRedeliveryDelay`. However, this parameter is currently ignored when DLQ is disabled. I think this is an implementation mistake. Users should be able to specify `negativeAckRedeliveryDelay` even if DLQ is disabled. https://github.com/apache/pulsar/blob/ee202d06548e3c73d70ad52374658ee3507ca809/pulsar-websocket/src/main/java/org/apache/pulsar/websocket/ConsumerHandler.java#L389-L403 Related PR: apache#8249 ### Modifications Fixed `ConsumerHandler` of WebSocket to use the `negativeAckRedeliveryDelay` value specified by the client even if DLQ is disabled. In addition, fixed an inappropriate test code (`ProxyPublishConsumeTest#nackMessageTest()`).
bharanic-dev
pushed a commit
to bharanic-dev/pulsar
that referenced
this pull request
Mar 18, 2022
…fective even if DLQ is disabled (apache#11495) ### Motivation On the consumer endpoint of WebSocket API, we can specify the delay time before a message which is negatively acknowledged is redelivered using the query parameter `negativeAckRedeliveryDelay`. However, this parameter is currently ignored when DLQ is disabled. I think this is an implementation mistake. Users should be able to specify `negativeAckRedeliveryDelay` even if DLQ is disabled. https://github.com/apache/pulsar/blob/ee202d06548e3c73d70ad52374658ee3507ca809/pulsar-websocket/src/main/java/org/apache/pulsar/websocket/ConsumerHandler.java#L389-L403 Related PR: apache#8249 ### Modifications Fixed `ConsumerHandler` of WebSocket to use the `negativeAckRedeliveryDelay` value specified by the client even if DLQ is disabled. In addition, fixed an inappropriate test code (`ProxyPublishConsumeTest#nackMessageTest()`).
momo-jun
added a commit
to momo-jun/pulsar
that referenced
this pull request
Aug 5, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
On the consumer endpoint of WebSocket API, we can specify the delay time before a message which is negatively acknowledged is redelivered using the query parameter
negativeAckRedeliveryDelay.However, this parameter is currently ignored when DLQ is disabled. I think this is an implementation mistake. Users should be able to specify
negativeAckRedeliveryDelayeven if DLQ is disabled.pulsar/pulsar-websocket/src/main/java/org/apache/pulsar/websocket/ConsumerHandler.java
Lines 389 to 403 in ee202d0
Related PR: #8249
Modifications
Fixed
ConsumerHandlerof WebSocket to use thenegativeAckRedeliveryDelayvalue specified by the client even if DLQ is disabled. In addition, fixed an inappropriate test code (ProxyPublishConsumeTest#nackMessageTest()).Verifying this change
Does this pull request potentially affect one of the following parts: