[
https://issues.apache.org/jira/browse/KAFKA-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13535104#comment-13535104
]
Jay Kreps commented on KAFKA-675:
-
+1
I will check this in on 0.8 if no objections from an
[
https://issues.apache.org/jira/browse/KAFKA-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-672.
-
Resolution: Fixed
> Merge 0.8 changes to trunk
> --
>
> Key: K
[
https://issues.apache.org/jira/browse/KAFKA-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-676.
-
Resolution: Fixed
> Create a test jar
> -
>
> Key: KAFKA-676
>
I did the merge from 0.8. If you see anything that looks wrong, let me
know. This does seem to produce an impressive flury of emails on the
commits list, one for each change I merged in. Sorry for the spam.
-Jay
[
https://issues.apache.org/jira/browse/KAFKA-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matan updated KAFKA-675:
Attachment: kafka-675-updated.patch
I've included a new patch file with the changes you suggested.
In summary:
1.
[
https://issues.apache.org/jira/browse/KAFKA-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13535035#comment-13535035
]
Neha Narkhede commented on KAFKA-676:
-
+1
> Create a test jar
> --
[
https://issues.apache.org/jira/browse/KAFKA-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps reassigned KAFKA-676:
---
Assignee: Jay Kreps
> Create a test jar
> -
>
> Key: KAFKA-676
>
[
https://issues.apache.org/jira/browse/KAFKA-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-676:
Attachment: KAFKA-676.patch
Trivial change to add a test jar.
> Create a test jar
> ---
Jay Kreps created KAFKA-676:
---
Summary: Create a test jar
Key: KAFKA-676
URL: https://issues.apache.org/jira/browse/KAFKA-676
Project: Kafka
Issue Type: New Feature
Affects Versions: 0.8
Good point about compressed message sets. I think that that works and is
simpler. We might still need the txn id to be able to do the application to
the hashmap atomically, but this depends on a number of details that aren't
really spec'd out, in particular how the replicas keep their hashmap fed
a
Thanks for the proposal. Added a couple of comments to the wiki.
Thanks,
Jun
On Mon, Dec 17, 2012 at 10:45 AM, Jay Kreps wrote:
> Hey Guys,
>
> David has made a bunch of progress on the offset commit api implementation.
>
> Since this is a public API it would be good to do as much thinking up-
[
https://issues.apache.org/jira/browse/KAFKA-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534856#comment-13534856
]
Prashanth Menon commented on KAFKA-330:
---
I'll take this on, hoping to get a patch in
[
https://issues.apache.org/jira/browse/KAFKA-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prashanth Menon reassigned KAFKA-330:
-
Assignee: Prashanth Menon
> Add delete topic support
> -
>
>
13 matches
Mail list logo