Remove support for Kafka v0.8.0 #94
Merged
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
mthssdrbrg
force-pushed
the
remove-kafka-0.8.0
branch
2 times, most recently
from
ebdf6eb
to
c621819
Compare
mthssdrbrg
force-pushed
the
remove-kafka-0.8.0
branch
from
c621819
to
454407b
Compare
mthssdrbrg
force-pushed
the
remove-kafka-0.8.0
branch
from
454407b
to
ff74d3b
Compare
mthssdrbrg
force-pushed
the
remove-kafka-0.8.0
branch
from
ff74d3b
to
1436515
Compare
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The release of Kafka
v0.8.0have a couple of differences from the subsequent releases (archive extension, archive directory structure and Scala version), and I think it'd be good to get rid of the custom code that deals with these.This'll be part of
v1.0.0though, so breaking backward compatibility should be "fine".