+1
On 10/18/2012 07:03 PM, Jakob Homan wrote:
As discussed previously, Kafka is ready to graduate and we've drafted
resolution to make that happen. Resolution is now corrected from my overly
giraphy version (thanks, Joel for catching that):
Please cast your votes:
[ ] +1 Graduate Kafka
https://issues.apache.org/jira/browse/INFRA-5111
Pleaes check out
https://git-wip-us.apache.org/repos/asf/incubator-kafka.git (currently
read only) and report on any issues. Joe and I were looking at the git
mirror the other day (which this is based on) and didn't notice
anything, so any bugs
Thanks for writing this up Jakob.
There are a number of current comitters who are more worthwhile PMC
choices then myself. To get the TLP off on the right foot perhaps now
is the time to straighten out how we want comitter vs PMC member to work
there.
On 09/22/2012 05:55 PM, Jakob Homan wrote:
On 2012-09-13 13:15, Joe Stein wrote:
I am working on a new product that has 0.7.1 in it don't mind even
pushing 0.7.2 into or 0.8 and releasing both in succession.
Do yo want help with the mechanics of the release itself?
On a tangentially related note with regards to branches I think the
[
https://issues.apache.org/jira/browse/KAFKA-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13428534#comment-13428534
]
Chris Burroughs commented on KAFKA-377:
---
I clicked through everything at
https
? If so, maybe it's better to wait until 0.8 is released.
Jun
On Mon, Jul 30, 2012 at 5:40 PM, Chris Burroughs
chris.burrou...@gmail.comwrote:
I was originally going to follow this was a [VOTE] thread, but most of
the responses are a +1 anyway. I think we can do
https://issues.apache.org/jira/browse/INFRA-5111
On 07/30/2012 08:40 PM, Chris Burroughs wrote:
I was originally going to follow this was a [VOTE] thread, but most of
the responses are a +1 anyway. I think we can do this and it will be a
significant improvement. I'll follow up with INFRA
.
On 07/26/2012 11:39 AM, Chris Burroughs wrote:
It came up in the 0.7.2 thread that with the number of parallel branches
git may be preferable to svn for our current and future workflow. I'd
like to gauge interest in possibly switching from svn to git.
Currently INFRA can provide read/write
On 07/26/2012 02:43 PM, Joel Koshy wrote:
+1 for git in general - however, the apache git mirror has been working
pretty well for me for local work/code review. So if the caveats you
mention are significant enough then maybe we should stay on svn?
I think the caveats are of the things *could*
most people are using the
svn-git integration anyway.
Anyone know the state of git support at apache? I heard other projects have
switched over. Is that generally available?
Sent from my iPhone
On Jul 26, 2012, at 5:31 AM, Chris Burroughs chris.burrou...@gmail.com
wrote:
Would
It came up in the 0.7.2 thread that with the number of parallel branches
git may be preferable to svn for our current and future workflow. I'd
like to gauge interest in possibly switching from svn to git.
Currently INFRA can provide read/write git hosting at
https://git-wip-us.apache.org/.
[
https://issues.apache.org/jira/browse/KAFKA-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Burroughs updated KAFKA-377:
--
Fix Version/s: (was: 0.7.1)
0.7.2
some of the dist mirrors
[
https://issues.apache.org/jira/browse/KAFKA-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13417625#comment-13417625
]
Chris Burroughs commented on KAFKA-377:
---
INFRA-4975 is closed now, we good here
I added a 0.7.2 release in JIRA for you (Joe, do you have the bits
flipped to be able to do this?)
On 07/18/2012 02:05 PM, Joe Stein wrote:
I was thinking we would have a 0.7.2 release if there are patches in trunk
that folks want to use, why not release them and make it available for
them? I
Thanks Jay. This is a very helpful investigation!
On 05/24/2012 01:40 PM, Jay Kreps wrote:
Unfortunately *any* call to fsync will block appends even in a background
thread so how can we give control over physical disk persistence without
introducing high latency for the producer? The answer
On 06/15/2012 10:21 AM, Jun Rao wrote:
Thanks for everyone who showed up for the user group meeting last night. It
was a good turnout and was very interactive. If you missed the event, the
video recording can be found at
I don't think we should release as is.
- project.version is set to 0.7.0
- Have not released since the general@ threads highlighted the included
jars problem. Thanks for pointing that out Kevan.
(The unit test also don't pass for me but that could easily be a local
issue, I'll try to get a
Currently our jenkins build does not send email. This was my original
preference (hordes of machine emails scare people away from
subscribing). If others would prefer to see build emails sent somewhere
let me know.
https://builds.apache.org/job/Kafka-trunk/
My interpretation of the long Binary dependencies in source releases
thread is that the build tools are (I think) defensible, but it really
would be best if we could get rid of the rest.
I see that Neha and Jacob already did most of the work last round in
KAFKA-222 (go team!). In the comments
As a matter of cleanliness I'd like to remove the old (ie not final) RC
tags from 0.7.0-*. Does anyone have any objections?
On 2012-05-23 23:32, Alan D. Cabrera wrote:
We struggled a bit with licensing and packaging issues but we got those
issues resolved and did a release and this should be pretty easy going
forward.
This is the one point I am hesitant about. I think it would be
reasonable to ask us for a history
Where Jay has set the bar for now sounds good to me. Yeah
review-before-commit!
I think the long term goal of committers == PMC is the right one. While
I am not sure if they have it set as formal policy it seems common on
projects I have observed for new committers to become PMC members $n$
[
https://issues.apache.org/jira/browse/KAFKA-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13179555#comment-13179555
]
Chris Burroughs commented on KAFKA-230:
---
The download link goes directly
[
https://issues.apache.org/jira/browse/KAFKA-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13179002#comment-13179002
]
Chris Burroughs commented on KAFKA-230:
---
See
http://incubator.apache.org/guides
Great work!
Having a solid doc/spec for the wire protocol would also likely decrease
the need to have as many clients in-tree. I think at this point that
would be a good thing.
On 11/23/2011 06:32 PM, David Ormsbee wrote:
Hi folks,
Inspired by the Wire Format wiki entry, I recently created
On 12/03/2011 02:40 PM, Chris Burroughs wrote:
My reading is that since we would only be distributing source code, the
NOTICE file should not reflect binary dependencies and would have *only*
the standard Apache bit [3]. Same for LICENSE.
I suppose any jar's checked into svn would complicate
[
https://issues.apache.org/jira/browse/KAFKA-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13159503#comment-13159503
]
Chris Burroughs commented on KAFKA-216:
---
Could you add something like For Nunit used
ZOOKEEPER-961 is nasty, upgrade to zk 3.3.4
---
Key: KAFKA-218
URL: https://issues.apache.org/jira/browse/KAFKA-218
Project: Kafka
Issue Type: Bug
Reporter: Chris Burroughs
[
https://issues.apache.org/jira/browse/KAFKA-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155857#comment-13155857
]
Chris Burroughs commented on KAFKA-204:
---
I mean once you hit that all bets are off
[
https://issues.apache.org/jira/browse/KAFKA-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155962#comment-13155962
]
Chris Burroughs commented on KAFKA-134:
---
Is 0.10 still the most recent version
[
https://issues.apache.org/jira/browse/KAFKA-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155970#comment-13155970
]
Chris Burroughs commented on KAFKA-203:
---
I *think* metrics is source compatible
[
https://issues.apache.org/jira/browse/KAFKA-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Burroughs updated KAFKA-204:
--
Attachment: k204-v1.txt
BoundedByteBufferReceive hides OutOfMemoryError
[
https://issues.apache.org/jira/browse/KAFKA-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13151220#comment-13151220
]
Chris Burroughs commented on KAFKA-204:
---
Tiny patch for this one case, created KAFKA
Audit swallowing of exceptions/throwables
-
Key: KAFKA-205
URL: https://issues.apache.org/jira/browse/KAFKA-205
Project: Kafka
Issue Type: Task
Reporter: Chris Burroughs
[
https://issues.apache.org/jira/browse/KAFKA-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Burroughs updated KAFKA-206:
--
Attachment: k206-v1.txt
Still not sure which things actually need to be mentioned in the NOTICE
Reporter: Chris Burroughs
Priority: Critical
private def byteBufferAllocate(size: Int): ByteBuffer = {
var buffer: ByteBuffer = null
try {
buffer = ByteBuffer.allocate(size)
}
catch {
case e: OutOfMemoryError =
throw new RuntimeException(OOME with size
and point them to the new brokers.
What do people feel about this?
Thanks,
Jun
On Sun, Nov 13, 2011 at 5:57 PM, Chris Burroughs
chris.burrou...@gmail.comwrote:
On 11/11/2011 06:01 PM, Jay Kreps wrote:
2. Our current focus for linkedin folks was going to be on replication
which
On 11/11/2011 06:01 PM, Jay Kreps wrote:
2. Our current focus for linkedin folks was going to be on replication
which will be a really disruptive set of features that need to be released
together.
I think there are some differing assumptions on the impact of
replication. My assumption
On 11/11/2011 01:55 PM, Jeffrey Damick wrote:
So with regard to the
KAFKA-187https://issues.apache.org/jira/browse/KAFKA-187 what
is the stance going to be on supporting new compression methods? Is it
expected that all clients 'must' will support them? If not, is there a
set of 'required'
On 11/03/2011 03:41 PM, Alan D. Cabrera wrote:
Zowie. Look at all these jars that I have to make sure are kosher to
distribute:
Can someone help me?
Assuming we can cut down on the boot/test jars. All we need is a table
of jar-name,licence, correct?
To Alan and Jay's point, I don't think there is a need to distribut the
./boot jars.
I thought we went over the rest in KAFKA-142, but looking back it
doesn't sound as definitive.
On 11/03/2011 03:41 PM, Alan D. Cabrera wrote:
Zowie. Look at all these jars that I have to make sure are kosher
An example.
On 10/31/2011 10:57 PM, Chris Burroughs wrote:
Similar information, but different audience. This is about summarising
only what has changed and is operational relevant (special pre/post
upgrade procedure or in this case upgrade order) in plain language.
Think of the experience
https://issues.apache.org/jira/browse/KAFKA/fixforversion/12317243
I don't seen any open issues listed.
On 10/31/2011 06:55 PM, Neha Narkhede wrote:
Chris, please could you elaborate a little more on this ? I think if
this is a small change, we can cut the RC today.
I think we ought to include a NEWS file for users upgading from a
previous version. Projects varry in how they do this, some
, Oct 31, 2011 at 7:21 PM, Chris Burroughs
chris.burrou...@gmail.com wrote:
On 10/31/2011 06:55 PM, Neha Narkhede wrote:
Chris, please could you elaborate a little more on this ? I think if
this is a small change, we can cut the RC today.
I think we ought to include a NEWS file for users upgading
[
https://issues.apache.org/jira/browse/KAFKA-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Burroughs updated KAFKA-91:
-
Attachment: k91-v2.txt
Sorry missed your reply, rebased
[
https://issues.apache.org/jira/browse/KAFKA-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13136630#comment-13136630
]
Chris Burroughs commented on KAFKA-170:
---
Do users care about the topic/partition
I
[
https://issues.apache.org/jira/browse/KAFKA-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13134056#comment-13134056
]
Chris Burroughs commented on KAFKA-166:
---
Coda Hale's metrics package has built
[
https://issues.apache.org/jira/browse/KAFKA-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13134364#comment-13134364
]
Chris Burroughs commented on KAFKA-91:
--
Could I get a review
[
https://issues.apache.org/jira/browse/KAFKA-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13134381#comment-13134381
]
Chris Burroughs commented on KAFKA-91:
--
Our custom build of zkclient isn't in any repo
[
https://issues.apache.org/jira/browse/KAFKA-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13131854#comment-13131854
]
Chris Burroughs commented on KAFKA-164:
---
There are good things to be said about
On 10/17/2011 02:22 PM, Alan D. Cabrera wrote:
Under the Versions tab there should be a Manage Versions link on the
right side.
I don't see Manage Versions :-(
[
https://issues.apache.org/jira/browse/KAFKA-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13129985#comment-13129985
]
Chris Burroughs commented on KAFKA-153:
---
Is this something we want to re-spin
[
https://issues.apache.org/jira/browse/KAFKA-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13129018#comment-13129018
]
Chris Burroughs commented on KAFKA-156:
---
This is more or less what we do
On 10/14/2011 03:44 PM, Alan D. Cabrera wrote:
That's fine. What do others in the community think about this? Were
they counting on a release of Maven artifacts as well? If that's
what is everyone's understanding then the release should be good on
this front.
My expectation was that maven
[
https://issues.apache.org/jira/browse/KAFKA-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13129024#comment-13129024
]
Chris Burroughs commented on KAFKA-156:
---
Sorry, wrong we. I meant this is what
On 10/10/2011 11:08 PM, Alan D. Cabrera wrote:
On Oct 10, 2011, at 5:46 PM, Chris Burroughs wrote:
On 10/02/2011 12:16 PM, Alan D. Cabrera wrote:
I assume that our first release will be 0.6. Is that correct?
Could someone close the old 0.6 jira milestone?
You and all the developers
[
https://issues.apache.org/jira/browse/KAFKA-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13129301#comment-13129301
]
Chris Burroughs commented on KAFKA-156:
---
Perhaps the producers themselves should just
Alan, can we still report and get signoff today. Or is the 12th
deadline a hard one?
On 10/01/2011 10:00 AM, no-re...@apache.org wrote:
Dear Kafka Developers,
This email was sent by an automated system on behalf of the Apache Incubator
PMC.
It is an initial reminder to give you plenty of
[
https://issues.apache.org/jira/browse/KAFKA-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13124099#comment-13124099
]
Chris Burroughs commented on KAFKA-143:
---
- LICENSE files need to have the Copyright
[
https://issues.apache.org/jira/browse/KAFKA-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13124100#comment-13124100
]
Chris Burroughs commented on KAFKA-142:
---
Sorry, I meant the *dependencies* of clients
On 10/09/2011 04:10 PM, Neha Narkhede wrote:
I wondered if it was lying around from the time when Kafka was hosted
on github. Thought we have forgotten to clean it up when we moved to
Apache.
Ah okay, makes sense. I added it in r1153592 for git (and git-svn) users.
Will restore.
: Chris Burroughs
Assignee: Chris Burroughs
Priority: Minor
It's handy for debugging large and unprintable messages.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira
[
https://issues.apache.org/jira/browse/KAFKA-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Burroughs updated KAFKA-152:
--
Attachment: k152-v1.txt
Include payload size in DumpLogSegments
[
https://issues.apache.org/jira/browse/KAFKA-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Burroughs updated KAFKA-91:
-
Status: Patch Available (was: Open)
zkclient does not show up in pom
We have two KEYS files at root/KEYS and trunk/KEYS.
Which is the correct location?
On 10/07/2011 01:18 PM, nehanarkh...@apache.org wrote:
Author: nehanarkhede
Date: Fri Oct 7 17:18:56 2011
New Revision: 1180110
URL: http://svn.apache.org/viewvc?rev=1180110view=rev
Log:
Minor patch, removing the .gitigore file
Why was the .gitignore file removed?
[
https://issues.apache.org/jira/browse/KAFKA-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13123760#comment-13123760
]
Chris Burroughs commented on KAFKA-142:
---
jopt-simple is MIT, but that's still
[
https://issues.apache.org/jira/browse/KAFKA-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13123788#comment-13123788
]
Chris Burroughs commented on KAFKA-149:
---
Thanks, that makes sense. Is there a ticket
[
https://issues.apache.org/jira/browse/KAFKA-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13122486#comment-13122486
]
Chris Burroughs commented on KAFKA-149:
---
I'm not following what was wrong
[
https://issues.apache.org/jira/browse/KAFKA-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Burroughs resolved KAFKA-92.
--
Resolution: Won't Fix
Ah, I see Neha already did.
upgrade to latest stable 0.7
[
https://issues.apache.org/jira/browse/KAFKA-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13120043#comment-13120043
]
Chris Burroughs commented on KAFKA-79:
--
What Jay called compression ids (ie 1==gzip
Great. I've added a .0 to trunk now so we don't forget.
On 10/04/2011 12:39 AM, Jun Rao wrote:
Sure.
Jun
On Mon, Oct 3, 2011 at 7:35 PM, Chris Burroughs
chris.burrou...@gmail.comwrote:
If we want to support people with bugfix only releases (which I think we
are stable enough to do
I have not seen that failure, but I get LogManagerTest failures often
locally. There is a nearby TODO about sleeps and time for metadata updates.
info] == core-kafka / kafka.log.LogManagerTest ==
[info] Test Starting: testCreateLog
[info] Test Passed: testCreateLog
[info] Test Starting:
testUnreachableServer sporadically fails
Key: KAFKA-146
URL: https://issues.apache.org/jira/browse/KAFKA-146
Project: Kafka
Issue Type: Bug
Reporter: Chris Burroughs
Priority
[
https://issues.apache.org/jira/browse/KAFKA-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Burroughs updated KAFKA-92:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
upgrade to latest stable
[
https://issues.apache.org/jira/browse/KAFKA-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Burroughs updated KAFKA-114:
--
Resolution: Fixed
Fix Version/s: 0.7
Status: Resolved (was: Patch Available
[
https://issues.apache.org/jira/browse/KAFKA-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Burroughs updated KAFKA-15:
-
Fix Version/s: 0.7
Unless we want to make this a one off, we need to fix this for the release
: Chris Burroughs
Since scala does not maintain binary compatibly between versions, organizations
tend to have to move all of there code at the same time. It would thus be very
helpful if we could cross build multiple scala versions.
http://code.google.com/p/simple-build-tool/wiki/CrossBuild
On 09/12/2011 01:25 PM, Chris Burroughs wrote:
http://incubator.apache.org/projects/kafka.html has checkboxes for ASF
copyright on file, correct and compatible licenses etc.
These block a podling release, correct? Alan, are there steps we can
take to completing them (make sure
[
https://issues.apache.org/jira/browse/KAFKA-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13089532#comment-13089532
]
Chris Burroughs commented on KAFKA-114:
---
+1
Replace tabs with spaces
[
https://issues.apache.org/jira/browse/KAFKA-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13089965#comment-13089965
]
Chris Burroughs commented on KAFKA-116:
---
IllegalQueueStateException was missed
So from what I can tell it's common practice [1] for Java projects to
switch to using the the org.apache namespace. Scala/kafka doesn't even
follow the reverse FQDM convention, so I don't see a need to change the
source code. But what about for packaging? Ought a project depending
on kafka be
[
https://issues.apache.org/jira/browse/KAFKA-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Burroughs updated KAFKA-90:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
remove in tree zk jar
[
https://issues.apache.org/jira/browse/KAFKA-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13085697#comment-13085697
]
Chris Burroughs commented on KAFKA-96:
--
I created KAFKA-105 to split off the logging
Include rolledup segment size stats via jmx
---
Key: KAFKA-106
URL: https://issues.apache.org/jira/browse/KAFKA-106
Project: Kafka
Issue Type: New Feature
Reporter: Chris Burroughs
[
https://issues.apache.org/jira/browse/KAFKA-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13082314#comment-13082314
]
Chris Burroughs commented on KAFKA-85:
--
Eric, git://git.apache.org/kafka.git mirror
[
https://issues.apache.org/jira/browse/KAFKA-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Burroughs updated KAFKA-90:
-
Priority: Minor (was: Major)
remove in tree zk jar
-
Key
remove in tree zk jar
-
Key: KAFKA-90
URL: https://issues.apache.org/jira/browse/KAFKA-90
Project: Kafka
Issue Type: Improvement
Components: packaging
Reporter: Chris Burroughs
Assignee
[
https://issues.apache.org/jira/browse/KAFKA-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Burroughs updated KAFKA-90:
-
Attachment: k90-v1.txt
remove in tree zk jar
-
Key: KAFKA
zkclient does not show up in pom
Key: KAFKA-91
URL: https://issues.apache.org/jira/browse/KAFKA-91
Project: Kafka
Issue Type: Bug
Components: packaging
Reporter: Chris Burroughs
[
https://issues.apache.org/jira/browse/KAFKA-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13081840#comment-13081840
]
Chris Burroughs commented on KAFKA-91:
--
Your right that's probably the best way instead
upgrade to latest stable 0.7.x sbt
--
Key: KAFKA-92
URL: https://issues.apache.org/jira/browse/KAFKA-92
Project: Kafka
Issue Type: Improvement
Reporter: Chris Burroughs
Assignee: Chris
[
https://issues.apache.org/jira/browse/KAFKA-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Burroughs updated KAFKA-92:
-
Status: Patch Available (was: Open)
Diff doesn't include the binary:
http://code.google.com/p
+1
On 2011-08-01 19:26, Jun Rao wrote:
Hi, Everyone,
I propose that we use the review then commit process for future changes in
Kafka. Other than trivial changes, all patches will be reviewed in JIRA. Any
objections to this?
Thanks,
Jun
The kafka-* archives links have appeared on
http://mail-archives.apache.org/mod_mbox/. Jay, could you add links to
http://sna-projects.com/kafka/contact.php ?
the index optional?
Jun
On Tue, Jul 26, 2011 at 6:19 PM, Chris Burroughs
chris.burrou...@gmail.comwrote:
So for good reason [1] Kafka doesn't keep a complicated time -- offset
index. Whatever is the start and end of log file is what you get. We
can approximate finer grained time indexes
My understanding is that in practice SO_LINGER results in a RST being
sent intead of the desired please send all of your queued data and then
close behaviour.
98 matches
Mail list logo
