[
https://issues.apache.org/jira/browse/KAFKA-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399838#comment-13399838
]
Jun Rao commented on KAFKA-338:
---
Prashanth,
Thanks for signing up for this jira. One thing t
Hi,
We closed the following jira this week. A few other jiras have patches and
are under review.
KAFKA-329: Create topic support (revisit based on v3 design)
We have people signed up on the following jiras:
KAFKA-339: Use multi-fetch for follower replication
KAFKA-350: Improve the highwatermark
[
https://issues.apache.org/jira/browse/KAFKA-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399781#comment-13399781
]
Joel Koshy commented on KAFKA-373:
--
John, thanks for the patch. Some of these comments wo
Alan,
I found the list of jars that you published during the 0.7.0 release. The
new jars in the 0.7.1 release are the following:
commons-cli: AL2
commons-el: AL2
commons-net: AL2
commons-io: AL2
commons-compress: AL2
core: Eclipse Public License 1.0
hsqldb: BSD
jasper-compiler: AL2
jasper-runtime:
On Jun 22, 2012, at 3:16 PM, Chris Douglas wrote:
> Alan-
>
> Please recheck your results using the 0.7.0 release and not your email
> archives to make sure your process is consistent. Please also let us
> know how you're composing your list so your concerns are reproducible.
> We can't be chasi
[
https://issues.apache.org/jira/browse/KAFKA-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-353:
-
Attachment: kafka-353_v1.patch
Patch is not too big, but a bit tricky. To help with review, here is an
ove
Alan-
Please recheck your results using the 0.7.0 release and not your email
archives to make sure your process is consistent. Please also let us
know how you're composing your list so your concerns are reproducible.
We can't be chasing ghosts.
Your memory of the 0.7.0 release is dissimilar to my
[
https://issues.apache.org/jira/browse/KAFKA-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung updated KAFKA-373:
Attachment: kafka-373-v1.patch
Uploaded kafka-373-v1.patch. The changes are:
1. Modified mirror_producer*.p
[
https://issues.apache.org/jira/browse/KAFKA-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung updated KAFKA-373:
Status: Patch Available (was: Open)
> Broker Failure Test needs to be fixed to work with Mirror Maker i
John Fung created KAFKA-373:
---
Summary: Broker Failure Test needs to be fixed to work with Mirror
Maker in TRUNK
Key: KAFKA-373
URL: https://issues.apache.org/jira/browse/KAFKA-373
Project: Kafka
I
[
https://issues.apache.org/jira/browse/KAFKA-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung closed KAFKA-370.
---
Downloaded rev. 1353005 and tried the test a few times. The issue is fixed.
> Exception "java.uti
On Fri, Jun 22, 2012 at 11:25 AM, Alan D. Cabrera wrote:
> This is why documenting transitive dependencies is so dangerous.
Should we stop?
Marvin Humphrey
You would think so but that is not the case. Simply compare my old email
against what you get now.
Regards,
Alan
On Jun 22, 2012, at 11:49 AM, Jun Rao wrote:
> Alan,
>
> Shouldn't we always get the same set of jars after build from the 0.7.0
> release, whether it's done when 0.7.0 was vote
Alan,
Shouldn't we always get the same set of jars after build from the 0.7.0
release, whether it's done when 0.7.0 was voted or now?
Thanks,
Jun
On Fri, Jun 22, 2012 at 11:25 AM, Alan D. Cabrera wrote:
> This is why documenting transitive dependencies is so dangerous. The set
> of jars that
This is why documenting transitive dependencies is so dangerous. The set of
jars that I got last year is much different. This list from last year is what
was voted upon. You need to compare the 0.7.1 list of jars against what I
presented last year. You can hunt down that old email using the
Alan,
Here is what I did. I built the 0.7.0 release and the 0.7.1 release.
Extract *.jar, sort them, and compare. I reached the same conclusion as
Joe: the only new jar is snappy. Other jar differences are all due to jar
upgrades (are you referring to those?). Could you list any other completely
n
[
https://issues.apache.org/jira/browse/KAFKA-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-370.
---
Resolution: Fixed
Fix Version/s: 0.8
Assignee: Jun Rao
Thanks for the review. Committed to 0.8
[
https://issues.apache.org/jira/browse/KAFKA-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399451#comment-13399451
]
Joel Koshy commented on KAFKA-370:
--
+1
> Exception "java.util.NoSuchEleme
[
https://issues.apache.org/jira/browse/KAFKA-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399439#comment-13399439
]
Jun Rao commented on KAFKA-306:
---
Thanks for patch v4. A few more comments:
21.2 KAFA-313 add
[
https://issues.apache.org/jira/browse/KAFKA-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-370:
--
Attachment: kafka-370_v1.patch
Attach patch v1. The issue is that the code relies on the broker ids in the
hash
Alan,
I compared all dependent jars in 0.7.1 with 0.7.0. Other than upgrades, the
only added jar in 0.7.1 is the following.
./core/lib_managed/scala_2.8.0/compile/snappy-java-1.0.4.1.jar
Snappy is on Apache License 2.0. So, our licenses should be covered.
Thanks,
Jun
On Thu, Jun 21, 2012 at 9
21 matches
Mail list logo
