[jira] [Commented] (KAFKA-717) scala 2.10 build support

[ https://issues.apache.org/jira/browse/KAFKA-717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697490#comment-13697490 ] Sriram Subramanian commented on KAFKA-717: -- I get the following errors when I try

[jira] [Updated] (KAFKA-879) In system test, read the new leader from zookeeper instead of broker log on completion of become-leader state transition

[ https://issues.apache.org/jira/browse/KAFKA-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Fung updated KAFKA-879: Status: Patch Available (was: Open) kafka-879-v1.patch contains the change to query zookeeper to find out t

[jira] [Updated] (KAFKA-879) In system test, read the new leader from zookeeper instead of broker log on completion of become-leader state transition

[ https://issues.apache.org/jira/browse/KAFKA-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Fung updated KAFKA-879: Attachment: kafka-879-v1.patch Uploaded kafka-879-v1.patch > In system test, read the new l

Re: site updates

1. I think it is fine to do a one-off since it won't impact the APIs. It would be *awesome* to get this working. 2. Let's sync up since I think we may be both working on the same page. -Jay On Mon, Jul 1, 2013 at 9:50 AM, Sriram Subramanian < srsubraman...@linkedin.com> wrote: > Also, > > 1. I

[jira] Subscription: outstanding kafka patches

Issue Subscription Filter: outstanding kafka patches (76 issues) The list of outstanding kafka patches Subscriber: kafka-mailing-list Key Summary KAFKA-956 High-level consumer fails to check topic metadata response for errors https://issues.apache.org/jira/browse/KAF

Re: site updates

Also, 1. I am trying to get the api stuff working but it is little but of work. I need to make Kafka compile with Scala 2.10 first. 2. I have started a design page for kafka replication. The idea is that it goes as a separate section under the current design page. I will update the page today and

[jira] [Commented] (KAFKA-956) High-level consumer fails to check topic metadata response for errors

[ https://issues.apache.org/jira/browse/KAFKA-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696943#comment-13696943 ] Sam Meder commented on KAFKA-956: - I don't think it has anything to do with topic creation,

Re: site updates

Yeah thanks for the feedback, that's helpful. Here was my thinking: 1. I think it just makes sense to have one design and implementation page which describe the most recent release and live at the top level. You could imagine wanting to read older design pages but that seems a bit unlikely mostly,

[jira] [Commented] (KAFKA-956) High-level consumer fails to check topic metadata response for errors

[ https://issues.apache.org/jira/browse/KAFKA-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696896#comment-13696896 ] Jun Rao commented on KAFKA-956: --- This problem seems to only occur if a consumer is started at

[jira] [Commented] (KAFKA-956) High-level consumer fails to check topic metadata response for errors

[ https://issues.apache.org/jira/browse/KAFKA-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696789#comment-13696789 ] Sam Meder commented on KAFKA-956: - I guess we can carry my patch locally for now (we don't