Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ISRs to kt topics -replicas #53

Merged
merged 3 commits into from
May 3, 2017
Merged

Add ISRs to kt topics -replicas #53

merged 3 commits into from
May 3, 2017

Conversation

pd
Copy link
Contributor

@pd pd commented May 1, 2017

sarama.Client.InSyncReplicas just landed upstream in sarama; I've updated the vendored version, and now include ISRs if replica information was requested from kt topics.

Many thanks for kt, which makes writing tooling around Kafka so much easier than the default Kafka CLI tools. Pretty sure this was my final use case for ever calling kafka-topics.sh. 🎉

pd added 2 commits May 1, 2017 15:13
To get access to the `client.InSyncReplicas` function, added here:

IBM/sarama#872
Copy link
Owner

@fgeller fgeller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pd that looks awesome, thanks! glad kt is of help to you!

just one change request on naming and do you know if sarama is planning a release in the foreseeable future?

topic.go Outdated
@@ -48,6 +48,7 @@ type partition struct {
NewestOffset int64 `json:"newest"`
Leader string `json:"leader,omitempty"`
Replicas []int32 `json:"replicas,omitempty"`
Isrs []int32 `json:"isrs,omitempty"`
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pd
Copy link
Contributor Author

pd commented May 2, 2017

Nah, I know nothing of sarama's release schedule. If you normally wait for a tagged release version before vendoring it here, that makes sense to me, and I'll try to keep an eye on sarama.

@fgeller
Copy link
Owner

fgeller commented May 3, 2017

@pd cheers!

not too concerned about using untagged releases for master, just for the next tagged release for kt. But might just perform a bit more testing for that myself when the time has come - I'm assume you're happy installing kt via go get -u?

thanks again for the contribution!

@fgeller fgeller merged commit a90b67f into fgeller:master May 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants