Build failed in Jenkins: kafka-trunk-jdk9 #463

See Changes: [wangguoz] MINOR: Remove code duplication + excessive space (#4683) -- [...truncated 1.48 MB...] kafka.message.ByteBufferMessageSetTest > testWriteToChannelTh

Build failed in Jenkins: kafka-trunk-jdk7 #3242

See Changes: [wangguoz] MINOR: Remove code duplication + excessive space (#4683) -- [...truncated 418.73 KB...] kafka.zk.KafkaZkClientTest > testDeleteRecursive PASSED ka

Build failed in Jenkins: kafka-trunk-jdk8 #2465

See Changes: [wangguoz] MINOR: Remove code duplication + excessive space (#4683) -- [...truncated 419.48 KB...] kafka.zookeeper.ZooKeeperClientTest > testZNodeChildChange

Re: [DISCUSS] KIP-258: Allow to Store Record Timestamps in RocksDB

@John, Guozhang, thanks a lot for your comments. Very long reply... About upgrading the rebalance metadata: Another possibility to do this, would be to register multiple assignment strategies for the 1.2 applications. For this case, new instances would be configured to support both and the brok

Re: [DISCUSS] KIP-253: Support in-order message delivery with partition expansion

Hey Jason, This is a good solution on the server side for log compacted topic. Thinking about this more, there maybe another probably simpler solution on the client side for log compacted topics. This solution is now specified in the section "Changes in how producer produced keyed messages to log

Re: [DISCUSSION] KIP-266: Add TimeoutException to KafkaConsumer#position()

Hi all, I updated the KIP where overloading position() is now the favored approach. Bounding position() using requestTimeoutMs has been listed as rejected. Any thoughts? On Tue, Mar 6, 2018 at 6:00 PM, Guozhang Wang wrote: > I agree that adding the overloads is most flexible. But going for tha