Hi Jay.
Agreed, we're planning to try to do the compression before the producer
with 0.8 as we get back to this part, hopefully this week. I saw your other
JIRA issue about the copying in the code path so that looks promising as
well.
Thanks for all the responses, really appreciate the effort and
[
https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728571#comment-13728571
]
Dan F commented on KAFKA-881:
-
Sam: Thanks for that. It would be comforting to know if/when we
[
https://issues.apache.org/jira/browse/KAFKA-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728575#comment-13728575
]
Jay Kreps commented on KAFKA-527:
-
The general idea of the refactoring would be to allow di
[
https://issues.apache.org/jira/browse/KAFKA-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728577#comment-13728577
]
Jay Kreps commented on KAFKA-996:
-
+1 but can we apply this on trunk? We are trying to mini
[
https://issues.apache.org/jira/browse/KAFKA-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps closed KAFKA-994.
---
> High level consumer doesn't throw an exception when the message it is trying
> to fetch exceeds the configu
[
https://issues.apache.org/jira/browse/KAFKA-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728583#comment-13728583
]
Jay Kreps commented on KAFKA-992:
-
This is good, this can go on trunk, right?
[
https://issues.apache.org/jira/browse/KAFKA-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-995:
Fix Version/s: 0.8.1
> Enforce that the value for replica.fetch.max.bytes is always >= the value for
>
[
https://issues.apache.org/jira/browse/KAFKA-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728585#comment-13728585
]
Jay Kreps commented on KAFKA-995:
-
Committed on trunk.
> Enforce that the
[
https://issues.apache.org/jira/browse/KAFKA-985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-985.
-
Resolution: Fixed
Fix Version/s: (was: 0.9)
0.8.1
Ack, nice catch.
[
https://issues.apache.org/jira/browse/KAFKA-984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728597#comment-13728597
]
Jay Kreps commented on KAFKA-984:
-
Guys I don't think we should be doing massive surgery on
[
https://issues.apache.org/jira/browse/KAFKA-984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728601#comment-13728601
]
Sriram Subramanian commented on KAFKA-984:
--
Agreed. I share the same thought and h
[
https://issues.apache.org/jira/browse/KAFKA-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-718:
Attachment: KAFKA-718-v4.patch
New patch. Rebased. Fixed logging in tools so that we no longer spew crazy lo
This is a set of good housekeeping things for 0.8 open source release:
https://issues.apache.org/jira/browse/KAFKA-718
This is just a small set of trivial cleanups that are very visible:
- Fix logging for tools so we don't spew log messages in with tool output
- Fix GC settings so we don't default
[
https://issues.apache.org/jira/browse/KAFKA-717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728695#comment-13728695
]
stephen samuel commented on KAFKA-717:
--
I've forked Kafka and patched 0.8 client code
[
https://issues.apache.org/jira/browse/KAFKA-717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728704#comment-13728704
]
Rob Withers commented on KAFKA-717:
---
I just realized that this is as it should be. The b
15 matches
Mail list logo