GitHub user Kaiserchen opened a pull request:
https://github.com/apache/kafka/pull/1705
KAFKA-3817: KTableRepartitionMap publish old Change first, for non-count
aggregates
I affirm that the contribution is my original work and that I license the
work to the project under the projec
[
https://issues.apache.org/jira/browse/KAFKA-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407425#comment-15407425
]
ASF GitHub Bot commented on KAFKA-3817:
---
GitHub user Kaiserchen opened a pull reques
[
https://issues.apache.org/jira/browse/KAFKA-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407483#comment-15407483
]
.D. commented on KAFKA-1310:
Excuse me, appear this error is how to solve?
What principle, eac
[
https://issues.apache.org/jira/browse/KAFKA-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407593#comment-15407593
]
ASF GitHub Bot commented on KAFKA-3875:
---
Github user asfgit closed the pull request
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/1703
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
[
https://issues.apache.org/jira/browse/KAFKA-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-3875.
Resolution: Fixed
Fix Version/s: 0.10.1.0
Issue resolved by pull request 1703
[https://github
[
https://issues.apache.org/jira/browse/KAFKA-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407632#comment-15407632
]
Jim Jagielski commented on KAFKA-3940:
--
Could you send over the patch... either via a
[
https://issues.apache.org/jira/browse/KAFKA-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407746#comment-15407746
]
Dustin Cote commented on KAFKA-4017:
[~ewencp] yeah that's right. Super easy to repro
Hello Kafka users, developers and client-developers,
This is the third candidate for the release of Apache Kafka 0.10.0.1. This
is a bug fix release and it includes fixes and improvements from 53 JIRAs
(including a few critical bugs). See the release notes for more details:
http://home.apache.org
[
https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407964#comment-15407964
]
Jun Rao commented on KAFKA-3665:
[~Ryan P], is SNI really relevant here? According to Raji
[
https://issues.apache.org/jira/browse/KAFKA-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407990#comment-15407990
]
Jun Rao commented on KAFKA-4009:
Thanks for the info. Then, N1 only discovered the issue d
[
https://issues.apache.org/jira/browse/KAFKA-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-3894:
---
Summary: LogCleaner thread crashes if the number of unique keys in a
segment (was: Log Cleaner threa
[
https://issues.apache.org/jira/browse/KAFKA-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-3894:
---
Summary: LogCleaner thread crashes if not even one segment can fit in the
map (was: LogCleaner thread
[
https://issues.apache.org/jira/browse/KAFKA-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-3894:
---
Affects Version/s: 0.10.0.0
> LogCleaner thread crashes if not even one segment can fit in the map
> -
[
https://issues.apache.org/jira/browse/KAFKA-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-3894:
---
Fix Version/s: 0.10.1.0
> LogCleaner thread crashes if not even one segment can fit in the map
> -
[
https://issues.apache.org/jira/browse/KAFKA-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15408036#comment-15408036
]
Ismael Juma commented on KAFKA-3894:
I updated the title to match the issue that is st
[
https://issues.apache.org/jira/browse/KAFKA-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Bejeck updated KAFKA-3989:
---
Fix Version/s: 0.10.1.0
> Add JMH module for Benchmarks
> -
>
>
[
https://issues.apache.org/jira/browse/KAFKA-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-3894:
---
Summary: LogCleaner thread crashes if not even one segment can fit in the
offset map (was: LogCleaner
[
https://issues.apache.org/jira/browse/KAFKA-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15408067#comment-15408067
]
Ismael Juma commented on KAFKA-3989:
Is the former in the `buildscript` section? If so
Hi
Could you please tell me if this pull request can be merged and if so when
can we expect this to happen?
Thanks
Luciano
On Tue, Jul 26, 2016 at 9:01 AM, Luciano Afranllie wrote:
> Hi
>
> Could somebody with commit permission review (and eventually merge) this
> pull request?
>
> Regards
> L
Hello,
I'd like to initiate a discussion about
https://cwiki.apache.org/confluence/display/KAFKA/KIP-72%3A+Allow+Sizing+Incoming+Request+Queue+in+Bytes
The goal of the KIP is to allow configuring a bound on the capacity (as in
bytes of memory used) of the incoming request queue, in addition to th
[
https://issues.apache.org/jira/browse/KAFKA-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15408276#comment-15408276
]
Bill Bejeck commented on KAFKA-3989:
Yes, the classpath entry is in the 'buildscript s
Shawn He created KAFKA-4020:
---
Summary: Kafka consumer stop taking messages from kafka server
Key: KAFKA-4020
URL: https://issues.apache.org/jira/browse/KAFKA-4020
Project: Kafka
Issue Type: Bug
Jun Rao created KAFKA-4019:
--
Summary: LogCleaner should grow read/write buffer to max message
size for the topic
Key: KAFKA-4019
URL: https://issues.apache.org/jira/browse/KAFKA-4019
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15408544#comment-15408544
]
Ryan P commented on KAFKA-3665:
---
[~junrao] yes I do think that SNI is still relevant despite
Jun Rao created KAFKA-4021:
--
Summary: system tests need to enable trace level logging for
controller and state-change log
Key: KAFKA-4021
URL: https://issues.apache.org/jira/browse/KAFKA-4021
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15408726#comment-15408726
]
Jun Rao commented on KAFKA-3518:
Took a look at the log. The following are my findings.
>
[
https://issues.apache.org/jira/browse/KAFKA-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15408738#comment-15408738
]
Ewen Cheslack-Postava commented on KAFKA-3518:
--
[~junrao] If this case seems
[
https://issues.apache.org/jira/browse/KAFKA-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-3518.
Resolution: Cannot Reproduce
Closing the jira since it's likely fixed by KAFKA-3670.
> Transient failure in
Hello,
Just trying to follow up on the request to add me to the contributor list.
Please let me know if more information is required.
Chetan Singh
chetanjbsi...@gmail.com
On Mon, Aug 1, 2016 at 7:11 AM, chetan singh
wrote:
> Hello,
>
> I am interested in contributing to Kafka project. Can I pl
+1 (non-binding)
On Thu, Aug 4, 2016 at 6:54 AM, Ismael Juma wrote:
> Hello Kafka users, developers and client-developers,
>
> This is the third candidate for the release of Apache Kafka 0.10.0.1. This
> is a bug fix release and it includes fixes and improvements from 53 JIRAs
> (including a few
31 matches
Mail list logo