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

Merge upstream master changes #3

Merged
merged 45 commits into from
Mar 27, 2017
Merged

Merge upstream master changes #3

merged 45 commits into from
Mar 27, 2017

Conversation

cmshetty
Copy link

No description provided.

hollow and others added 30 commits January 25, 2017 15:55
Mitigation for the quasi-breaking change as noted in IBM#816.
make list of brokers available through sarama.Client
Fixing link to CONTRIBUTING.MD file in README.md file
Formatting all files with gofmt -s
Removed all else statement where if block ends with a return
AsyncClose has nothing to do with flushes at all.

Close *waits* for messages to be flushed, but does not *trigger* a flush
itself.
The wrapper function NewCustomHashPartitioner is a wrapper around the PartitionerConstructor, allowing for specifying the hash algorithm, which will be used.
Add functionality for custom hash partitioner.
Tweak documentation of Close/AsyncClose methods
Fix incorrect "larger than MaxRequestSize" message, closes IBM#836
Passing an already instantiated hasher is a really bad idea. Instead pass a function returning the expected interface,
so the hasher is instantiated when needed, also assuring there's one hasher for each partitionDispatcher and thus avoid concurrency problems."
eapache and others added 15 commits March 2, 2017 15:05
In Producer.Flush, if Bytes or Messages is set but Frequency is not then
messages may not get flushed because Sarama will wait forever to fulfill
the Byte/Message configurations.
Update dev at the same time.
Bump supported/tested go and kafka versions
Remove type hasherFunc.
Adjust doc comments for the NewCustomHashPartitioner.
The kafka protocol for JoinGroupRequest allows you to specify priority
on group protocols for seamless rollout of new protocols while a
consumer group is running. The old map was not supporting that use case.

Add an array field (OrderedGroupProtocols) and deprecate the map.
Permit protocol ordering in JoinGroup requests
Fix tiny typo in examples README link
@cmshetty cmshetty merged commit 20fe3a6 into master Mar 27, 2017
@cmshetty cmshetty deleted the chandra/merge_upstream branch March 27, 2017 16:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

9 participants