Move offsets logic to the service out of the records storage #5
Conversation
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
mrnakumar
reviewed
Jul 13, 2018
| public CompletionStage<Void> seekTo(long position) { | ||
| return kafkaReceiver | ||
| .doOnConsumer(consumer -> { | ||
| // + 1 because in Kafka "seek" moves the cursor to the desired next record |
There was a problem hiding this comment.
Will it make sense to rename the method to 'seekAfter' instead?
There was a problem hiding this comment.
Well, the public API is "seekTo", just in Kafka they have this "+1" API.
Also, the rest of Liiklus uses "latest acked position" notation instead of "the offset to start reading from"
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.
No description provided.