Definitely no plans in 0.8, we are trying to get it out the door so we
really want to change as little as possible.
We haven't had huge discussions around 0.9 yet, but some of us have had an
interest in simplifying the client implementation. To me this would mean
(1) move the consumer co-ordinatio
Seems to be a commonly discussed topic. What do people thing about this?
Are there any plans for it in 0.8?
When I've done stuff like this in the past for projects, it's been a
combination of reorganizing code and configuring a build tool like Ivy
using sub-modules. Does sbt support modules in
+1 from me, though I did submit the patch
On 12/13/12 1:40 AM, Joe Stein wrote:
+1 on the code change looks alright, I prefer using the java version in
this case only because we are using an implementation from another project
and its a drop in ... no reason to change things without good reason,
[
https://issues.apache.org/jira/browse/KAFKA-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13532884#comment-13532884
]
derek commented on KAFKA-139:
-
Since we're on Git now, I've pushed a branch with the changes he
[
https://issues.apache.org/jira/browse/KAFKA-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-598:
-
Attachment: KAFKA-598-v3.patch
Quick overview of revised patch:
1 - Addressed your comment about the prev
On 12/14/12 4:30 PM, Jay Kreps wrote:
http://kafka.apache.org/
I will set up redirects from the old to the new.
If folks could sanity check the links, email addresses, english, and so on
that would be swell.
-Jay
Small nit - Flume has graduated and has a new webpage
http://flume.apache.org/
The bug bit me, so reapplied my patch on the latest from the 0.8 branch. I
pushed it up to my Git repo:
https://github.com/dchenbecker/kafka-sbt
I got it back to the point where it compiles, tests, etc. The stumbling
block last time was packaging, so there's still a fair bit of work to do
there.
[
https://issues.apache.org/jira/browse/KAFKA-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-664:
-
Attachment: KAFKA-664-v4.patch
All good points - here is v4 with those changes.
> Kafka s
Hi,
I ran FF linkchecker plugin on the new site and found a few things:
* api docs in the left menu link to 0.7.1 is that right or is there api
docs for 0.7.2?
* on
http://kafka.apache.org/downloads.html
the KEYS link: http://svn.apache.org/repos/asf/incubator/kafka/KEYS gives
404
* on
ht
Okay, I set up redirects. Since our old website was updated via some 20
minute rsync script and since ModRewrite is mind boggling it is kind of
hard to say whether people will actually be properly redirected to the new
site or whether I just destroyed the old site. We will see in 20 minutes.
What
Awesome! I hope to have a pull request for updated SBT builds some time
next week :)
On Fri, Dec 14, 2012 at 12:50 PM, Jay Kreps wrote:
> And as with apache svn, it sounds like you need to use https if you want a
> writable version and http otherwise...
>
> -Jay
>
>
> On Fri, Dec 14, 2012 at 10
And as with apache svn, it sounds like you need to use https if you want a
writable version and http otherwise...
-Jay
On Fri, Dec 14, 2012 at 10:43 AM, Jun Rao wrote:
> Hi, Everyone,
>
> We have moved Kafka repo to git. The location of the new repo is at:
> https://git-wip-us.apache.org/repos
Hi, Everyone,
We have moved Kafka repo to git. The location of the new repo is at:
https://git-wip-us.apache.org/repos/asf/kafka.git
Please follow the following instruction on how to use it.
https://git-wip-us.apache.org
Thanks,
Jun
[
https://issues.apache.org/jira/browse/KAFKA-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung closed KAFKA-628.
---
> System Test Failure Case 5005 (Mirror Maker bouncing) - Data Loss in
> ConsoleConsumer
> --
[
https://issues.apache.org/jira/browse/KAFKA-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung resolved KAFKA-628.
-
Resolution: Fixed
This issue is not showing any more in 0.8 branch. So mark this close now.
[
https://issues.apache.org/jira/browse/KAFKA-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13532413#comment-13532413
]
David Arthur commented on KAFKA-374:
Akka seems a bit overkill for this (although it do
Let me go ahead and put in some time in next week to get it running again.
I've only been skimming the emails lately, but is Kafka moved over to Git
yet? Using Git would allow me to avoid some of the issues we ran into
trying to submit an SVN patch due to deleted files, etc. Also, which
branch/revi
[
https://issues.apache.org/jira/browse/KAFKA-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-600.
-
Resolution: Fixed
Since there don't seem to be any objections I am closing out this issue.
[
https://issues.apache.org/jira/browse/KAFKA-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-616:
Labels: newbie (was: )
> Implement acks=0
>
>
> Key: KAFKA-616
>
That sounds like a bug. Don't worry about the script if it is proprietary, I
can just write a simple java test harness. That would actually be a good test
to run going forward.
Sent from my iPhone
On Dec 14, 2012, at 2:21 AM, ben fleis wrote:
> Hey Jay, (yes, I just like the sound of that!)
Hey Jay, (yes, I just like the sound of that!)
I have a testing harness for my Node client, but I can't (at the moment)
put it out in the open. If you'd like, I cab share it via LI channels and
get you into full simulation without too much pain, I think.
And yes, they are same partition, same s
21 matches
Mail list logo
