Kafka
  1. Kafka
  2. KAFKA-375

update the site page for the 0.7.1 release download and related changes

    Details

    • Type: Task Task
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.7.1
    • Fix Version/s: 0.7.1
    • Component/s: None
    • Labels:
      None
    1. KAFKA-375.patch.v3
      11 kB
      Joe Stein
    2. KAFKA-375.consumerapi.patch.v2
      7 kB
      Joel Koshy
    3. KAFKA-375.consumerapi.patch
      4 kB
      Joel Koshy
    4. KAFKA-375.patch
      3 kB
      Joe Stein

      Activity

      Hide
      Joel Koshy added a comment -

      Joe, thanks for pulling this together. There are some small edits required to the quick start as well (due to the consumer API change). I can add a diff for that in a bit.

      Show
      Joel Koshy added a comment - Joe, thanks for pulling this together. There are some small edits required to the quick start as well (due to the consumer API change). I can add a diff for that in a bit.
      Hide
      Jay Kreps added a comment -

      This is great. Joel, do you think we should add a few lines to the design document anywhere to mention the wildcard support?

      Show
      Jay Kreps added a comment - This is great. Joel, do you think we should add a few lines to the design document anywhere to mention the wildcard support?
      Hide
      Joel Koshy added a comment -

      Yes - added a few more comments on topic filters.

      Show
      Joel Koshy added a comment - Yes - added a few more comments on topic filters.
      Hide
      Jun Rao added a comment -

      Looks good. The only thing is that message format has changed in 0.7.1 slightly (an optional attribute field) and we need to reflect that in design. Once that's fixed, we can commit.

      /**

      • A message. The format of an N byte message is the following:
        *
      • If magic byte is 0
        *
      • 1. 1 byte "magic" identifier to allow format changes
        *
      • 2. 4 byte CRC32 of the payload
        *
      • 3. N - 5 byte payload
        *
      • If magic byte is 1
        *
      • 1. 1 byte "magic" identifier to allow format changes
        *
      • 2. 1 byte "attributes" identifier to allow annotations on the message independent of the version (e.g. compression enabled, type of codec used)
        *
      • 3. 4 byte CRC32 of the payload
        *
      • 4. N - 6 byte payload
      • */

      Show
      Jun Rao added a comment - Looks good. The only thing is that message format has changed in 0.7.1 slightly (an optional attribute field) and we need to reflect that in design. Once that's fixed, we can commit. /** A message. The format of an N byte message is the following: * If magic byte is 0 * 1. 1 byte "magic" identifier to allow format changes * 2. 4 byte CRC32 of the payload * 3. N - 5 byte payload * If magic byte is 1 * 1. 1 byte "magic" identifier to allow format changes * 2. 1 byte "attributes" identifier to allow annotations on the message independent of the version (e.g. compression enabled, type of codec used) * 3. 4 byte CRC32 of the payload * 4. N - 6 byte payload */
      Hide
      Joe Stein added a comment -

      v3 patch attached, covers the other patches together + the message format updated in design.html

      Show
      Joe Stein added a comment - v3 patch attached, covers the other patches together + the message format updated in design.html
      Hide
      Joe Stein added a comment -

      commited

      Show
      Joe Stein added a comment - commited

        People

        • Assignee:
          Unassigned
          Reporter:
          Joe Stein
        • Votes:
          0 Vote for this issue
          Watchers:
          4 Start watching this issue

          Dates

          • Created:
            Updated:
            Resolved:

            Development