[
https://issues.apache.org/jira/browse/KAFKA-4542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy reassigned KAFKA-4542:
--
Assignee: Manikumar Reddy
> Add authentication based on delegation to
[
https://issues.apache.org/jira/browse/KAFKA-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy resolved KAFKA-3531.
Resolution: Duplicate
Assignee: (was: Parth Brahmbhatt)
Resolving this as
[
https://issues.apache.org/jira/browse/KAFKA-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy resolved KAFKA-4076.
Resolution: Invalid
Pl reopen the issue, if still exists.
> Kafka broker shuts down
[
https://issues.apache.org/jira/browse/KAFKA-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859568#comment-15859568
]
Manikumar Reddy commented on KAFKA-4751:
It is a known issue. Related JIR
[
https://issues.apache.org/jira/browse/KAFKA-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837319#comment-15837319
]
Manikumar Reddy commented on KAFKA-4541:
[~singhashish] Can you post your WI
[
https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15751936#comment-15751936
]
Manikumar Reddy commented on KAFKA-1696:
Thanks for creating sub-tasks. A
[
https://issues.apache.org/jira/browse/KAFKA-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15751744#comment-15751744
]
Manikumar Reddy commented on KAFKA-4541:
[~singhashish] Is this JIRA
[
https://issues.apache.org/jira/browse/KAFKA-4543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy reassigned KAFKA-4543:
--
Assignee: Manikumar Reddy
> Add capability to renew/expire delegation tok
[
https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15747403#comment-15747403
]
Manikumar Reddy commented on KAFKA-1696:
[~singhashish] Yes, Pl go ahead
[
https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15742486#comment-15742486
]
Manikumar Reddy commented on KAFKA-1696:
.[~singhashish] Sorry for the late r
[
https://issues.apache.org/jira/browse/KAFKA-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528682#comment-15528682
]
Manikumar Reddy commented on KAFKA-4074:
[~hachikuji] Yes, resolving thi
[
https://issues.apache.org/jira/browse/KAFKA-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy resolved KAFKA-4074.
Resolution: Duplicate
> Deleting a topic can make it unavailable even
[
https://issues.apache.org/jira/browse/KAFKA-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15495450#comment-15495450
]
Manikumar Reddy commented on KAFKA-4164:
This is a valid concern. Curre
[
https://issues.apache.org/jira/browse/KAFKA-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-4126:
---
Comment: was deleted
(was: Yes. Another issue related to producer excessive warn logging is
[
https://issues.apache.org/jira/browse/KAFKA-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15495420#comment-15495420
]
Manikumar Reddy commented on KAFKA-4126:
Yes. Another issue related to prod
[
https://issues.apache.org/jira/browse/KAFKA-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15495422#comment-15495422
]
Manikumar Reddy commented on KAFKA-4126:
Yes. Another issue related to prod
[
https://issues.apache.org/jira/browse/KAFKA-2700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy reassigned KAFKA-2700:
--
Assignee: Manikumar Reddy (was: Parth Brahmbhatt)
> delete topic should remove
[
https://issues.apache.org/jira/browse/KAFKA-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy reassigned KAFKA-4072:
--
Assignee: Manikumar Reddy
> improving memory usage in LogClea
[
https://issues.apache.org/jira/browse/KAFKA-2700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15492770#comment-15492770
]
Manikumar Reddy commented on KAFKA-2700:
[~parth.brahmbhatt]], are you workin
[
https://issues.apache.org/jira/browse/KAFKA-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15490118#comment-15490118
]
Manikumar Reddy commented on KAFKA-4126:
[~vahid] I think, I tried by disab
adding missing classifier parameter..
org.apache.kafka
kafka-streams
0.10.0.0
test-jar
test
On Tue, Sep 13, 2016 at 12:07 PM, Manikumar Reddy wrote:
> Hi,
>
> Kafka uses "test" as classifier (default is "tests" ) for test jars.
> We can add test paramete
Hi,
Kafka uses "test" as classifier (default is "tests" ) for test jars.
We can add test parameter to dependency tag to
resolve the error.
org.apache.kafka
kafka-streams
0.10.0.0
test-jar
test
Thanks
Manikumar
On Tue, Sep
[
https://issues.apache.org/jira/browse/KAFKA-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469613#comment-15469613
]
Manikumar Reddy commented on KAFKA-4074:
[~junrao] Yes, Both issues are same
[
https://issues.apache.org/jira/browse/KAFKA-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469580#comment-15469580
]
Manikumar Reddy commented on KAFKA-4111:
Ok got it. Broker handles each prod
[
https://issues.apache.org/jira/browse/KAFKA-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15466584#comment-15466584
]
Manikumar Reddy commented on KAFKA-4111:
"compression.type"
[
https://issues.apache.org/jira/browse/KAFKA-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15466570#comment-15466570
]
Manikumar Reddy commented on KAFKA-4109:
Enable producer debug logs to get
[
https://issues.apache.org/jira/browse/KAFKA-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15466496#comment-15466496
]
Manikumar Reddy commented on KAFKA-4126:
Currently producer logs below
We don't need JIRA for minor PRs. Just prefix "MINOR:" to PR title.
On Tue, Sep 6, 2016 at 9:16 AM, Jaikiran Pai
wrote:
> Thanks Ismael, I'll raise a PR for this. As a process, is there a JIRA
> that's expected to be filed for this before I raise a PR or would this be
> OK without a JIRA?
>
> -J
[
https://issues.apache.org/jira/browse/KAFKA-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15436585#comment-15436585
]
Manikumar Reddy commented on KAFKA-4065:
Agree, currently new producer d
[
https://issues.apache.org/jira/browse/KAFKA-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy reassigned KAFKA-4074:
--
Assignee: Manikumar Reddy
> Deleting a topic can make it unavailable even
[
https://issues.apache.org/jira/browse/KAFKA-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15434215#comment-15434215
]
Manikumar Reddy commented on KAFKA-4065:
"compression.type" conf
[
https://issues.apache.org/jira/browse/KAFKA-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432667#comment-15432667
]
Manikumar Reddy commented on KAFKA-3218:
[~ rajinisivaram]KAFKA-3680 f
[
https://issues.apache.org/jira/browse/KAFKA-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432252#comment-15432252
]
Manikumar Reddy commented on KAFKA-4076:
You are storing kafka data logs to
[
https://issues.apache.org/jira/browse/KAFKA-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy resolved KAFKA-3204.
Resolution: Won't Fix
> ConsumerConnector blocked on Authenticated by SAS
+1 (non-binding)
This feature help us control memory footprint and allows consumer to
progress on fetching large messages.
On Fri, Aug 19, 2016 at 10:32 AM, Gwen Shapira wrote:
> +1 (binding)
>
> On Thu, Aug 18, 2016 at 1:47 PM, Andrey L. Neporada
> wrote:
> > Hi all!
> > I’ve modified KIP-74
[
https://issues.apache.org/jira/browse/KAFKA-4063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy resolved KAFKA-4063.
Resolution: Duplicate
> Add support for infinite endpoints for range queries in Ka
[
https://issues.apache.org/jira/browse/KAFKA-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy resolved KAFKA-2199.
Resolution: Fixed
> Make signing artifacts optional, setting maven repository possible f
During server/client startup, we are logging all the supplied configs. May
be we can just mask
the password related config values for both valid/invalid configs.
On Wed, Aug 17, 2016 at 5:14 PM, Jaikiran Pai
wrote:
> Any opinion about this proposed change?
>
> -Jaikiran
>
> On Tuesday 16 August
[
https://issues.apache.org/jira/browse/KAFKA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424315#comment-15424315
]
Manikumar Reddy edited comment on KAFKA-3980 at 8/17/16 11:2
[
https://issues.apache.org/jira/browse/KAFKA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424315#comment-15424315
]
Manikumar Reddy commented on KAFKA-3980:
as suspected, this may be relate
[
https://issues.apache.org/jira/browse/KAFKA-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-4035:
---
Resolution: Fixed
Fix Version/s: 0.10.1.0
Status: Resolved (was: Patch
[
https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419140#comment-15419140
]
Manikumar Reddy commented on KAFKA-3959:
Yes, min.insync.replicas applicabl
[
https://issues.apache.org/jira/browse/KAFKA-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-4012:
---
Status: Patch Available (was: Open)
> KerberosShortNamer should implement toStr
[
https://issues.apache.org/jira/browse/KAFKA-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-4035:
---
Affects Version/s: 0.9.0.0
0.10.0.0
0.10.0.1
[
https://issues.apache.org/jira/browse/KAFKA-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-4035:
---
Status: Patch Available (was: Open)
> AclCommand should allow Describe operation on gro
[
https://issues.apache.org/jira/browse/KAFKA-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy reassigned KAFKA-4035:
--
Assignee: Manikumar Reddy
> AclCommand should allow Describe operation on gro
[
https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418751#comment-15418751
]
Manikumar Reddy edited comment on KAFKA-3959 at 8/12/16 1:2
[
https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418751#comment-15418751
]
Manikumar Reddy commented on KAFKA-3959:
looks like this is done on pur
[
https://issues.apache.org/jira/browse/KAFKA-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy resolved KAFKA-1612.
Resolution: Won't Fix
Closing this issue in favor new consumer API.
> Consumer
+1 (non-binding)
On Wed, Aug 10, 2016 at 8:30 AM, Ewen Cheslack-Postava
wrote:
> +1 (binding), thanks for working on this Vahid.
>
> @Dana - See https://cwiki.apache.org/confluence/display/KAFKA/Bylaws re:
> binding/non-binding, although I now notice that we specify criteria (lazy
> majority) on
ka-0.10.0.1-rc2/RELEASE_NOTES.html
>>
>> When compared to RC1, RC2 contains a fix for a regression where an older
>> version of slf4j-log4j12 was also being included in the libs folder of the
>> binary tarball (KAFKA-4008). Thanks to Manikumar Reddy for reporting the
>&g
Hi,
There are two versions of slf4j-log4j jar in the build. (1.6.1, 1.7.21).
slf4j-log4j12-1.6.1.jar is coming from streams:examples module.
Thanks,
Manikumar
On Tue, Aug 2, 2016 at 8:31 PM, Ismael Juma wrote:
> Hello Kafka users, developers and client-developers,
>
> This is the second candid
[
https://issues.apache.org/jira/browse/KAFKA-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-3950:
---
Affects Version/s: (was: 0.10.0.0)
0.9.0.0
> kafka mirror ma
[
https://issues.apache.org/jira/browse/KAFKA-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-3950:
---
Reviewer: Ismael Juma
Fix Version/s: 0.10.0.1
> kafka mirror maker tool is
[
https://issues.apache.org/jira/browse/KAFKA-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-3950:
---
Affects Version/s: 0.10.0.0
> kafka mirror maker tool is not respecting whitelist opt
[
https://issues.apache.org/jira/browse/KAFKA-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399444#comment-15399444
]
Manikumar Reddy commented on KAFKA-3950:
[~ijuma] Can we include this in 0.10
[
https://issues.apache.org/jira/browse/KAFKA-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393962#comment-15393962
]
Manikumar Reddy commented on KAFKA-3992:
looks like you are giving same clien
[
https://issues.apache.org/jira/browse/KAFKA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390792#comment-15390792
]
Manikumar Reddy edited comment on KAFKA-3980 at 7/23/16 6:2
[
https://issues.apache.org/jira/browse/KAFKA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390792#comment-15390792
]
Manikumar Reddy commented on KAFKA-3980:
[~ajorgensen] Can you enable debug
[
https://issues.apache.org/jira/browse/KAFKA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387174#comment-15387174
]
Manikumar Reddy commented on KAFKA-3980:
This may due to increasing in cl
[
https://issues.apache.org/jira/browse/KAFKA-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15379198#comment-15379198
]
Manikumar Reddy commented on KAFKA-3102:
Subscribe to user mailing
[
https://issues.apache.org/jira/browse/KAFKA-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-2213:
---
Resolution: Duplicate
Status: Resolved (was: Patch Available)
This duplicate of
[
https://issues.apache.org/jira/browse/KAFKA-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15379135#comment-15379135
]
Manikumar Reddy commented on KAFKA-3102:
[~liuxinjian] There is no kafka i
[
https://issues.apache.org/jira/browse/KAFKA-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy resolved KAFKA-3102.
Resolution: Duplicate
> Kafka server unable to connect to zookee
Hi,
Can we allow ListAcls to take list of resources? This may help when we
have many associated
resources under same principal.
Thanks
Manikumar
On Fri, Jul 15, 2016 at 11:15 AM, Gwen Shapira wrote:
> Thank you, Grant. This is lovely :)
>
> Few comments / requests for clarifications below:
>
[
https://issues.apache.org/jira/browse/KAFKA-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375342#comment-15375342
]
Manikumar Reddy commented on KAFKA-3961:
you can try DumpLogSegments tools t
[
https://issues.apache.org/jira/browse/KAFKA-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15373115#comment-15373115
]
Manikumar Reddy commented on KAFKA-3950:
I was also thinking similar l
[
https://issues.apache.org/jira/browse/KAFKA-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-3950:
---
consumer.subscribe(Pattern p , ..) method is failing when authorizer is enabled.
irrespective of
Hi,
consumer.subscribe(Pattern p , ..) method implementation tries to get
metadata of all the topics.
This will throw TopicAuthorizationException on internal topics and other
unauthorized topics.
We may need to move the pattern matching to sever side.
Is this know issue?. If not, I will raise JIR
+1 (non-binding)
On Tue, Jun 21, 2016 at 9:16 AM, Ewen Cheslack-Postava
wrote:
> +1 (binding) and thanks for the work on this Grant!
>
> -Ewen
>
> On Mon, Jun 20, 2016 at 12:18 PM, Gwen Shapira wrote:
>
> > +1 (binding)
> >
> > On Mon, Jun 20, 2016 at 12:13 PM, Tom Crayford
> > wrote:
> > > +1
+1 (non-binding)
On Fri, Jun 17, 2016 at 3:37 PM, Rajini Sivaram <
rajinisiva...@googlemail.com> wrote:
> +1 (non-binding)
>
> On Fri, Jun 17, 2016 at 4:45 AM, Grant Henke wrote:
>
> > +1
> >
> > On Thu, Jun 16, 2016 at 8:50 PM, tao xiao wrote:
> >
> > > +1
> > >
> > > On Fri, 17 Jun 2016 at 09
[
https://issues.apache.org/jira/browse/KAFKA-3802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-3802:
---
Status: Patch Available (was: Open)
> log mtimes reset on broker rest
[
https://issues.apache.org/jira/browse/KAFKA-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-2651:
---
Fix Version/s: 0.11.0.0
> Remove deprecated config alteration from TopicCommand in 0.9.
+1 (non binding)
On Wed, May 25, 2016 at 4:03 PM, Tom Crayford wrote:
> +1 (non binding)
>
> Agree on log.cleaner.compaction.delay.ms being the better name.
>
> I think this setting is going to be extremely hard to tune for users, and
> worry about adding yet more configuration - Kafka already h
e:
> Manikumar,
> Any reason for this. Before the workflow is to open
> a new JIRA if a JIRA closed.
> -Harsha
>
> On Fri, May 20, 2016, at 08:54 PM, Manikumar Reddy wrote:
> > Jun/Ismail,
> >
> > I requested Apache Infra to change JIRA w
[
https://issues.apache.org/jira/browse/KAFKA-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy resolved KAFKA-2547.
Resolution: Fixed
> Make DynamicConfigManager to use the ZkNodeChangeNotificationListe
[
https://issues.apache.org/jira/browse/KAFKA-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-2547:
---
Status: Reopened (was: Closed)
> Make DynamicConfigManager to use
[
https://issues.apache.org/jira/browse/KAFKA-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy resolved KAFKA-3219.
Resolution: Fixed
> Long topic names mess up broker topic st
[
https://issues.apache.org/jira/browse/KAFKA-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-3219:
---
Status: Reopened (was: Closed)
> Long topic names mess up broker topic st
Jun/Ismail,
I requested Apache Infra to change JIRA workflow to add Closed -> Reopen
transition.
https://issues.apache.org/jira/browse/INFRA-11857
Let me know, If any concerns
Manikumar
[
https://issues.apache.org/jira/browse/KAFKA-2800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy resolved KAFKA-2800.
Resolution: Fixed
> Update outdated dependenc
[
https://issues.apache.org/jira/browse/KAFKA-2800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-2800:
---
Status: Reopened (was: Closed)
> Update outdated dependenc
Hi,
There is a kafka.tools.TestLogCleaning tool, which is used to stress test
the compaction feature.
This tool validates the correctness of compaction process. This tool can be
improved for perf testing.
I think you want to benchmark server side compaction process. Currently we
have few compact
[
https://issues.apache.org/jira/browse/KAFKA-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-2159:
---
Resolution: Duplicate
Status: Resolved (was: Patch Available
[
https://issues.apache.org/jira/browse/KAFKA-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy closed KAFKA-665.
-
> Outgoing responses delayed on a busy Kafka bro
[
https://issues.apache.org/jira/browse/KAFKA-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy resolved KAFKA-1201.
Resolution: Duplicate
Assignee: (was: Jay Kreps)
Fix Version/s: 0.9.0.0
[
https://issues.apache.org/jira/browse/KAFKA-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy reassigned KAFKA-3389:
--
Assignee: Manikumar Reddy (was: Neha Narkhede)
> ReplicaStateMach
[
https://issues.apache.org/jira/browse/KAFKA-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15282496#comment-15282496
]
Manikumar Reddy commented on KAFKA-3389:
Scala map.forall(predicate) returns
[
https://issues.apache.org/jira/browse/KAFKA-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy resolved KAFKA-2868.
Resolution: Duplicate
This was fixed in KAFKA-2138
> retry.backoff.ms ignored by Produ
[
https://issues.apache.org/jira/browse/KAFKA-3593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy resolved KAFKA-3593.
Resolution: Duplicate
> kafka.network.Processor throws ArrayIndexOutOfBoundsExcept
[
https://issues.apache.org/jira/browse/KAFKA-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-3584:
---
Status: Patch Available (was: Open)
> NullPointer Exception found when Delete Topic and
[
https://issues.apache.org/jira/browse/KAFKA-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272275#comment-15272275
]
Manikumar Reddy commented on KAFKA-3525:
1. Assume reserved.broker.max.id =10
[
https://issues.apache.org/jira/browse/KAFKA-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15270385#comment-15270385
]
Manikumar Reddy commented on KAFKA-3147:
Similar exception scenario is fixe
[
https://issues.apache.org/jira/browse/KAFKA-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-2651:
---
Assignee: Manikumar Reddy
Status: Patch Available (was: Open)
> Remove depreca
[
https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15261630#comment-15261630
]
Manikumar Reddy commented on KAFKA-3587:
[~ecomar] your alternative appr
[
https://issues.apache.org/jira/browse/KAFKA-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-3629:
---
Status: Patch Available (was: Open)
> KStreamImpl.to(...) throws NPE when the value SerDe
Congrats Ismael!!
On Tue, Apr 26, 2016 at 12:03 PM, Ashish Singh wrote:
> Congrats Ismael, well deserved!
>
> On Monday, April 25, 2016, Guozhang Wang wrote:
>
> > Congrats Ismael!
> >
> > On Mon, Apr 25, 2016 at 10:52 PM, Neha Narkhede > > wrote:
> >
> > > The PMC for Apache Kafka has invited
[
https://issues.apache.org/jira/browse/KAFKA-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15253761#comment-15253761
]
Manikumar Reddy commented on KAFKA-3609:
Current Mirror Maker supports par
[
https://issues.apache.org/jira/browse/KAFKA-3517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-3517:
---
Status: Patch Available (was: Open)
> Document configuration of SASL/PLAIN and multi
[
https://issues.apache.org/jira/browse/KAFKA-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-3605:
---
Status: Patch Available (was: Reopened)
> Connector REST endpoint allows incorrec
1 - 100 of 872 matches
Mail list logo
