GitHub user becketqin opened a pull request:

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

    KAFKA-3025 Added timetamp to Message and use relative offset.

    See KIP-31 and KIP-32 for details.
    
    A few notes on the patch:
    1. This patch only implements the server side message format change. It 
also implements the message format conversion.
    2. All unit tests passed when set . Some of the tests require specific 
message format versions. I will fix them once the change on o.a.k.clients are 
done.
    3. The unit tests were run with new and old message format.
    4. When message format conversion occurs during consumption, the consumer 
will not be able to detect the message size too large situation. I did not try 
to fix this because the situation seems rare and only happen during migration 
phase.
    
    The remaining work for KIP-31 and KIP-32 is
    1. Add timestamp and relative offset to o.a.k.clients. 
    2. Add more unit test and integration test


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

    $ git pull https://github.com/becketqin/kafka KAFKA-3025

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

    https://github.com/apache/kafka/pull/764.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 #764
    
----
commit 5604b4a57fff61188c562cc634daca4dee72aa4f
Author: Jiangjie Qin <becket....@gmail.com>
Date:   2016-01-07T14:30:39Z

    Added timetamp to Message and use relative offset.
    See KIP-31 and KIP-32 for details.

----


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to