Update 2015-12-17 #3
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
… get out of sync Author: Jason Gustafson <jason@confluent.io> Reviewers: Michal Turek, Ismael Juma, Guozhang Wang Closes #666 from hachikuji/KAFKA-2978
Author: Grant Henke <granthenke@gmail.com> Reviewers: Gwen Shapira Closes #676 from granthenke/doc-link
Author: Jason Gustafson <jason@confluent.io> Reviewers: Ismael Juma <ismael@juma.me.uk>, Ewen Cheslack-Postava <ewen@confluent.io> Closes #675 from hachikuji/KAFKA-2990
Author: Guozhang Wang <wangguoz@gmail.com> Reviewers: Ismael Juma Closes #674 from guozhangwang/K2837
People are facing problems upgrading their clusters with configured broker IDs above 1000 due to `reserved.broker.max.id` which wasn't very well announced. This PR attempts to improve that somewhat by fixing the broker config docs and adding a note to the upgrade documentation. Author: Magnus Edenhill <magnus@edenhill.se> Reviewers: Grant Henke <granthenke@gmail.com>, Ewen Cheslack-Postava <ewen@confluent.io> Closes #670 from edenhill/docs-reserved.broker.max.id
Mention Java 7 requirement, fix and improve formatting and remove obsolete reference to SVN website. Author: Ismael Juma <ismael@juma.me.uk> Reviewers: Sriharsha Chintalapani <harsha@hortonworks.com>, Jason Gustafson <jason@confluent.io> Closes #677 from ijuma/mention-java-requirement-in-readme
Author: Vahid Hashemian <vahidhashemian@us.ibm.com> Reviewers: Gwen Shapira Closes #673 from vahidhashemian/typo02/fix_typos_in_code_comments
…sts equivalent Author: Grant Henke <granthenke@gmail.com> Reviewers: Gwen Shapira Closes #647 from granthenke/isr-request
Author: Gwen Shapira <cshapi@gmail.com> Reviewers: Ewen Cheslack-Postava <ewen@confluent.io> Closes #681 from gwenshap/minor-herder-comment
…etcher We're seeing some GC pause issues in production, and during our investigation found that the thunks created during invocation of three trace statements guarded in this PR were responsible for ~98% of all allocations by object count and ~90% by size. While I'm not sure that this was actually the cause of our issue, it seems prudent to avoid useless allocations in a tight loop. I realize that the trace() call does its own guarding internally, however it's insufficient to prevent allocation of the thunk. This is my original work, and I license it to the Kafka project under the project's Apache license. Author: Cory Kolbeck <cory.kolbeck@urbanairship.com> Reviewers: Gwen Shapira Closes #682 from ckolbeck/guard-trace-statements
Credit to Gwen for some of the text. Author: Ismael Juma <ismael@juma.me.uk> Reviewers: Guozhang Wang <wangguoz@gmail.com>, Ewen Cheslack-Postava <ewen@confluent.io> Closes #678 from ijuma/mirror-maker-compatibility-note
guozhangwang Author: Yasuhiro Matsuda <yasuhiro@confluent.io> Reviewers: Guozhang Wang Closes #680 from ymatsuda/perf
guozhangwang At DAG level, `KTable<K,V>` sends (key, (new value, old value)) to down stream. This is done by wrapping the new value and the old value in an instance of `Change<V>` class and sending it as a "value" part of the stream. The old value is omitted (set to null) by default for optimization. When any downstream processor needs to use the old value, the framework should enable it (see `KTableImpl.enableSendingOldValues()` and implementations of `KTableProcessorSupplier.enableSensingOldValues()`). NOTE: This is meant to be used by aggregation. But, if there is a use case like a SQL database trigger, we can add a new KTable method to expose this. Author: Yasuhiro Matsuda <yasuhiro@confluent.io> Reviewers: Guozhang Wang Closes #672 from ymatsuda/trigger
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.