forked from apache/pulsar
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Feature] Introduce continuous offset for pulsar (apache#9039)
Fixes apache#9038 ### Motivation As described in [PIP-70](https://github.com/apache/pulsar/wiki/PIP-70%3A-Introduce-lightweight-broker-entry-metadata). One of the use case for Broker entry metadata is providing continuous message sequence-Id for messages in one topic-partition which is useful for Protocol Hanlder like KOP. This PR enable Pulsar to support continuous offset for message based on Broker entry metadata. ### Modifications Introduce a new field for broker entry metadta named `offset`; Introduce a new interceptor type `ManagedLedgerInterceptor` which intercept entry in `ManagedLedger`; Each partition will be assigned a `ManagedLedgerInterceptor` when `ManagedLedger` created; Each Entry will be intercept for adding a monotone increasing offset in Broker entry metadata and the offet is added by batchSize of entry; Support find position by a given offset.
- Loading branch information
1 parent
11b9359
commit d85a5e2
Showing
21 changed files
with
897 additions
and
37 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.