I see someone filed a jira, we'll answer there
Neha Narkhede wrote on Wed, Nov 28, 2012 at 16:43:08 -0800:
> Gavin,
>
> Thanks for moving the repository. Any idea what needs to be done to
> get the website moved ?
>
> -Neha
>
> On Wed, Nov 28, 2012 at 4:08 PM, Gavin McDonald
> wrote:
> > Yep
Has there ever been discussion of moving to Git?
-David
John Fung created KAFKA-640:
---
Summary: System Test Failures :
kafka.common.InvalidClientIdException in broker log4j messages
Key: KAFKA-640
URL: https://issues.apache.org/jira/browse/KAFKA-640
Project: Kafk
Yes, we are working on it. We will notify everyone once the git repo is ready.
Thanks,
Neha
On Thu, Nov 29, 2012 at 7:25 AM, David Arthur wrote:
> Has there ever been discussion of moving to Git?
>
> -David
Issue Subscription
Filter: outstanding kafka patches (53 issues)
The list of outstanding kafka patches
Subscriber: kafka-mailing-list
Key Summary
KAFKA-637 Separate log4j environment variable from KAFKA_OPTS in
kafka-run-class.sh
https://issues.apache.org/jira/browse
[
https://issues.apache.org/jira/browse/KAFKA-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506714#comment-13506714
]
John Fung commented on KAFKA-628:
-
This test case is consistently failing in System Test. T
[
https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506824#comment-13506824
]
Otis Gospodnetic commented on KAFKA-133:
There you have it:
zkclient 0.2:
http://s
[
https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506839#comment-13506839
]
Neha Narkhede commented on KAFKA-133:
-
That's great. Thanks a lot Otis for seeing this
[
https://issues.apache.org/jira/browse/KAFKA-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506858#comment-13506858
]
Neha Narkhede commented on KAFKA-633:
-
That happens due to the test failure. If the tes
[
https://issues.apache.org/jira/browse/KAFKA-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-640:
Attachment: kafka-640.patch
This happened because ClientId.validate(clientId) in SimpleConsumer did
[
https://issues.apache.org/jira/browse/KAFKA-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy reassigned KAFKA-633:
Assignee: Joel Koshy
> AdminTest.testShutdownBroker fails
> --
>
[
https://issues.apache.org/jira/browse/KAFKA-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506889#comment-13506889
]
Joel Koshy commented on KAFKA-633:
--
I'll take a look into this.
> AdminTe
[
https://issues.apache.org/jira/browse/KAFKA-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-608:
Status: Patch Available (was: Open)
> getTopicMetadata does not respect producer config setting
Juan Valencia created KAFKA-641:
---
Summary: ConsumerOffsetChecker breaks when using dns names x.b.com
as opposed to raw public IP for broker.
Key: KAFKA-641
URL: https://issues.apache.org/jira/browse/KAFKA-641
[
https://issues.apache.org/jira/browse/KAFKA-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede reassigned KAFKA-608:
---
Assignee: Neha Narkhede
> getTopicMetadata does not respect producer config settings
> ---
[
https://issues.apache.org/jira/browse/KAFKA-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-608:
Status: In Progress (was: Patch Available)
> getTopicMetadata does not respect producer config
[
https://issues.apache.org/jira/browse/KAFKA-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506917#comment-13506917
]
Jay Kreps commented on KAFKA-633:
-
But that's a problem, no? Those test harnesses are suppo
[
https://issues.apache.org/jira/browse/KAFKA-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-608:
Attachment: kafka-608-v1.patch
Attaching a patch that makes the following changes -
1. Fixes the me
[
https://issues.apache.org/jira/browse/KAFKA-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-608:
Status: Patch Available (was: In Progress)
> getTopicMetadata does not respect producer config
I started trying to document the 0.8 protocol from the code and write a
guide to client implementation. This is meant to be a more user-friendly
and up-to-date version of the proposal wiki we had on the protocol changes.
Here is what I wrote up so far:
https://cwiki.apache.org/confluence/display/K
[
https://issues.apache.org/jira/browse/KAFKA-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506934#comment-13506934
]
Joel Koshy commented on KAFKA-633:
--
Yes it's definitely annoying (apart from the test fail
[
https://issues.apache.org/jira/browse/KAFKA-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506985#comment-13506985
]
John Fung commented on KAFKA-640:
-
Thanks Swapnil for the patch. It is working with the lat
Okay here is a proposal to address the issues I raised.
1, 2. Correlation id. This is not strictly speaking needed, but it is maybe
useful for debugging to be able to trace a particular request from client
to server. So we will extend this across all the requests.
3. For metadata response I will t
Jay Kreps created KAFKA-642:
---
Summary: Protocol tweaks for 0.8
Key: KAFKA-642
URL: https://issues.apache.org/jira/browse/KAFKA-642
Project: Kafka
Issue Type: Bug
Reporter: Jay Kreps
T
24 matches
Mail list logo
