Congrats all around!
Sent from my phone
On Nov 21, 2012, at 5:39 PM, Prashanth Menon wrote:
> Awesome! Congrats everybody!
>
> - Prashanth
>
>
> On Wed, Nov 21, 2012 at 5:14 PM, Jay Kreps wrote:
>
>> We graduated!
>>
>> -Jay
>> -- Forwarded message --
>> From: Doug Cutting
>>
BTW, here are some cURL calls from my test environment:
https://gist.github.com/e59b9c8ee4ae56dad44f
On Nov 20, 2012, at 4:08 PM, David Arthur wrote:
> Another bump for this thread...
>
> For those just joining, this prototype is a simple HTTP server that proxies
> the complex c
thread per topic+group?
Cheers
-David
On Sep 10, 2012, at 9:49 AM, David Arthur wrote:
> Bump.
>
> Anyone have feedback on this approach?
>
> -David
>
> On Aug 24, 2012, at 12:37 PM, David Arthur wrote:
>
>> Here is an initial pass at a Kafka REST proxy (in Scala
On Thu, Nov 8, 2012 at 10:32 AM, David Arthur wrote:
>
>> There is a line item on the project ideas for "improved stream processing
>> libraries". I was wondering if anyone has done any work on this. I know you
>> can hook Kafka into things like Storm and S4(?),
There is a line item on the project ideas for "improved stream processing
libraries". I was wondering if anyone has done any work on this. I know you can
hook Kafka into things like Storm and S4(?), but I'm not looking for a
CEP/dataflow thing, just distributed stream processing
-David
Read through the quick start on the project page
http://incubator.apache.org/kafka/quickstart.html
Kafka consumers need to be in the same "consumer group" in order to act as one
(one message goes to one consumer, instead of going to all consumers). This
functionality requires that you have more
[
https://issues.apache.org/jira/browse/KAFKA-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486297#comment-13486297
]
David Arthur commented on KAFKA-397:
Try cleaning out ZooKeeper as well as the K
[
https://issues.apache.org/jira/browse/KAFKA-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-474:
---
Attachment: KAFKA-474.patch
Something as simple as this?
> support changing h
[
https://issues.apache.org/jira/browse/KAFKA-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-456:
---
Affects Version/s: (was: 0.7.2)
(was: 0.7.1)
Status
[
https://issues.apache.org/jira/browse/KAFKA-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-456:
---
Attachment: KAFKA-456.patch
I looked around in other parts of the code for similar situations (lots
[
https://issues.apache.org/jira/browse/KAFKA-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469333#comment-13469333
]
David Arthur commented on KAFKA-474:
I took a look at AbstractFetcherManager and
[
https://issues.apache.org/jira/browse/KAFKA-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-363:
---
Attachment: (was: KAFKA-363.patch)
> Replace numerical compression codes in config w
[
https://issues.apache.org/jira/browse/KAFKA-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-363:
---
Attachment: KAFKA-363.patch
Compilation error - embarrassing. Maybe I should be more careful since
[
https://issues.apache.org/jira/browse/KAFKA-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-363:
---
Attachment: KAFKA-363.patch
Joel, thanks for the review.
I've changed the config property ba
[
https://issues.apache.org/jira/browse/KAFKA-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-363:
---
Attachment: (was: KAFKA-363.patch)
> Replace numerical compression codes in config w
Answered my own question:
The gzipped payload is an encoded MessageSet itself, not just the gzip of a
single message's payload.
-David
On Sep 26, 2012, at 7:43 PM, David Arthur wrote:
> I'm working on adding gzip support to the Python client, and I'm running into
> s
I'm working on adding gzip support to the Python client, and I'm running into
some issues. I think I might not understand exactly how the compression is
supposed to be implemented.
My initial approach was to set the compression byte to 1 to indicate gzip, and
then simply gzip the payload. Here
[
https://issues.apache.org/jira/browse/KAFKA-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-363:
---
Attachment: KAFKA-363.patch
> Replace numerical compression codes in config with something hu
[
https://issues.apache.org/jira/browse/KAFKA-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-363:
---
Attachment: (was: KAFKA-363.patch)
> Replace numerical compression codes in config w
[
https://issues.apache.org/jira/browse/KAFKA-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-363:
---
Status: Patch Available (was: Open)
Here's a go at a simple fix for this. I added a "name&
[
https://issues.apache.org/jira/browse/KAFKA-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-363:
---
Attachment: KAFKA-363.patch
> Replace numerical compression codes in config with something hu
I moved this into a standalone project on GitHub:
https://github.com/mumrah/kafka-python
Any suggestions for features beyond the protocol support?
Also, where can I find details on protocol changes for 0.8 (if it's even
finalized yet)?
Cheers,
David
On Sep 22, 2012, at 2:55 PM, David A
+1 for pulling out client libs. That said, should the client libs be pulled
into self-contained projects?
On Sep 22, 2012, at 6:17 PM, Lorenzo Alberton wrote:
> It's probably better to remove the client libraries and add a README with a
> link to this wiki page:
>
> https://cwiki.apache.org/co
I made some improvements to the Python client. I implemented fetch,
multi-fetch, multi-produce, and offset requests; I also documented each
request/response with the wire format. I've committed to my Kafka branch on
GitHub. I have only briefly tested things.
https://github.com/mumrah/kafka/tree
[
https://issues.apache.org/jira/browse/KAFKA-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460593#comment-13460593
]
David Arthur edited comment on KAFKA-523 at 9/22/12 3:2
[
https://issues.apache.org/jira/browse/KAFKA-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460593#comment-13460593
]
David Arthur edited comment on KAFKA-523 at 9/22/12 3:2
[
https://issues.apache.org/jira/browse/KAFKA-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-523:
---
Description:
There is not error handling in the KafkaRequestHandlers#handleOffsetRequest, as
a
[
https://issues.apache.org/jira/browse/KAFKA-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-523:
---
Description:
There is not error handling in the KafkaRequestHandlers#handleOffsetRequest, as
a
[
https://issues.apache.org/jira/browse/KAFKA-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-523:
---
Description:
There is not error handling in the KafkaRequestHandlers#handleOffsetRequest, as
a
David Arthur created KAFKA-523:
--
Summary: OffsetRequest handler does not handle errors
Key: KAFKA-523
URL: https://issues.apache.org/jira/browse/KAFKA-523
Project: Kafka
Issue Type: Bug
Bump.
Anyone have feedback on this approach?
-David
On Aug 24, 2012, at 12:37 PM, David Arthur wrote:
> Here is an initial pass at a Kafka REST proxy (in Scala)
>
> https://github.com/mumrah/kafka/blob/rest/contrib/rest-proxy/src/main/scala/RESTServer.scala
>
> The basic gis
will be some overhead for the extra hop, but
>> then there is some overhead for HTTP itself.
>>
>> This is just my personal opinion, it would be great to hear what other
>> think.
>>
>> -Jay
>>
>> On Mon, Aug 6, 2012 at 5:39 AM, David Arthur wrote:
&
[
https://issues.apache.org/jira/browse/KAFKA-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-468:
---
Priority: Trivial (was: Major)
> String#getBytes is platform depend
[
https://issues.apache.org/jira/browse/KAFKA-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-468:
---
Attachment: KAFKA-468.diff
> String#getBytes is platform depend
[
https://issues.apache.org/jira/browse/KAFKA-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-468:
---
Fix Version/s: 0.8
Affects Version/s: 0.8
Status: Patch Available (was: Open
David Arthur created KAFKA-468:
--
Summary: String#getBytes is platform dependent
Key: KAFKA-468
URL: https://issues.apache.org/jira/browse/KAFKA-468
Project: Kafka
Issue Type: Bug
verhead for HTTP itself.
>
> This is just my personal opinion, it would be great to hear what other
> think.
>
> -Jay
>
> On Mon, Aug 6, 2012 at 5:39 AM, David Arthur wrote:
>
>> I'd be happy to collaborate on this, though it's been a while since I've
&g
ve proposed, rather than a proxy.
> The proxy was low-hanging fruit within Box because we already had a framework
> for cranking out a REST API quite easily and a set of Kafka+ZK classes. It
> was simply stitching the two together.
>
> -Jonathan
>
> On Mon, Aug 6, 2012 at
yours later this afternoon, we should work together.
>
> -Jonathan
>
>
> On Fri, Aug 3, 2012 at 7:41 AM, David Arthur wrote:
>
>> I'd like to tackle this project (assuming it hasn't been started yet).
>>
>> I wrote up some initial thoughts here: https://gist.git
I'd like to tackle this project (assuming it hasn't been started yet).
I wrote up some initial thoughts here: https://gist.github.com/3248179
TLDR; use Range header for specifying offsets, simple URIs like
/kafka/topics/[topic]/[partition], use for a simple transport of bytes and/or
represent
not sure what's the best thing to do here.
Cheers
-David
On Jul 31, 2012, at 5:48 PM, Neha Narkhede wrote:
> David,
>
> Would you mind sending around the error stack traces ? That will help
> determine the right fix.
>
> Thanks,
> Neha
>
> On Tue, Jul 31, 20
Greetings all,
I'm using the KafkaLog4jAppender with Solr and ran into an interesting issue
recently. The disk filled up on my Kafka broker (just a single broker, this is
a dev environment) and Solr slowed down to a near halt. My best estimation is
that each log4j log message created was incur
[
https://issues.apache.org/jira/browse/KAFKA-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-242:
---
Attachment: kafka.log
Annotated log messages from two different test runs. For each test run, 20k
Project: Kafka
Issue Type: Bug
Components: clients
Affects Versions: 0.7
Reporter: David Arthur
When calling ConsumerConnector.createMessageStreams in rapid succession, the
Consumer offset is incorrectly advanced causing the consumer to lose
44 matches
Mail list logo
