You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by gwenshap <gi...@git.apache.org> on 2016/07/28 18:52:42 UTC

[GitHub] kafka pull request #1678: KAFKA-3852: Clarify how to handle message format u...

GitHub user gwenshap opened a pull request:

    https://github.com/apache/kafka/pull/1678

    KAFKA-3852: Clarify how to handle message format upgrade without kill\u2026

    \u2026ing performance

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gwenshap/kafka kafka-3852

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/1678.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1678
    
----
commit 046919994032cf873f74da7a34db30cb84d3371e
Author: Gwen Shapira <cs...@gmail.com>
Date:   2016-07-28T18:51:27Z

    KAFKA-3852: Clarify how to handle message format upgrade without killing performance

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] kafka pull request #1678: KAFKA-3852: Clarify how to handle message format u...

Posted by asfgit <gi...@git.apache.org>.

Github user asfgit closed the pull request at:

    https://github.com/apache/kafka/pull/1678


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---