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

Upgrade sarama dependency to support Kafka 0.11.0 #297

Merged
merged 2 commits into from
Dec 4, 2017
Merged

Upgrade sarama dependency to support Kafka 0.11.0 #297

merged 2 commits into from
Dec 4, 2017

Conversation

kpocius
Copy link
Contributor

@kpocius kpocius commented Dec 4, 2017

Burrow 0.1.1 was working just fine with Kafka 0.11.0.1, but due to the introduction of a new helper in the latest version, it now fails to start with the following error:

{"level":"panic","ts":1512380881.6406214,"msg":"Unknown Kafka Version: 0.11.0"}

Now I could probably work around it by simply specifying a lower version of Kafka than I'm actually using, but we might as well do it properly, right?

I checked sarama changes and it doesn't look like it would break anything in Burrow.

@kpocius kpocius changed the title Upgrade sarama dependency to support Kafka 0.11.0 & 1.0.0 Upgrade sarama dependency to support Kafka 0.11.0 Dec 4, 2017
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.04%) to 74.216% when pulling 362b478 on kpocius:master into d088c99 on linkedin:master.

2 similar comments
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.04%) to 74.216% when pulling 362b478 on kpocius:master into d088c99 on linkedin:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.04%) to 74.216% when pulling 362b478 on kpocius:master into d088c99 on linkedin:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.04%) to 74.216% when pulling 5ae98db on kpocius:master into d088c99 on linkedin:master.

1 similar comment
@coveralls
Copy link

coveralls commented Dec 4, 2017

Coverage Status

Coverage decreased (-0.04%) to 74.216% when pulling 5ae98db on kpocius:master into d088c99 on linkedin:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.04%) to 74.216% when pulling 5ae98db on kpocius:master into d088c99 on linkedin:master.

2 similar comments
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.04%) to 74.216% when pulling 5ae98db on kpocius:master into d088c99 on linkedin:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.04%) to 74.216% when pulling 5ae98db on kpocius:master into d088c99 on linkedin:master.

Gopkg.lock Outdated
revision = "bbdbe644099b7fdc8327d5cc69c030945188b2e9"
version = "v1.13.0"
revision = "240fd146ce68bcafb034cc5dc977229ffbafa8ea"
version = "v1.14.0"
Copy link
Contributor

Choose a reason for hiding this comment

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

You should not be editing the Gopkg.lock file. Changes like this have to go into the Gopkg.toml file.

@coveralls
Copy link

coveralls commented Dec 4, 2017

Coverage Status

Coverage decreased (-0.04%) to 74.216% when pulling f4f35f2 on kpocius:master into 8993eb7 on linkedin:master.

@toddpalino toddpalino merged commit 3a4372f into linkedin:master Dec 4, 2017
@bai bai mentioned this pull request May 30, 2018
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.

3 participants