[
https://issues.apache.org/jira/browse/KAFKA-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15760443#comment-15760443
]
Vahid Hashemian commented on KAFKA-3853:
[~jeffwidman] Yes, it did pass. But, unfo
@Jason
Yes, second thought on the number of messages included, the offset delta
will probably be sufficient. The use case I encounter before for number of
messages in a message set is an embedded mirror maker on the destination
broker side which fetches message directly from the source cluster. Id
GitHub user sjmittal opened a pull request:
https://github.com/apache/kafka/pull/2274
Implement topic config for internal topics
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sjmittal/kafka sm
Alternatively you can review and
[
https://issues.apache.org/jira/browse/KAFKA-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15759588#comment-15759588
]
Jeff Widman commented on KAFKA-3853:
Did the KIP get the missing vote required to pass
The details about headers for control messages are still to define. But
yes, the idea is to have some common default behavior that clients would
need to implement.
The point is, that "regular headers" add meta data to regular messages.
Thus, those messages will be returned to the user via .poll().
[
https://issues.apache.org/jira/browse/KAFKA-4555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15759489#comment-15759489
]
ASF GitHub Bot commented on KAFKA-4555:
---
GitHub user rekhajoshm opened a pull reques
GitHub user rekhajoshm opened a pull request:
https://github.com/apache/kafka/pull/2273
KAFKA-4555: Using Hamcrest for expressive intent in tests
- Adding hamcrest in gradle files
- Using hamcrest in couple of tests - SourceTaskOffsetCommitterTest,
MetadataTest
You can merge th
Rekha Joshi created KAFKA-4555:
--
Summary: Using Hamcrest for easy intent expression in tests
Key: KAFKA-4555
URL: https://issues.apache.org/jira/browse/KAFKA-4555
Project: Kafka
Issue Type: Test
[
https://issues.apache.org/jira/browse/KAFKA-4527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15759269#comment-15759269
]
Roger Hoover commented on KAFKA-4527:
-
Happened again:
http://confluent-systest.s3-w
[
https://issues.apache.org/jira/browse/KAFKA-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15759266#comment-15759266
]
Roger Hoover commented on KAFKA-3808:
-
Happened again:
http://confluent-systest.s3-w
[
https://issues.apache.org/jira/browse/KAFKA-4166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15759264#comment-15759264
]
Roger Hoover commented on KAFKA-4166:
-
Similar failure:
http://confluent-systest.s3-w
[
https://issues.apache.org/jira/browse/KAFKA-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15759260#comment-15759260
]
Roger Hoover commented on KAFKA-4526:
-
Thanks, [~apurva]
> Transient failure in Throt
Would be grateful to hear opinions from experts out there. Thanks in advance
> 在 2016年12月16日,下午6:17,Json Tu 写道:
>
> Hi all,
> we have a cluster of 0.9.0.0 with 3 nodes, we have a topic with 3
> replicas, and send it with ack -1, our sending latency is avg 7ms. I prepare
> to optimize pe
[
https://issues.apache.org/jira/browse/KAFKA-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ning Zhang resolved KAFKA-3841.
---
Resolution: Won't Fix
> MirrorMaker topic renaming
> --
>
> Ke
[
https://issues.apache.org/jira/browse/KAFKA-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Cheng resolved KAFKA-4187.
Resolution: Resolved
[~m...@vrischmann.me] was able to use MirrorMakerMessageHandler to solve this.
15 matches
Mail list logo