[
https://issues.apache.org/jira/browse/KAFKA-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241396#comment-13241396
]
Jun Rao edited comment on KAFKA-320 at 3/29/12 5:21 PM:
That
[
https://issues.apache.org/jira/browse/KAFKA-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241396#comment-13241396
]
Jun Rao commented on KAFKA-320:
---
That's a good finding. We should probably patch i
Here is another thought. An alternative is to take the fetch.size in
consumer config and divide it among all partitions. Initially, this can be
just simple even distribution. Later on, we can be a bit smarter and give
larger partitions larger fetch size.
Thanks,
Jun
On Thu, Mar 29, 2012 at 1:51
[
https://issues.apache.org/jira/browse/KAFKA-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240166#comment-13240166
]
Jun Rao commented on KAFKA-249:
---
Thanks for the patch. Some comments:
1. For fu
[
https://issues.apache.org/jira/browse/KAFKA-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-305.
---
Resolution: Fixed
Fix Version/s: 0.8
Assignee: Prashanth Menon
Prashanth,
Thanks for the
[
https://issues.apache.org/jira/browse/KAFKA-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238470#comment-13238470
]
Jun Rao commented on KAFKA-318:
---
Pierre-Yves,
Thanks for the patch. Could you summarize
disallow recursively compressed message
---
Key: KAFKA-316
URL: https://issues.apache.org/jira/browse/KAFKA-316
Project: Kafka
Issue Type: Improvement
Components: core
Reporter: Jun
[
https://issues.apache.org/jira/browse/KAFKA-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-315:
--
Status: Patch Available (was: Open)
patch attached.
> enable shallow iterator
[
https://issues.apache.org/jira/browse/KAFKA-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-315:
--
Attachment: kafka-315.patch
> enable shallow iterator in ByteBufferMessageSet to allow mirroing d
Project: Kafka
Issue Type: Improvement
Components: core
Reporter: Jun Rao
Assignee: Jun Rao
Fix For: 0.7.1
Attachments: kafka-315.patch
Currently, the iterator of ByteBufferMessageSet does deep iteration, ie, if
messages are
[
https://issues.apache.org/jira/browse/KAFKA-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237021#comment-13237021
]
Jun Rao commented on KAFKA-305:
---
If this is indeed a ZK issue, we can probably check/
[
https://issues.apache.org/jira/browse/KAFKA-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13236782#comment-13236782
]
Jun Rao commented on KAFKA-305:
---
Prashanth,
v2 patch looks good.
As for 5, I do
[
https://issues.apache.org/jira/browse/KAFKA-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13236734#comment-13236734
]
Jun Rao commented on KAFKA-307:
---
+1 on patch v3.
> Refactor server
[
https://issues.apache.org/jira/browse/KAFKA-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13236175#comment-13236175
]
Jun Rao commented on KAFKA-307:
---
Thanks for patch v2. Looks cleaner. A couple of o
[
https://issues.apache.org/jira/browse/KAFKA-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235707#comment-13235707
]
Jun Rao commented on KAFKA-307:
---
Overall looks good. Some suggestions:
1. KafkaSe
[
https://issues.apache.org/jira/browse/KAFKA-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235679#comment-13235679
]
Jun Rao commented on KAFKA-309:
---
+1 on the patch.
> Bug in FileMessa
[
https://issues.apache.org/jira/browse/KAFKA-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235675#comment-13235675
]
Jun Rao commented on KAFKA-310:
---
+1 on v2.
> Incomplete mess
[
https://issues.apache.org/jira/browse/KAFKA-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235636#comment-13235636
]
Jun Rao commented on KAFKA-310:
---
ByteBufferMessageSet.validBytes currently makes a
[
https://issues.apache.org/jira/browse/KAFKA-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235614#comment-13235614
]
Jun Rao commented on KAFKA-305:
---
Prashant,
2. If you want to make sure that a broke
[
https://issues.apache.org/jira/browse/KAFKA-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234541#comment-13234541
]
Jun Rao commented on KAFKA-300:
---
+1 on patch v2.
> Implement
[
https://issues.apache.org/jira/browse/KAFKA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234017#comment-13234017
]
Jun Rao commented on KAFKA-296:
---
Also, could you add some basic unit tests for the go cl
[
https://issues.apache.org/jira/browse/KAFKA-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-303:
--
Resolution: Fixed
Fix Version/s: 0.7.1
Status: Resolved (was: Patch Available)
Jose,
Thanks
[
https://issues.apache.org/jira/browse/KAFKA-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-279.
---
Resolution: Fixed
Fix Version/s: 0.7.1
Assignee: Jun Rao
Edward,
Thanks for the review. Just
[
https://issues.apache.org/jira/browse/KAFKA-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233969#comment-13233969
]
Jun Rao commented on KAFKA-305:
---
Prashanth,
Thanks for the patch. This is very useful.
[
https://issues.apache.org/jira/browse/KAFKA-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233885#comment-13233885
]
Jun Rao commented on KAFKA-300:
---
Thanks for the patch. Some comments:
1. KafkaZookeeper:
[
https://issues.apache.org/jira/browse/KAFKA-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-292:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
[
https://issues.apache.org/jira/browse/KAFKA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao reopened KAFKA-296:
---
Actually, I have to revert the commit since the patch didn't apply cleanly.
! clients/go/tools/of
[
https://issues.apache.org/jira/browse/KAFKA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-296:
--
Resolution: Fixed
Fix Version/s: 0.7.1
Status: Resolved (was: Patch Available)
Thanks for
[
https://issues.apache.org/jira/browse/KAFKA-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-49:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thanks for the patch Prashanth. Just committed
[
https://issues.apache.org/jira/browse/KAFKA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13228865#comment-13228865
]
Jun Rao commented on KAFKA-296:
---
I can't seem to apply the patch. Could you rebase?
[
https://issues.apache.org/jira/browse/KAFKA-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13228845#comment-13228845
]
Jun Rao commented on KAFKA-49:
--
Prashanth,
I am ready to commit your patch. A couple th
[
https://issues.apache.org/jira/browse/KAFKA-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13228774#comment-13228774
]
Jun Rao commented on KAFKA-45:
--
If there are 2 followers and leader receives ack from
[
https://issues.apache.org/jira/browse/KAFKA-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225845#comment-13225845
]
Jun Rao commented on KAFKA-49:
--
1. Or we can just treat noacks the same as act=1 for
[
https://issues.apache.org/jira/browse/KAFKA-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225321#comment-13225321
]
Jun Rao commented on KAFKA-49:
--
Prashanth,
Thanks for the patch. Overall, it looks pr
[
https://issues.apache.org/jira/browse/KAFKA-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-220:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to trunk
[
https://issues.apache.org/jira/browse/KAFKA-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224538#comment-13224538
]
Jun Rao commented on KAFKA-273:
---
The patch for EOF looks fine. We probably need to do
Jeffrey,
Yes, we can get that started. Just be aware that there could be minor
tweaks to the wire protocol in the next few months.
Thanks,
Jun
On Wed, Mar 7, 2012 at 7:02 AM, Jeffrey Damick wrote:
> So now that kafka-240 is complete, shall we go ahead and start updating the
> clients? i'll sta
[
https://issues.apache.org/jira/browse/KAFKA-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223525#comment-13223525
]
Jun Rao commented on KAFKA-273:
---
We have also seem the following gzip issue. Is that
Joe,
0.8 now has compilation error after this check in. It seems that you forgot
to check in a new file. See my comment in kafka-240. Could you fix this?
Thanks,
Jun
On Fri, Mar 2, 2012 at 9:46 PM, wrote:
> Author: joestein
> Date: Sat Mar 3 05:46:43 2012
> New Revision: 1296577
>
> URL: htt
[
https://issues.apache.org/jira/browse/KAFKA-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223436#comment-13223436
]
Jun Rao commented on KAFKA-240:
---
I got a compilation error on 0.8.
/home/
Added you to the committer list of kafka jira. Hopefully you can resolve
jiras now.
Thanks,
Jun
On Wed, Feb 29, 2012 at 6:49 PM, Joe Stein wrote:
> I don't have access it seems so can't resolve
> https://issues.apache.org/jira/browse/KAFKA-284
>
> my username=charmalloc
>
> thanx
>
> /*
> Joe
[
https://issues.apache.org/jira/browse/KAFKA-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223407#comment-13223407
]
Jun Rao commented on KAFKA-49:
--
Prashanth,
Yes, that's actually a real bug. I
[
https://issues.apache.org/jira/browse/KAFKA-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223331#comment-13223331
]
Jun Rao commented on KAFKA-294:
---
Are you using namespace in ZK connection string? If so,
[
https://issues.apache.org/jira/browse/KAFKA-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-220:
--
Assignee: Jun Rao
Status: Patch Available (was: Open)
Attach a patch by setting lastmodifiedtime
[
https://issues.apache.org/jira/browse/KAFKA-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-220:
--
Attachment: kafka-220.patch
> LogManager test fails on li
Yes, I think so.
Thanks,
Jun
On Mon, Mar 5, 2012 at 2:59 PM, Andrew Psaltis wrote:
> All,
>
> We are interested in contributing to Kafka and wanted to clarify if the
> following Corporate Contributor License Agreement:
>
> http://www.apache.org/licenses/cla-corporate.txt
>
> Is the correct one
[
https://issues.apache.org/jira/browse/KAFKA-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222779#comment-13222779
]
Jun Rao commented on KAFKA-49:
--
The current defaulteventhandler already refreshes t
[
https://issues.apache.org/jira/browse/KAFKA-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-292:
--
Attachment: kafka-292_v2.patch
Attach patch v2. There is already a unit test for this. Just need to add the
[
https://issues.apache.org/jira/browse/KAFKA-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222700#comment-13222700
]
Jun Rao commented on KAFKA-49:
--
Prashanth,
That's a good question. Initially, I
[
https://issues.apache.org/jira/browse/KAFKA-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-292:
--
Attachment: kafka-292.patch
> broker deletes all file segments when cleaning up an empty log segm
[
https://issues.apache.org/jira/browse/KAFKA-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-292:
--
Status: Patch Available (was: Open)
patch attached.
> broker deletes all file segments w
Components: core
Reporter: Jun Rao
Assignee: Jun Rao
Fix For: 0.7.1
Attachments: kafka-292.patch
Suppose that a log has only one log segment left and it's empty. If that
segment expires and is deleted, we roll out a new segment of the
[
https://issues.apache.org/jira/browse/KAFKA-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13221452#comment-13221452
]
Jun Rao commented on KAFKA-240:
---
Joe,
When the client creates a ProduceRequest, we d
[
https://issues.apache.org/jira/browse/KAFKA-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13221318#comment-13221318
]
Jun Rao commented on KAFKA-240:
---
Yes, however, that information is not passed
[
https://issues.apache.org/jira/browse/KAFKA-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13221183#comment-13221183
]
Jun Rao commented on KAFKA-240:
---
Joe,
kafka-239 has been committed to the 0.8 branch.
[
https://issues.apache.org/jira/browse/KAFKA-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-239:
--
Resolution: Fixed
Fix Version/s: 0.8
Status: Resolved (was: Patch Available)
> W
[
https://issues.apache.org/jira/browse/KAFKA-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-50:
-
Attachment: kafka_replication_highlevel_design.docx
> kafka intra-cluster replication supp
[
https://issues.apache.org/jira/browse/KAFKA-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-50:
-
Attachment: kafka_replication_detailed_design_v2.docx
Attach the word doc of the design.
> ka
[
https://issues.apache.org/jira/browse/KAFKA-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220297#comment-13220297
]
Jun Rao commented on KAFKA-239:
---
+1 on the patch.
For 2, I was interpreting Host as a
[
https://issues.apache.org/jira/browse/KAFKA-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220290#comment-13220290
]
Jun Rao commented on KAFKA-50:
--
Yes, we can start a new wiki for each of the sub-jiras
[
https://issues.apache.org/jira/browse/KAFKA-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-240:
--
Attachment: kafka-240_unittestfix_delta.patch
Joe,
There are 2 reasons why the unit test fails.
1. Some
[
https://issues.apache.org/jira/browse/KAFKA-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220155#comment-13220155
]
Jun Rao commented on KAFKA-239:
---
Please address items 2 and 11. For 4, I am fine leaving
[
https://issues.apache.org/jira/browse/KAFKA-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219370#comment-13219370
]
Jun Rao commented on KAFKA-239:
---
1. ZkUtils.getTopicPartitionsPath: There are a co
[
https://issues.apache.org/jira/browse/KAFKA-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-290:
--
Attachment: kafka-290_v3.patch
Attach patch v3 that requires either broker.lost or zk.connect to be present
[
https://issues.apache.org/jira/browse/KAFKA-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-290:
--
Attachment: kafka-290_v2.patch
Attach patch v2.
> use propertyExists to test if b
[
https://issues.apache.org/jira/browse/KAFKA-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-290:
--
Affects Version/s: 0.7.1
Status: Patch Available (was: Open)
patch attached
[
https://issues.apache.org/jira/browse/KAFKA-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-290:
--
Attachment: kafka-290.patch
> use propertyExists to test if both broker.list and zk.connect are pres
Type: Improvement
Reporter: Jun Rao
Assignee: Jun Rao
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more
Joe,
As a new committer, do you want to do the report this time?
Thanks,
Jun
On Mon, Feb 27, 2012 at 8:16 PM, Alan D. Cabrera wrote:
> Any takers?
>
>
> Regards,
> Alan
>
>
> On Feb 23, 2012, at 5:14 AM, Marvin wrote:
>
> >
> >
> > Dear podling,
> >
> > This email was sent by an automated syst
[
https://issues.apache.org/jira/browse/KAFKA-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-285:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thanks for the patch, Elben. Just committed
; >
> >
> > nnarkhed-ld:kafka-239-topic-metadata nnarkhed$ svn log -l 5
> >
> > r1244650 | junrao | 2012-02-15 11:08:08 -0800 (Wed, 15 Feb 2012) | 1 line
> >
&
[
https://issues.apache.org/jira/browse/KAFKA-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217513#comment-13217513
]
Jun Rao commented on KAFKA-249:
---
Could we support subscribing to wildcard topics directl
[
https://issues.apache.org/jira/browse/KAFKA-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217500#comment-13217500
]
Jun Rao commented on KAFKA-240:
---
If you are not addressing #8 in this jira, we can trac
[
https://issues.apache.org/jira/browse/KAFKA-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-286:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thanks for the review. Just committed this
[
https://issues.apache.org/jira/browse/KAFKA-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217375#comment-13217375
]
Jun Rao commented on KAFKA-286:
---
Will this happen? It doesn't seem possible to me.
[
https://issues.apache.org/jira/browse/KAFKA-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217331#comment-13217331
]
Jun Rao commented on KAFKA-279:
---
That typically means that you are sending data at a
[
https://issues.apache.org/jira/browse/KAFKA-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-286:
--
Attachment: kafka-286_v2.patch
That's a good point. What can happen is that we may delete ZK paths th
[
https://issues.apache.org/jira/browse/KAFKA-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-283:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thanks for the review. Just committed this
[
https://issues.apache.org/jira/browse/KAFKA-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-286:
--
Attachment: kafka-286.patch
> consumer sometimes don't release partition ownership properly in Z
[
https://issues.apache.org/jira/browse/KAFKA-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-286:
--
Status: Patch Available (was: Open)
Patch attached.
> consumer sometimes don't
oject: Kafka
Issue Type: Bug
Components: core
Reporter: Jun Rao
Assignee: Jun Rao
Fix For: 0.7.1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
[
https://issues.apache.org/jira/browse/KAFKA-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215728#comment-13215728
]
Jun Rao commented on KAFKA-44:
--
It may be possible, but this can be a bit tricky. When
[
https://issues.apache.org/jira/browse/KAFKA-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-283:
--
Status: Patch Available (was: Open)
patch attached.
> add jmx beans in broker to track #
[
https://issues.apache.org/jira/browse/KAFKA-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-283:
--
Attachment: kafka-283.patch
> add jmx beans in broker to track # of failed reque
: core
Reporter: Jun Rao
Assignee: Jun Rao
Fix For: 0.7.1
Attachments: kafka-283.patch
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure
[
https://issues.apache.org/jira/browse/KAFKA-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-277.
---
Resolution: Fixed
Fix Version/s: 0.7.1
Thanks for the patch. It looks good. Just committed to trunk
[
https://issues.apache.org/jira/browse/KAFKA-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao reassigned KAFKA-277:
-
Assignee: Yang Ye
> Add a shallow iterator to the ByteBufferMessageSet, which is only used
We use scala collections very heavily. There is probably some overhead in
that. However, I am not sure if it's significant. Compared to disk I/Os and
network overhead, the scala overhead is probably negligible.
Jun
On Thu, Feb 23, 2012 at 12:11 PM, S Ahmed wrote:
> Excluding the fact it would p
[
https://issues.apache.org/jira/browse/KAFKA-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213817#comment-13213817
]
Jun Rao commented on KAFKA-46:
--
Some notes on the implementation:
1. If required_acks f
support multiple root log directories
-
Key: KAFKA-281
URL: https://issues.apache.org/jira/browse/KAFKA-281
Project: Kafka
Issue Type: Improvement
Components: core
Reporter: Jun Rao
Components: core
Affects Versions: 0.8
Reporter: Jun Rao
Currently, the on-disk layout is {log.dir}/topicname-partitionid. The problem
is that there is no appropriate place to store topicname level information such
as topic version. An alternative layout is {log.dir}/topicname
[
https://issues.apache.org/jira/browse/KAFKA-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213283#comment-13213283
]
Jun Rao commented on KAFKA-44:
--
Not sure if I follow exactly what you are proposing here
[
https://issues.apache.org/jira/browse/KAFKA-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213033#comment-13213033
]
Jun Rao commented on KAFKA-45:
--
Prashanth,
That's a good question. We'd like to
[
https://issues.apache.org/jira/browse/KAFKA-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213002#comment-13213002
]
Jun Rao commented on KAFKA-44:
--
Prshanth,
This seems like a good idea to me. Ideally,
Milind,
Thanks for the info. Could you update the wiki to report your usage?
Jun
On Mon, Feb 20, 2012 at 6:57 PM, Milind Parikh wrote:
> http://www.countandra.org/?q=node/19
>
> Thanks for the excellent work!
>
> Regards
> Milind
>
[
https://issues.apache.org/jira/browse/KAFKA-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212738#comment-13212738
]
Jun Rao commented on KAFKA-277:
---
Also, please add a unit test for this. Use a max_mes
[
https://issues.apache.org/jira/browse/KAFKA-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212329#comment-13212329
]
Jun Rao commented on KAFKA-48:
--
Overall, the patch looks good. Some comments
[
https://issues.apache.org/jira/browse/KAFKA-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-255:
--
Resolution: Fixed
Fix Version/s: 0.7.1
Status: Resolved (was: Patch Available)
Thanks John
[
https://issues.apache.org/jira/browse/KAFKA-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-254:
--
Resolution: Fixed
Fix Version/s: 0.7.1
Status: Resolved (was: Patch Available)
Thanks John
[
https://issues.apache.org/jira/browse/KAFKA-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-279:
--
Attachment: kafka-279.patch
Milind,
Attached is a patch to trunk. Could you try it out and see if it fixes
801 - 900 of 1410 matches
Mail list logo
