Skip to content

Commit

Permalink
Add paragraph about feature toggle
Browse files Browse the repository at this point in the history
  • Loading branch information
lhotari committed Oct 2, 2024
1 parent 61df62c commit 370f376
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions pip/pip-379.md
Original file line number Diff line number Diff line change
Expand Up @@ -377,6 +377,8 @@ For improved observability, a separate REST API for listing all pending messages

The "draining hashes" feature doesn't introduce backward or forward compatibility issues. The state is handled at runtime, and the changes are on the broker side without changes to the client protocol.
Slightly unrelated to PIP-379 changes, there's a need to ensure that users upgrading from Pulsar 3.x can revert to the "recently joined consumers" logic (before PIP-282) in case of possible regressions caused by PIP-379. Since PIP-282 is also new in Pulsar 4.0.0, there needs to be a feature flag that toggles between the PIP-379 implementation for Key_Shared and the "recently joined consumers" logic before PIP-282. Implemention details for this feature toggle can be handled in the pull request for implementing this.

## Links

- Mailing List discussion thread: https://lists.apache.org/thread/l5zjq0fb2dscys3rsn6kfl7505tbndlx
Expand Down

0 comments on commit 370f376

Please # to comment.